OpenRouter incident

The issue is now resolved. Root cause was identified as an authentication issue on the Meta Developer API Platform impacting all Managed Meta Accounts including OpenRouter's.

Minor Resolved

OpenRouter experienced a minor incident on September 24, 2026 affecting Chat (/api/v1/chat/completions) and TTS (/api/v1/audio/speech) and 1 more component, lasting 1h 37m. The incident has been resolved; the full update timeline is below.

Started
Sep 24, 2026, 10:55 PM UTC
Resolved
Sep 25, 2026, 12:33 AM UTC
Duration
1h 37m
Detected by Pingoru
Sep 24, 2026, 10:55 PM UTC

Affected components

Chat (/api/v1/chat/completions)TTS (/api/v1/audio/speech)STT (/api/v1/audio/transcriptions)

Update timeline

  1. investigating Sep 24, 2026, 10:55 PM UTC

    The Meta team has been pinged and is investigating.

  2. identified Sep 24, 2026, 11:15 PM UTC

    The Meta team is continuing to investigate and is beginning work on remediation. Root cause is still unknown.

  3. monitoring Sep 24, 2026, 11:28 PM UTC

    The Meta team has begun applying remediations and success rate is improving. Root cause is still unknown.

  4. monitoring Sep 24, 2026, 11:46 PM UTC

    Meta Provider API calls are operational again. We are continuing to monitor.

  5. resolved Sep 25, 2026, 12:33 AM UTC

    The issue is now resolved. Root cause was identified as an authentication issue on the Meta Developer API Platform impacting all Managed Meta Accounts including OpenRouter's.