- Level
- confirmed
- Worst impact
- Degraded
- Components
- MCP Servers
- Down Index
- 9of 100
What to do
Check whether you use Composio MCP Servers. 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 0m it lasted.
Anything that failed between 2026-06-11 11:00 UTC and 2026-06-11 11:00 UTC may need a replay.Subscribe to Composio's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=composio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Composio 1
- resolved
Type: Incident Duration: 4 hours Affected Components: MCP Servers Jun 11, 15:00:00 GMT+0 - Resolved - This incident has been resolved. Jun 11, 11:00:00 GMT+0 - Investigating - We are investigating elevated errors on the MCP Servers endpoint (backend.composio.dev/v3/mcp). Some requests may fail. Sessions (Tool Router) and the rest of the v3 API are not affected. We will share an update shortly.
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-c3c4768ce2
Is Composio still down?
No, this incident was resolved 2026-06-11 11:00 UTC. For Composio's live state, see https://down.guide/composio.
How long did it last?
0m, from 2026-06-11 11:00 UTC to 2026-06-11 11:00 UTC, by the times Composio posted.
What was affected?
Composio named MCP Servers.
What caused it?
Composio hasn't published a root cause. If it does, it shows here.
Where does this come from?
Composio's official status page, https://status.composio.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.