- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on Apify. 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 2025-09-15 12:38 UTC and 2025-09-15 12:38 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 1
- resolved
The latest version of the apify/send-mail Actor failed to email all recipients. The issue lasted from around 13:50 to 14:05 CEST. The root cause was identified, and the service of the Actor was restored. We apologize for any inconvenience this might have caused. We take this problem seriously and will take steps to prevent such issues from occurring in the future.
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-18795aaee3
Is Apify still down?
No, this incident was resolved 2025-09-15 12:38 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
0m, from 2025-09-15 12:38 UTC to 2025-09-15 12:38 UTC, by the times Apify posted.
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.