Apify: Degraded Console UI and API performance

What to do

Check whether you use Apify Console (console.apify.com), API (api.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 33m it lasted.
Anything that failed between 2026-05-01 11:23 UTC and 2026-05-01 11: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.

identifiedMay 1, 2026, 11:23 AM UTC
We have identified an issue causing degraded performance in the Console UI and in some API requests. We have implemented a fix, and the performance should stabilize soon.
provider
monitoringMay 1, 2026, 11:29 AM UTC
Console UI and API performance should be back to standard levels. We will monitor the situation while we investigate the incident's root cause.
provider
resolvedMay 1, 2026, 11:57 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Apify still down?

No, this incident was resolved 2026-05-01 11:57 UTC. For Apify's live state, see https://down.guide/apify.

How long did it last?

33m, from 2026-05-01 11:23 UTC to 2026-05-01 11:57 UTC, by the times Apify posted.

What was affected?

Apify named Console (console.apify.com), API (api.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.