# Degraded performance with @incident chat

- Provider: [incident.io](https://down.guide/incident-io)
- Level: confirmed
- Impact: Degraded
- lasted 27m
- started 2025-11-20 11:47 UTC
- id: DWN-70f96a3309
- Official page: https://status.incident.io/incidents/01KAGHEJEPHDWWXRQXTKN6JQ3H

## Updates from incident.io
### 2025-11-20 11:47 UTC: 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")

### 2025-11-20 12:14 UTC: 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.

From the builder: does your app depend on incident.io? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=incident-io) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention incident.io.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-70f96a3309), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.