- Level
- confirmed
- Worst impact
- Degraded
- Components
- MCP server (mcp.apify.com)
- Down Index
- 35of 100
What to do
Check whether you use Apify MCP server (mcp.apify.com). 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 12h 18m it lasted.
Anything that failed between 2026-05-06 20:08 UTC and 2026-05-07 08:27 UTC may need a replay.Subscribe to Apify's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=apify works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Apify 2
- identified
OAuth sign-in to mcp.apify.com from clients using CIMD with loopback redirects (currently Claude Code) is failing due to a regression. Existing connections and other clients (claude.ai, Cursor, Codex) are unaffected (the later use DCR). We are sorry for the inconvenience and working on a fix.
provider
- resolved
We have implemented a fix for the OAuth flow, and the connections are now working normally.
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-645d9c764a
Is Apify still down?
No, this incident was resolved 2026-05-07 08:27 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
12h 18m, from 2026-05-06 20:08 UTC to 2026-05-07 08:27 UTC, by the times Apify posted.
What was affected?
Apify named MCP server (mcp.apify.com).
What caused it?
Apify hasn't published a root cause. If it does, it shows here.
Where does this come from?
Apify's official status page, https://status.apify.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.