Apify incident

MCP: Failing OAuth sing-in from clients using CIMD with loopback redirects

Minor Resolved View vendor source →

Apify experienced a minor incident on May 6, 2026 affecting MCP server (mcp.apify.com), lasting 12h 18m. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 08:08 PM UTC
Resolved
May 07, 2026, 08:27 AM UTC
Duration
12h 18m
Detected by Pingoru
May 06, 2026, 08:08 PM UTC

Affected components

MCP server (mcp.apify.com)

Update timeline

  1. 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.

  2. resolved May 07, 2026, 08:27 AM UTC

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

Looking to track Apify downtime and outages?

Pingoru polls Apify's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Apify reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Apify alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Apify for free

5 free monitors · No credit card required