outages.live
Live
incident.ioIncident · 2026-10-02 22:33 UTC

Login errors for subset of Slack Enterprise Grid customers

ResolvedOfficial update

This incident has been resolved. Login via Slack is operating normally again, and no further action is required.

The latest update from incident.io.

State

Resolved

Started

30 d ago

2026-10-02 22:33 UTC

Lasted

1 h 14 min

until 2026-10-02 23:47 UTC

Worst impact

Degraded

Timeline

2 updates
22:3322:5123:1023:2823:47
DegradedUpdate postedTimes in UTC

Identified

1 h 14 min 100%

Updates

Times in UTC

As posted by incident.io

Resolved2026-10-02 23:47 UTC

This incident has been resolved. Login via Slack is operating normally again, and no further action is required.

Identified2026-10-02 22:33 UTC

Some customers on Slack Enterprise Grid who sign in with Slack are seeing Slack-originating errors when logging in. We've raised this with Slack and are monitoring for a fix. Customers using SAML sign-in aren't affected. Alert ingestion and our On-call product's paging functionality are unaffected.

incident.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

1 h 31 min

This incident

19% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

1 h 49 min
median 1 h 31 min
90 days agoToday

Other incident.io incidents

All incidents

incident.io·Increased latency in Microsoft Teams

Latency has now returned to normal. Between 13:00 and 15:08 UTC there were periods of increased latency from some Microsoft APIs. Messages in Microsoft Teams were delivered with increased latency. Our dashboard and mobile app were not affected.

Resolvedresolved 73 d ago

Follow incident.io

Your coding agent knows when incident.io is down, and tells you when a failure is theirs, not yours. You can also get incident.io incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "incidentio" and tell me if incident.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=incidentio
Slack
/feed subscribe https://outages.live/feed.xml?providers=incidentio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane