Slack incident

Scheduled Grid Migrations are experiencing extended downtime

Slack experienced a major incident on May 8, 2026 affecting Connectivity, lasting 5h 30m. The incident has been resolved; the full update timeline is below.

Started: May 08, 2026, 12:13 PM UTC
Resolved: May 08, 2026, 05:44 PM UTC
Duration: 5h 30m
Detected by Pingoru: May 08, 2026, 12:13 PM UTC

Affected components

Connectivity

Update timeline

identified May 08, 2026, 12:13 PM UTC

Users who are undergoing scheduled Grid Migrations are experiencing extended downtime. Downtime is expected during a Grid Migration however it's taking longer than usual. During the downtime users are unable to access Slack until the migration completes. We've identified an issue with Job Queues, which may be the cause and are investigating this further. The next update will be provided once additional information becomes available.
resolved May 08, 2026, 05:44 PM UTC

This issue is now resolved. Current status and actions being taken: We identified database write throttling as the cause of the stalled grid migrations. We applied a drop rule for jobs that were stuck in a retry loop, which has restored normal migration processing. Scope: A small number of enterprise users undergoing grid migrations experienced extended delays in accessing Slack. Current impact to end users: Affected users may have experienced an inability to access Slack during their migration window. Known workarounds: No workarounds needed at this time.We apologize for how this incident affected you and your business.