Slack Outage History

Slack's Messaging component briefly degraded, with the incident spanning from 5:29 PM UTC to 5:59 PM UTC. The outage lasted about 30 minutes, and the Messaging service returned to full operation after the window. Slack published two status updates during the event to acknowledge the degraded state and confirm recovery.

Slack experienced a brief degradation in search functionality beginning at 4:24 PM UTC, with some searches not completing or returning partial results and organization/workspace dashboards may not load correctly. The issue was acknowledged with updates from Slack and resolved by 4:49 PM UTC after about 25 minutes. The incident included 2 status updates and primarily affected the search component and related dashboards.

Slack experienced a brief issue with custom built-in internal apps, causing errors for users relying on Apps/Integrations/APIs. The outage began at 12:04 AM UTC and was resolved by 12:49 AM UTC, lasting about 45 minutes. The incident was limited to internal apps and integrations, with affected components including custom apps and related APIs. Slack's status page documented the issue as an initial advisory followed by confirmation of resolution, and the incident included two official status updates.

Slack experienced degraded search performance starting at 9:34 PM UTC, with slowness affecting AI search summaries and general search results. The issue appeared to be isolated to the Search component, and users may have experienced delays when performing searches. The degradation persisted for about 1 hour and 55 minutes, until 11:29 PM UTC. Slack issued two official status updates during the incident describing the problem and later confirming recovery. The impact was primarily on search functionality, with other features remaining generally available. User feedback indicated a small amount of reports of search slowness as the incident progressed.

Slack users on desktop and web experienced a grey screen when attempting to edit their profile, and the profile editing menu did not load. This prevented changes to profile fields such as name pronunciation and pronouns, and affected Windows and macOS clients while the mobile apps remained unaffected.

According to Slack's status updates, the issue began at Sep 23, 2025 1:04 PM UTC and was resolved by Sep 23, 2025 1:54 PM UTC, lasting about 50 minutes. The incident affected the Apps/Integrations/APIs component and Slack issued two status updates during the event.

Slack's Apps/Integrations/APIs component experienced a brief degraded performance beginning at 1:14 PM UTC and restored by 2:04 PM UTC. The incident affected app integrations and API-related features, potentially impacting workflows relying on Slack apps or external API calls. The Slack status page issued two updates during the incident documenting the degradation and the recovery, with impact confined to the Apps/Integrations/APIs component and no broader Slack service disruption.

Slack experienced a brief connectivity issue affecting loading of Slack.com, with some users seeing a server error when trying to access the site. The incident began at 7:44 PM UTC and was resolved by 8:29 PM UTC. Slack's Connectivity component was listed as degraded during the outage and the company issued two status updates as it investigated and restored service. The outage lasted about 45 minutes, with no broader impact indicated beyond the loading problems.

Slack's Notifications component experienced an Activity badge display issue where the unread badge persisted after all messages were read, causing confusion for users across Slack clients. The incident began on Sep 16, 2025 6:14 AM UTC and lasted for about 1 day and 13 hours, with the badge returning to normal on Sep 17, 2025 7:29 PM UTC as services stabilized.

Slack experienced a user-facing issue in the Activity badge display within the Notifications component, causing the unread count to persist after messages were read and potentially confusing users. The incident was classified as a degraded notification experience, with Slack actively investigating and providing updates as it worked to restore normal badge behavior. The issue began at Sep 12, 2025 6:09 AM UTC and was resolved by Sep 12, 2025 5:54 PM UTC, lasting about 11 hours and 45 minutes. Slack issued two status updates during the incident.

Slack reported issues opening the iOS app (version 25.09.10), with an error indicating jailbroken devices are blocked from accessing Slack for security reasons. This resulted in a partial outage for iOS users as the Login/SSO flow could not be completed. The incident began at Sep 3, 2025 9:04 PM UTC and was resolved by Sep 4, 2025 12:49 AM UTC.

Slack communicated via status updates, first flagging the problem and listing Login/SSO as affected, then restoring normal service after fixes were applied. The disruption lasted several hours, with two official status updates issued over the course of the incident.