Operational incident.io status
incident.io · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread incident.io problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Google Cloud: no issues
- CISA KEV (context) no recent entries for this vendor
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 9 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Disruption to Slack incident channels and messages”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside incident.io's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
incident.io may run on Google Cloud (inferred). We don't map other services that depend on incident.io. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on incident.io or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers incident.io may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with incident.io. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Disruption to Slack incident channels and messages
major resolved · started · resolved
6 updates
- investigating
We’re investigating an issue where Slack incident channels are not being created when new incidents are declared. Some Slack actions (such as posting messages or renaming channels) are also failing. Incidents remain available in the incident.io dashboard while we work to resolve this.
- investigating
A Slack outage is causing failures when creating incident channels and posting messages in Slack. We’ve reached out to Slack for assistance. You can follow their updates on [Slack’s status page](https://slack-status.com/2026-11/b8bb993128ac94f5). Incidents remain available in the incident.io dashboard.
- monitoring
Slack incident channel creation and message delivery both appear to be recovering. We’re continuing to monitor the situation. You can follow Slack's updates on [their status page](https://slack-status.com/2026-11/b8bb993128ac94f5).
- monitoring
Slack incident channel creation and message delivery appear to have recovered. We’re continuing to monitor the situation to ensure this recovery holds. You can follow Slack’s updates on [their status page](https://slack-status.com/2026-11/b8bb993128ac94f5).
- monitoring
We're no longer seeing errors creating Slack channels or delivering messages. We are continuing to monitor the situation to ensure this recovery holds. You can follow Slack’s updates on [their status page](https://slack-status.com/2026-11/b8bb993128ac94f5).
- resolved
Slack have now marked their incident as resolved, and we’re continuing to see normal performance for the Slack app in incident.io. For further information on the outage, please see [Slack's status page](https://slack-status.com/2026-11/b8bb993128ac94f5).
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.