- Level
- confirmed
- Worst impact
- Degraded
- Components
- Actors
- Down Index
- 30of 100
What to do
Check whether you use Apify Actors. 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 1h 4m it lasted.
Anything that failed between 2026-07-26 06:53 UTC and 2026-07-26 07:57 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
- investigating
Actor Standby mode has a higher error rate and may require more retries than usual. We are investigating the cause. https://docs.apify.com/actors/running/standby
provider
- resolved
The problem has been resolved. Impact was an increased error rate at the Actor Standby API, not other component was affected. There was no downtime during the period of the 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-fbf02fe87c
Is Apify still down?
No, this incident was resolved 2026-07-26 07:57 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
1h 4m, from 2026-07-26 06:53 UTC to 2026-07-26 07:57 UTC, by the times Apify posted.
What was affected?
Apify named Actors.
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.