Is Apify down?
Last checked 5m agoNo incidents right now.
Apify is operational right now. Last checked 5m ago; the most recent incident resolved 3d ago.
Real-time Apify status, recent outages, and incident history — pulled directly from Apify's official status page at https://status.apify.com every 5 minutes. Pingoru tracks 26 Apify services and has captured 10 incidents in the last 90 days (98.76% uptime). Get email, Slack, Discord, or webhook alerts the moment Apify reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Actors
Timeline · 2 updates
- investigating · Jul 26, 2026, 06:53 AM UTC
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
- resolved · Jul 26, 2026, 07:57 AM UTC
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.
Latest: 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 inciden…
-
- API (api.apify.com)Actors
Timeline · 10 updates
- identified · Jul 21, 2026, 02:49 PM UTC
We are currently investigating timing out operations on our API caused by slow database operations due to cluster changes.
- identified · Jul 21, 2026, 04:43 PM UTC
Slow database operations continue to impact our systems. API performance has improved, but Actor runs are currently timing out due to reduced worker capacity.
- identified · Jul 21, 2026, 05:09 PM UTC
We are continuing to work on a fix for this issue.
- monitoring · Jul 21, 2026, 05:11 PM UTC
We are now monitoring the situation. Worker capacity improved and is now able to handle starting Actor runs.
- investigating · Jul 21, 2026, 05:47 PM UTC
Our database cluster performance has further degraded, and the whole platform is facing a major outage. We will keep informing you as the situation progresses.
- identified · Jul 21, 2026, 08:33 PM UTC
We have identified the issue and are working towards recovery. The system is operational, but the capacity is capped, resulting in Actor runs being buffered in the "ready" state and a large portion of them timing out.
- identified · Jul 21, 2026, 08:34 PM UTC
We are continuing to work on a fix for this issue.
- identified · Jul 21, 2026, 08:52 PM UTC
Actors are now fully operational, and the system is processing all the runs in time.
- monitoring · Jul 21, 2026, 09:28 PM UTC
All systems are operational. We expect the database to fully recover in 4 hours (1 am UTC). We are monitoring the platform's performance. We apologize for any inconvenience this might have caused.
- resolved · Jul 22, 2026, 02:38 AM UTC
The database is fully recovered, and all systems are operational. We apologize for any inconvenience this might have caused. We are currently implementing new measures to ensure this won't happen again.
Latest: The database is fully recovered, and all systems are operational. We apologize for any inconvenience this might have caused. We are currently implementing new measures to ensure th…
-
- Actors
Timeline · 4 updates
- investigating · Jul 21, 2026, 06:52 AM UTC
A higher-than-usual number of Actor runs are being migrated between servers, which may cause brief interruptions or restarts for some runs. We are currently investigating the issue.
- identified · Jul 21, 2026, 06:57 AM UTC
The cause of the elevated Actor run migrations has been identified. We are resolving the cause.
- monitoring · Jul 21, 2026, 07:21 AM UTC
A fix has been applied and Actor run migrations are returning to normal. We apologize for any inconvenience this might have caused. We take this problem seriously and will be taking steps to avoid such issues occurring in the future.
- resolved · Jul 21, 2026, 11:53 AM UTC
All systems are operational, and we apologize for any inconvenience this might have caused.
Latest: All systems are operational, and we apologize for any inconvenience this might have caused.
-
- SERP
Timeline · 2 updates
- investigating · Jul 17, 2026, 02:04 PM UTC
We're seeing degraded performance of Google SERP requests. Responses may take longer than usual. We're investigating the issue.
- resolved · Jul 17, 2026, 08:08 PM UTC
The issue has been resolved. Both the response time and success rate have returned to normal levels.
Latest: The issue has been resolved. Both the response time and success rate have returned to normal levels.
-
- Webhooks
Timeline · 4 updates
- investigating · Jun 04, 2026, 03:07 PM UTC
We're investigating the issue.
- identified · Jun 04, 2026, 03:29 PM UTC
The issue has been identified, and we are resolving it.
- monitoring · Jun 04, 2026, 03:34 PM UTC
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.
- resolved · Jun 04, 2026, 05:07 PM UTC
Webhooks are operational, and we apologize for any inconvenience this might have caused.
Latest: Webhooks are operational, and we apologize for any inconvenience this might have caused.
-
See the full Apify outage history
5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Apify outage history →Or sign up free to get alerts when Apify breaks · 10 free monitors · No credit card
- Started Jul 26, 2026, 06:53 AM UTC · Resolved Jul 26, 2026, 07:57 AM UTC · 1h 4m
- Started Jul 21, 2026, 02:49 PM UTC · Resolved Jul 22, 2026, 02:38 AM UTC · 11h 49m
- High number of Actor run migrations ResolvedStarted Jul 21, 2026, 06:52 AM UTC · Resolved Jul 21, 2026, 11:53 AM UTC · 5h 1m
- Degraded SERP performance ResolvedStarted Jul 17, 2026, 02:04 PM UTC · Resolved Jul 17, 2026, 08:08 PM UTC · 6h 3m
- Degraded performance of webhooks ResolvedStarted Jun 04, 2026, 03:07 PM UTC · Resolved Jun 04, 2026, 05:07 PM UTC · 1h 59m
- Started May 15, 2026, 11:48 AM UTC · Resolved May 16, 2026, 05:28 AM UTC · 17h 39m
- Proxy degradation ResolvedStarted May 14, 2026, 07:20 AM UTC · Resolved May 14, 2026, 07:20 AM UTC · —
- Started May 06, 2026, 08:08 PM UTC · Resolved May 07, 2026, 08:27 AM UTC · 12h 18m