- Level
- confirmed
- Worst impact
- Degraded
- Components
- Webhooks
- Down Index
- 31of 100
What to do
Check whether you use Apify Webhooks. 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 2h it lasted.
Anything that failed between 2026-06-04 15:07 UTC and 2026-06-04 17:07 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 4
- investigating
We're investigating the issue.
provider
- identified
The issue has been identified, and we are resolving it.
provider
- monitoring
We have identified and resolved the root cause of the issue. No data loss occurred, as all webhooks are automatically retried. A backlog of pending webhooks remains and is currently being processed. We are monitoring the situation closely.
provider
- resolved
Webhooks are operational, and we apologize for any inconvenience this might have caused.
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-e4c0bc0ae5
Is Apify still down?
No, this incident was resolved 2026-06-04 17:07 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
2h, from 2026-06-04 15:07 UTC to 2026-06-04 17:07 UTC, by the times Apify posted.
What was affected?
Apify named Webhooks.
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.