Skip to main content
incident.io

Degraded performance with @incident chat

Degraded Lasted 27m · started · incident.io's page

Level
confirmed
Worst impact
Degraded
Down Index
16of 100

What to do

  • Check whether your product depends on incident.io. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 27m it lasted.

    Anything that failed between 2025-11-20 11:47 UTC and 2025-11-20 12:14 UTC may need a replay.
  • Subscribe to incident.io's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=incident-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from incident.io 2

  1. identified

    We are experiencing degraded performance from some of our LLM model providers, causing error responses from @incident. /inc commands remain unaffected. More info on [Anthropic's status page](https://status.claude.com/incidents/xbbf1wq2dlz7 "Anthropic's status page")

    provider

  2. resolved

    We have resolved the degraded performance affecting @incident chat. This issue was caused by an overload from one of our AI model providers, which led to intermittent errors when using AI actions such as generating summaries or drafting updates. \inc commands were unaffected during this time. We have confirmed that the provider's issue has been resolved and all @incident chat features are now functioning normally.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-70f96a3309

Is incident.io still down?

No, this incident was resolved 2025-11-20 12:14 UTC. For incident.io's live state, see https://down.guide/incident-io.

How long did it last?

27m, from 2025-11-20 11:47 UTC to 2025-11-20 12:14 UTC, by the times incident.io posted.

What caused it?

incident.io hasn't published a root cause. If it does, it shows here.

Where does this come from?

incident.io's official status page, https://status.incident.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.