Slack Outage History

Slack degraded · 1 active incident View live status →

Slack had 60 outages in the last 2 years totaling 1156h 25m of downtime — averaging 2.5 incidents per month.

There were 60 Slack outages since November 20, 2025 totaling 1156h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://slack-status.com

Minor January 22, 2026

Trouble loading Slack and performing actions

Detected by Pingoru
Jan 22, 2026, 07:43 PM UTC
Resolved
Jan 23, 2026, 12:13 AM UTC
Duration
4h 29m
Affected: Apps/Integrations/APIs
Timeline · 3 updates
  1. investigating Jan 22, 2026, 07:43 PM UTC

    Some users are having trouble performing certain actions related to App Management, such as; Create New App from https://api.slack.com/appsShow button to reveal the client secret Unable to install or delete internal appAttempting to edit event subscriptions, Enable Events view has an indefinite loading wheelThank you for your patience while we continue to investigate the situation.

  2. identified Jan 22, 2026, 08:28 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: We have identified the cause and are working on a fix.We'll be back with another update once we have news to share.

  3. resolved Jan 22, 2026, 10:18 PM UTC

    This issue is now resolved for all users. Current status and recent actions taken: We have completed deployment of a fix for this issue.Previous impact to end users: Some users were having trouble performing certain actions related to App ManagementRequired resolution steps: No additional steps are required from users.We apologize for any disruptions to your day.

Read the full incident report →

Minor January 15, 2026

Trouble loading Slack, messages, or canvas

Detected by Pingoru
Jan 15, 2026, 07:41 PM UTC
Resolved
Jan 15, 2026, 07:58 PM UTC
Duration
16m
Affected: ConnectivityMessagingCanvases
Timeline · 1 update
  1. resolved Jan 15, 2026, 07:41 PM UTC

    This issue is now resolved. Current status and recent actions taken: Affected users may have experienced performance issues in Slack.Scope: This issue did not affect any specific region, but a small percentage of users may have been impacted globally.Previous impact to end users: The majority of errors were retired successfully, but small number of users may have experienced errors when performing various tasks in Slack. Required resolution steps: No steps required. We apologize for any disruptions to your day

Read the full incident report →

Minor December 24, 2025

Issue loading threads in Slack

Detected by Pingoru
Dec 24, 2025, 12:33 AM UTC
Resolved
Dec 29, 2025, 05:49 PM UTC
Duration
5d 17h
Affected: Messaging
Timeline · 3 updates
  1. investigating Dec 24, 2025, 12:33 AM UTC

    We are aware of an issue currently impacting threads. Our teams are investigating, and we will provide more information as soon as it’s available. We regret any inconvenience this is causing.

  2. resolved Dec 24, 2025, 02:04 AM UTC

    This issue is now resolved for all users. Current status and recent actions taken: Threads should now load normally for all impacted users. To restore normal thread performance, we redirected traffic away from the affected database shard and then scaled up its capacity.Scope: A small number of users may have had trouble with threads.Previous impact on end users: Threads may have failed to load or resulted in a "Something's fishy!" error message.Required resolution steps: No additional steps are necessary.We apologize for any inconvenience this may have caused to your day

  3. resolved Dec 29, 2025, 05:49 PM UTC

    Between 1:05 PM and 5:26 PM PST on December 23, 2025, some users may have encountered a "Something's fishy!" error when attempting to load message threads. We traced this to a backend job that consumed an excessive amount of system resources, leading to a portion of a database becoming unresponsive. To mitigate, we optimized the resource allocation for these background tasks and restarted the affected database segments, resolving the issue for affected users.

Read the full incident report →

Minor December 15, 2025

Trouble running workflows

Detected by Pingoru
Dec 15, 2025, 05:14 PM UTC
Resolved
Dec 18, 2025, 04:57 PM UTC
Duration
2d 23h
Affected: Apps/Integrations/APIsWorkflows
Timeline · 4 updates
  1. investigating Dec 15, 2025, 05:14 PM UTC

    Users may experience issues when attempting to trigger a workflow using the Jira Cloud connector. We're investigating and will let you know as soon as we have more information.

  2. identified Dec 15, 2025, 06:25 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Jira Cloud workflow connector is experiencing failures where Get Domain URL and List Atlassian Domains API calls are running into '500 errors'.Create issue functionality is also failing with '400 errors'.The investigation into the cause of these errors is ongoing.We'll be back with another update as soon as we have news to share.

  3. resolved Dec 15, 2025, 09:51 PM UTC

    This issue is now resolved for all users. Current status and recent actions taken: This incident is considered all clear and required no action to be taken by Slack to alleviate the problem.Scope: We have determined that this issue was related to an incident experienced by the vendor, and it is now resolved.Previous impact to end users: Users experienced issues when attempting to trigger a workflow using the Jira Cloud connector.Required resolution steps: No additional steps are necessary.We apologize for any inconvenience this may have caused to your day.

  4. resolved Dec 18, 2025, 04:57 PM UTC

    Starting at around 7:00 AM until 12:10 PM PST on December 15, 2025, some users may have experienced issues triggering or using workflows containing the Jira connector or the Jira Cloud app in Slack. An upstream provider encountered an issue that resulted in trouble using the Jira connector. Once the upstream provider resolved the issue, the app returned to normal functionality.

Read the full incident report →

Minor December 8, 2025

Issues loading or viewing threads

Detected by Pingoru
Dec 08, 2025, 11:23 PM UTC
Resolved
Dec 18, 2025, 04:44 PM UTC
Duration
9d 17h
Affected: Messaging
Timeline · 5 updates
  1. investigating Dec 08, 2025, 11:23 PM UTC

    We are aware of an issue currently impacting threads. Our teams are investigating, and we will provide more information as soon as it’s available. We’re very sorry for any inconvenience this is causing.

  2. resolved Dec 09, 2025, 06:55 AM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: We have no additional news to share at this time, but we’re focused on getting things back to normal as quickly as possible.We'll be back with another update as soon as we have news to share.

  3. resolved Dec 09, 2025, 04:55 PM UTC

    We've identified the cause of the issue and implemented a fix. We're currently monitoring internal health metrics & user reports, but will provide an update once we've determined this issue is fully resolved. We appreciate your patience as we sort this out.

  4. investigating Dec 09, 2025, 05:34 PM UTC

    We've resolved the issue with threads not loading for some users. We apologize for any disruptions to you day.

  5. identified Dec 18, 2025, 04:44 PM UTC

    From 7:12 AM to 4:50 PM PST on December 8, 2025, some users encountered a "Something's fishy!" error when loading threads or experienced delays or a blank screen when loading specific channels in Slack. We identified the cause as a recent configuration change that triggered unexpected rate limiting on backend components responsible for fetching message data for threads. We reverted the problematic change, resolving the issue for all users.

Read the full incident report →

Major December 4, 2025

Slack Canvas Outage

Detected by Pingoru
Dec 04, 2025, 11:43 PM UTC
Resolved
Dec 05, 2025, 12:02 AM UTC
Duration
18m
Affected: Canvases
Timeline · 1 update
  1. resolved Dec 04, 2025, 11:43 PM UTC

    Between 2:08 PM PST and 2:34 PM PST on December 4, 2025, some users may have experienced 500 errors when trying to open a Canvas. Current status and recent actions taken: We have resolved the issue by reverting a web cache configuration setting that was causing the disruption. Users should no longer be experiencing trouble connecting to or loading Canvases in Slack.Scope: This issue did not affect any specific region, but a percentage of users may have been impacted globally.Previous impact to end users: Users experienced issues loading and accessing Canvases.Required resolution steps: NoneThis issue is now resolved for all users. We’re sorry for the disruption we brought to your day.

Read the full incident report →

Minor November 28, 2025

Slack login, workspaces loading failures, and general Slack functionality issues

Detected by Pingoru
Nov 28, 2025, 10:44 AM UTC
Resolved
Dec 01, 2025, 05:19 PM UTC
Duration
3d 6h
Affected: Connectivity
Timeline · 6 updates
  1. investigating Nov 28, 2025, 10:44 AM UTC

    We are currently investigating an issue where a subset of users may be unable to log into Slack or use certain features. We apologise for the inconvenience and will provide another update as soon as we have more details to share.

  2. identified Nov 28, 2025, 11:16 AM UTC

    We have identified an unhealthy database that is contributing to the current issue. We are working on restoring the database to a healthy state, which we anticipate will resolve the problem. We will update you as soon as we have more information.

  3. investigating Nov 28, 2025, 11:46 AM UTC

    We are actively working to resolve the current platform functionality issues, which have evolved to include connectivity problems, workspace loading failures, and server errors for some users. Our current efforts remain focused on restoring the unhealthy database identified earlier. We will update you as soon as we have more information.

  4. investigating Nov 28, 2025, 12:18 PM UTC

    We’ve also noticed instances getting out of memory errors, causing system instability. We are provisioning the service to larger and more stable servers. We continue to monitor everything for stability. We will update you as soon as we have more information.

  5. investigating Nov 28, 2025, 12:54 PM UTC

    Service has been fully restored for all affected users. The database connection issue, which was caused by high memory usage, was resolved by upscaling server capacity. All Slack features and functionalities are now loading correctly. We apologize for the disruption and thank you for your patience while we resolved this incident.

  6. resolved Dec 01, 2025, 05:19 PM UTC

    Starting around 1:45 AM PST until 4:30 AM PST on November 28, 2025, some users encountered connectivity issues, including difficulty accessing and loading their workspaces and receiving "Server error" messages. We traced this issue to a backend database service reaching unexpected capacity limits, which led to a spike in error rates and request timeouts. We immediately increased capacity limits for the affected databases, restoring full functionality and service stability to all impacted services.

Read the full incident report →