# Apify API Degraded Performance

- Provider: [Apify](https://down.guide/providers/apify)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 23h 15m
- started 2026-04-08 10:01 UTC
- Console (console.apify.com), API (api.apify.com), Actors
- Apify states the impact was 2026-04-08 10:00 to 20:30 UTC (10h 30m), and 2026-04-08 20:30 to 21:10 UTC (40m)
- id: DWN-2af40d537f
- Official page: https://stspg.io/rxntglghgn0f

## Updates from Apify
### 2026-04-08 10:01 UTC: investigating
We are investigating slow API response times due to underlying database issues.

### 2026-04-08 18:25 UTC: identified
We’ve identified the root cause and have resolved a part of the issue, but the system has not yet fully stabilized.
The Actor Runs list endpoint (https://api.apify.com/v2/acts/:actorId/runs) remains the most impacted, along with related views in the Apify Console, where we are still actively working on a fix. Additional endpoints may also experience degraded performance.
At this time, we cannot provide an estimate for full resolution.

### 2026-04-08 20:35 UTC: investigating
Our systems are currently experiencing a major disruption. We sincerely apologize and are actively investigating the root cause. We will provide updates as more information becomes available.

### 2026-04-08 21:16 UTC: identified
Service has partially recovered, and we are currently experiencing degraded performance.
We are actively investigating the issue and working on a fix. We will continue to provide updates as more information becomes available.

### 2026-04-08 22:24 UTC: monitoring
The Apify platform is fully recovered. The incident followed a database cluster sharding procedure that resulted in a performance impact on some operations. There was no data loss. The Actor run list API endpoint experienced performance issues between 10:00 and 20:30 UTC, followed by a partial outage of all services from 20:30 to 21:10.
Now everything is back to normal, and we are monitoring the situation. We are sorry for any inconvenience caused.

### 2026-04-09 09:15 UTC: resolved
All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen again.

From the builder: does your app depend on Apify? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=apify) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Apify.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-2af40d537f), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.