- Level
- confirmed
- Worst impact
- Degraded
- Components
- Triggers V2, v3 API, Triggers V1
- Down Index
- 10of 100
What to do
Check whether you use Composio Triggers V2, v3 API, Triggers V1. 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-08-24 10:00 UTC and 2026-08-24 10: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: 1 hour and 29 minutes Affected Components: Triggers V2, v3 API, Triggers V1 Aug 24, 11:29:15 GMT+0 - Resolved - This incident has been resolved. Our latency numbers are looking good and slack triggers continue to work now. Aug 24, 11:00:44 GMT+0 - Monitoring - Slack triggers are turned off as part of remediation of platform latencies. Aug 24, 10:16:53 GMT+0 - Investigating - We are currently investigating this incident. Aug 24, 10:00:00 GMT+0 - Investigating - We are currently investigating this incident.
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-7033461a79
Is Composio still down?
No, this incident was resolved 2026-08-24 10:00 UTC. For Composio's live state, see https://down.guide/composio.
How long did it last?
0m, from 2026-08-24 10:00 UTC to 2026-08-24 10:00 UTC, by the times Composio posted.
What was affected?
Composio named Triggers V2, v3 API, Triggers V1.
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.