← HonkWatch.com

Is Slack down in Svalbard and Jan Mayen?

No problems reported with Slack right now

People in Svalbard and Jan Mayen: 0 reports in the last hour Official page: No incident reported, checked 2 min ago Our checks: loads from 35 of 35 places

API (Apps/Integrations/APIs): OperationalLogin (Login/SSO): Operational

Slack reports no current incident. Updated 7 Nov, 19:48 UTC, 2 min ago · Official status page
Report a problem
Change country

Known issues (from Slack's status page)

Slack's status page lists no open incident and no planned maintenance.

In Slack's own words, as we read them every 2.5 minutes, last 2 min ago. Read Slack's status page

Reports from people in Svalbard and Jan Mayen

Last 24 hours · Svalbard and Jan Mayen · times in UTC

0 reports

No community reports in the last 24 hours from Svalbard and Jan Mayen. Having trouble? Add your report.

024 00:0006:0012:0018:00 20:00-20:10 UTC: 24 of 24 places loaded it, typical 378 to 430 ms20:10-21:00 UTC: 35 of 35 places loaded it, typical 368 to 435 ms21:00-21:05 UTC: 25 of 25 places loaded it, typical 448 ms21:05-21:10 UTC: 30 of 30 places loaded it, typical 522 ms21:10-21:25 UTC: 35 of 35 places loaded it, typical 411 to 435 ms21:25-21:30 UTC: 33 of 33 places loaded it, typical 421 ms21:30-21:45 UTC: 35 of 35 places loaded it, typical 372 to 430 ms21:45-21:50 UTC: 33 of 33 places loaded it, typical 373 ms21:50-21:55 UTC: 27 of 27 places loaded it, typical 483 ms21:55-19:50 UTC: 35 of 35 places loaded it, typical 344 to 495 ms Typical response time of the places that loaded it, at most 522 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Strip under the bars: how many places loaded slack.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Our checks are worldwide; the bars count reports from Svalbard and Jan Mayen only.

Latest checks, 21:55-19:50 UTC: 35 of 35 places loaded it, typical 344 to 495 ms.

Report totals as of 7 Nov, 19:50 UTC

Report a problem with Slack

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Svalbard and Jan Mayen

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Svalbard and Jan Mayen. The report chart above is filtered to Svalbard and Jan Mayen.

Our own checks of slack.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Jakarta: loaded in 370 ms Doha: loaded in 719 ms São Paulo: loaded in 213 ms Santiago: loaded in 836 ms Hong Kong: loaded in 693 ms Johannesburg: loaded in 430 ms Lauterbourg: loaded in 237 ms New Jersey: loaded in 167 ms New York: loaded in 194 ms Mumbai: loaded in 593 ms Atlanta: loaded in 218 ms Madrid: loaded in 274 ms Warsaw: loaded in 302 ms St. Louis: loaded in 231 ms Querétaro: loaded in 368 ms Portsmouth: loaded in 339 ms Los Angeles: loaded in 440 ms Seattle: loaded in 390 ms Delhi: loaded in 461 ms London: loaded in 313 ms Osaka: loaded in 682 ms Dallas: loaded in 275 ms Cape Town: loaded in 352 ms Port Louis: loaded in 1547 ms Seoul: loaded in 412 ms Singapore: loaded in 682 ms Sydney: loaded in 596 ms Tel Aviv: loaded in 507 ms Melbourne: loaded in 674 ms Hamina: loaded in 356 ms Frankfurt: loaded in 188 ms Bangalore: loaded in 766 ms Toronto: loaded in 169 ms Tokyo: loaded in 804 ms Amsterdam: loaded in 266 ms
  • JakartaReachable370 ms, 3 min ago
  • DohaReachable719 ms, 3 min ago
  • São PauloReachable213 ms, 3 min ago
  • SantiagoReachable836 ms, 3 min ago
  • Hong KongReachable693 ms, 3 min ago
  • JohannesburgReachable430 ms, 3 min ago
  • LauterbourgReachable237 ms, 3 min ago
  • New JerseyReachable167 ms, 3 min ago
  • New YorkReachable194 ms, 3 min ago
  • MumbaiReachable593 ms, 3 min ago
  • AtlantaReachable218 ms, 4 min ago
  • MadridReachable274 ms, 4 min ago
  • WarsawReachable302 ms, 4 min ago
  • St. LouisReachable231 ms, 4 min ago
  • QuerétaroReachable368 ms, 4 min ago
  • PortsmouthReachable339 ms, 4 min ago
  • Los AngelesReachable440 ms, 4 min ago
  • SeattleReachable390 ms, 4 min ago
  • DelhiReachable461 ms, 4 min ago
  • LondonReachable313 ms, 4 min ago
  • OsakaReachable682 ms, 4 min ago
  • DallasReachable275 ms, 4 min ago
  • Cape TownReachable352 ms, 4 min ago
  • Port LouisReachable1547 ms, 5 min ago
  • SeoulReachable412 ms, 5 min ago
  • SingaporeReachable682 ms, 5 min ago
  • SydneyReachable596 ms, 5 min ago
  • Tel AvivReachable507 ms, 5 min ago
  • MelbourneReachable674 ms, 5 min ago
  • HaminaReachable356 ms, 5 min ago
  • FrankfurtReachable188 ms, 5 min ago
  • BangaloreReachable766 ms, 5 min ago
  • TorontoReachable169 ms, 5 min ago
  • TokyoReachable804 ms, 5 min ago
  • AmsterdamReachable266 ms, 5 min ago

This is separate from the status page: we request slack.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Slack

Slack Status
  • Login/SSOOperational
  • ConnectivityOperational
  • MessagingOperational
  • NotificationsOperational
  • SearchOperational
  • FilesOperational
  • HuddlesOperational
  • CanvasesOperational
  • ListsOperational
  • WorkflowsOperational
  • Apps/Integrations/APIsOperational
  • Workspace/Org AdministrationOperational

Incidents and maintenance

No open incidents or planned maintenance.

Outage history

No problems recorded since 2 Nov 2026.

Last 9030 days

100.00% of the time without a reported outage, since 2 Nov

Of the last 90 days, 0 had a partial or major outage, 0 had maintenance only and 84 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

No problems recorded since 2 Nov 2026.

What can I try?

Having trouble with Slack?

  1. Compare reports from Svalbard and Jan Mayen and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Slack down, or is it just me?

The Slack status page reports no problem and our own checks reach slack.com. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

We read the official Slack status page and load slack.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 2.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Other services in Communication

Each card shows that service's own status, not Slack's. A problem listed here does not mean Slack has one.

See the live outage feed for Svalbard and Jan Mayen · Find another service