Skip to main content
Apify

Elevated errors in Actor runs

Partial outage Lasted 0m · started · Apify's page

Level
confirmed
Worst impact
Partial outage
Down Index
29of 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 2026-09-22 15:06 UTC and 2026-09-22 14:30 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

  1. resolved

    Some Actor runs were experiencing degraded performance, slower start and finish times, and elevated error rates. The issue is resolved.

    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-f77cb12196

Is Apify still down?

No, this incident was resolved 2026-09-22 14:30 UTC. For Apify's live state, see https://down.guide/apify.

How long did it last?

0m, from 2026-09-22 15:06 UTC to 2026-09-22 14:30 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.