- Level
- confirmed
- Worst impact
- Degraded
- Components
- Down Index
- 9of 100
What to do
Check whether you use Composio INSTAGRAM. 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-02 20:07 UTC and 2026-10-02 20:07 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 34 minutes Affected Components: INSTAGRAM Oct 2, 21:40:32 GMT+0 - Resolved - All instagram accounts connected before August 3 got expired. We have fixed the issue in our refresh logic for instagram. For older accounts, user need to reauthenticate. Oct 2, 20:40:45 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 2, 20:07:00 GMT+0 - Identified - We are continuing to work on a fix for 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-d151307626
Is Composio still down?
No, this incident was resolved 2026-10-02 20:07 UTC. For Composio's live state, see https://down.guide/composio.
How long did it last?
0m, from 2026-10-02 20:07 UTC to 2026-10-02 20:07 UTC, by the times Composio posted.
What was affected?
Composio named INSTAGRAM.
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.