🟢 Operational
Incident: Scheduled Grid Migrations are experiencing extended downtime
Resolved
- Started
- 2026-05-08 17:44 UTC
136 days ago - Last update
- 2026-05-08 17:44 UTC
136 days ago - Duration
- 0s
Timeline
-
08 May · 17:44 UTC
🟡 Resolved
rss
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.
-
08 May · 17:44 UTC
🟡 Resolved
rss
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.
Source
Official Slack status — view original incident ↗
IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.