Is Apify down?

Last checked 3m ago
Current status
Apify is up

No incidents right now.

Official status page: https://status.apify.com · Polled every 5 minutes · 26 components tracked

Apify is operational right now. Last checked 3m ago; the most recent incident resolved 9d 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 8 incidents in the last 90 days (98.61% uptime). Get email, Slack, Discord, or webhook alerts the moment Apify reports a new incident — free for 5 monitors, no credit card.

Users who monitor Apify also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Apify uptime 98.61% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 59m
    Started Jun 04, 2026, 03:07 PM UTC · Resolved Jun 04, 2026, 05:07 PM UTC
    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.

  2. Resolved 17h 39m
    Started May 15, 2026, 11:48 AM UTC · Resolved May 16, 2026, 05:28 AM UTC
    DatacenterConsole (console.apify.com)ResidentialAPI (api.apify.com)SERP
    Timeline · 4 updates
    • investigating · May 15, 2026, 11:48 AM UTC

      We're investigating the issue.

    • investigating · May 15, 2026, 11:51 AM UTC

      We are continuing to investigate this issue.

    • monitoring · May 15, 2026, 12:19 PM UTC

      We have identified and resolved the current problems with our in-memory cache. We're monitoring the situation.

    • resolved · May 16, 2026, 05:28 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved
    Started May 14, 2026, 07:20 AM UTC · Resolved May 14, 2026, 07:20 AM UTC
    Timeline · 1 update
    • resolved · May 14, 2026, 08:21 AM UTC

      We experienced degraded performance on our proxy due to an unexpected increase in load. This caused slower response times for some users. The issue lasted approximately 5 minutes and has been fully resolved. All systems are now operating normally. We apologize for the inconvenience.

    Latest: We experienced degraded performance on our proxy due to an unexpected increase in load. This caused slower response times for some users. The issue lasted approximately 5 minutes a…

  4. Resolved 12h 18m
    Started May 06, 2026, 08:08 PM UTC · Resolved May 07, 2026, 08:27 AM UTC
    MCP server (mcp.apify.com)
    Timeline · 2 updates
    • identified · May 06, 2026, 08:08 PM UTC

      OAuth sign-in to mcp.apify.com from clients using CIMD with loopback redirects (currently Claude Code) is failing due to a regression. Existing connections and other clients (claude.ai, Cursor, Codex) are unaffected (the later use DCR). We are sorry for the inconvenience and working on a fix.

    • resolved · May 07, 2026, 08:27 AM UTC

      We have implemented a fix for the OAuth flow, and the connections are now working normally.

    Latest: We have implemented a fix for the OAuth flow, and the connections are now working normally.

  5. Resolved 44m
    Started May 05, 2026, 01:50 PM UTC · Resolved May 05, 2026, 02:34 PM UTC
    Console (console.apify.com)
    Timeline · 3 updates
    • investigating · May 05, 2026, 01:50 PM UTC

      We're experiencing outage of key-value store. We're investigation the cause of the issue

    • monitoring · May 05, 2026, 02:19 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · May 05, 2026, 02:34 PM UTC

      We've resolved an issue where a key-value store API update caused some Actor runs to time out. If your Actor run timed out you can get it back by resurrecting it. There was no data loss. We sincerely apologize for any inconvenience this may have caused.

    Latest: We've resolved an issue where a key-value store API update caused some Actor runs to time out. If your Actor run timed out you can get it back by resurrecting it. There was no data…

See the full Apify outage history

3 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

Outage history

Past 90 days · 8 incidents View full outage history →