- Level
- confirmed
- Worst impact
- Degraded
- Components
- Composio Connect MCP
- Down Index
- 9of 100
What to do
Check whether you use Composio Composio Connect MCP. 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-10-30 05:20 UTC and 2026-10-30 05:20 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: 7 hours Affected Components: Composio Connect MCP Oct 30, 05:27:00 GMT+0 - Resolved - Between 05:20 and 05:27 UTC on 30 October, requests to Composio Connect MCP returned errors, and users could not start or use MCP sessions. The cause was a faulty deployment, which we rolled back at 05:27 UTC. A permanent fix has been deployed since. Oct 30, 05:20:00 GMT+0 - Identified -
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-b68eb050a6
Is Composio still down?
No, this incident was resolved 2026-10-30 05:20 UTC. For Composio's live state, see https://down.guide/composio.
How long did it last?
0m, from 2026-10-30 05:20 UTC to 2026-10-30 05:20 UTC, by the times Composio posted.
What was affected?
Composio named Composio Connect MCP.
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.