OpenRouter Outage History

OpenRouter is up right now

Pingoru has recorded 16 incidents for OpenRouter: 16 in the last 12 months and 11 in the last 90 days.

Source: status.openrouter.ai

16incidents recorded
16last 12 months
11last 90 days
6 hourstypical duration
Incidents per month
024MayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOct8%
Pingoru began tracking OpenRouter in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 2026111 of 744 (1%)
June 2026013 of 720 (2%)
July 202631 of 744 (0%)
August 2026416 of 744 (2%)
September 202645 of 720 (1%)
October 2026345 of 556 (8%)

Incidents, newest first

Minor October 15, 2026 The issue is now resolved. 1d 13h Web & Application Services

Started Oct 15, 2026, 02:50 PM UTC· resolved Oct 17, 2026, 04:43 AM UTC

  1. investigating Oct 15, 2026, 02:50 PM UTC

    We are investigating the issue.

  2. investigating Oct 15, 2026, 06:20 PM UTC

    We are continuing to investigate the issue. Inference is not affected.

  3. identified Oct 15, 2026, 10:32 PM UTC

    We have identified the issue and are deploying remediations. Inference is not affected.

  4. identified Oct 16, 2026, 05:44 AM UTC

    We have identified the issue and are deploying remediations. Inference is not affected.

  5. identified Oct 16, 2026, 09:45 AM UTC

    We have identified the issue and are deploying remediations. Inference is not affected.

  6. identified Oct 16, 2026, 07:26 PM UTC

    Logs latency has been significantly reduced, though is still elevated. Inference is not affected.

  7. identified Oct 17, 2026, 12:09 AM UTC

    Logs latency continues to be elevated. Inference is not affected.

  8. monitoring Oct 17, 2026, 01:15 AM UTC

    Logs and usage metrics are now up to date in almost all cases. A small fraction are still delayed.

  9. resolved Oct 17, 2026, 04:43 AM UTC

    The issue is now resolved.

Read the full incident report →

Minor October 14, 2026 The issue is now resolved. Cloudflare moved traffic to nearby locations. Other locations were not affected, and no change on our side caused it. 42m Chat (/api/v1/chat/completions)

Started Oct 14, 2026, 04:12 AM UTC· resolved Oct 14, 2026, 04:54 AM UTC

  1. investigating Oct 14, 2026, 03:25 PM UTC

    We are investigating the issue. Requests that reached OpenRouter through Portland were slow or failed.

  2. resolved Oct 14, 2026, 03:25 PM UTC

    The issue is now resolved. Cloudflare moved traffic to nearby locations. Other locations were not affected, and no change on our side caused it.

Read the full incident report →

Minor September 24, 2026 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. 1h 37m Chat (/api/v1/chat/completions), TTS (/api/v1/audio/speech), STT (/api/v1/audio/transcriptions)

Started Sep 24, 2026, 10:55 PM UTC· resolved Sep 25, 2026, 12:33 AM UTC

  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.

Read the full incident report →

Minor September 23, 2026 This incident is resolved. Between approximately 11:50 and 17:11 UTC, a portion of sign-in and sign-up attempts on openrouter.ai were incorrectly blocked with the message "This action was detected as suspicious and has been blocked." The cause was an infrastructure issue at our authentication provider that made one of its bot-protection checks fail, which in turn triggered a blocking rule. The provider disabled the rule at 17:11 UTC and sign-ins have succeeded normally since then. Existing ses 26m Web & Application Services

Started Sep 23, 2026, 05:11 PM UTC· resolved Sep 23, 2026, 05:38 PM UTC

  1. investigating Sep 23, 2026, 05:11 PM UTC

    We are investigating the issue. Since approximately 11:50 UTC, a portion of sign-in and sign-up attempts on openrouter.ai are failing with the message "This action was detected as suspicious and has been blocked." This affects all login methods. Workaround: Retrying the sign-in usually succeeds within a few attempts.

  2. identified Sep 23, 2026, 05:19 PM UTC

    We have identified the cause. An infrastructure issue at our authentication provider caused one of its bot-protection checks to fail, which incorrectly blocked a portion of sign-in and sign-up attempts.

  3. monitoring Sep 23, 2026, 05:25 PM UTC

    The provider has disabled the affected rule and new sign-ins, we are monitoring the recovery.

  4. resolved Sep 23, 2026, 05:38 PM UTC

    This incident is resolved. Between approximately 11:50 and 17:11 UTC, a portion of sign-in and sign-up attempts on openrouter.ai were incorrectly blocked with the message "This action was detected as suspicious and has been blocked." The cause was an infrastructure issue at our authentication provider that made one of its bot-protection checks fail, which in turn triggered a blocking rule. The provider disabled the rule at 17:11 UTC and sign-ins have succeeded normally since then. Existing sessions and API keys were not affected at any point, and there was no security breach or exposure of account data. If you were unable to sign in earlier, please try again. We apologize for the disruption.

Read the full incident report →

Major September 4, 2026 Degraded video generation and batch jobs APIs 2h 44m

Started Sep 04, 2026, 06:27 PM UTC· resolved Sep 04, 2026, 09:12 PM UTC

  1. investigating Sep 04, 2026, 06:27 PM UTC

    We are investigating degraded availability for our video generation and batch jobs APIs.

  2. monitoring Sep 04, 2026, 07:45 PM UTC

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

  3. resolved Sep 04, 2026, 09:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 4, 2026 This incident has been resolved. 2h 45m Video (/api/v1/videos)

Started Sep 04, 2026, 06:27 PM UTC· resolved Sep 04, 2026, 09:12 PM UTC

  1. investigating Sep 11, 2026, 02:34 AM UTC

    We are investigating degraded availability for our video generation and batch jobs APIs.

  2. resolved Sep 11, 2026, 02:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 28, 2026 Web application degraded 2h 42m

Started Aug 28, 2026, 07:50 PM UTC· resolved Aug 28, 2026, 10:33 PM UTC

  1. investigating Aug 28, 2026, 07:50 PM UTC

    We are investigating an issue that is causing certain parts of the web application to be unavailable. We will update when we have more information. Inference is unaffected.

  2. monitoring Aug 28, 2026, 09:47 PM UTC

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

  3. resolved Aug 28, 2026, 10:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 28, 2026 Elevated 429s on Anthropic and OpenAI – Chat (/api/v1/chat/completions)

Started Aug 28, 2026, 02:15 AM UTC· resolved Aug 28, 2026, 02:15 AM UTC

  1. resolved Aug 28, 2026, 02:15 AM UTC

    Between 1:20 and 1:24 UTC, Anthropic and OpenAI models responded with 429s at an elevated rate.

Read the full incident report →

Minor August 28, 2026 Issue is resolved 4m Chat (/api/v1/chat/completions)

Started Aug 28, 2026, 02:15 AM UTC· resolved Aug 28, 2026, 02:19 AM UTC

  1. investigating Sep 11, 2026, 02:38 AM UTC

    Anthropic and OpenAI models responded with 429s at an elevated rate.

  2. resolved Sep 11, 2026, 02:38 AM UTC

    Issue is resolved

Read the full incident report →

Major July 23, 2026 Erroneous outage status – Chat (/api/v1/chat/completions)

Started Jul 23, 2026, 09:17 PM UTC· resolved Jul 23, 2026, 09:17 PM UTC

  1. resolved Jul 23, 2026, 09:17 PM UTC

    We briefly reported a major service outage on our Chat (/api/v1/chat/completions) and other inference endpoints. This was in error. We apologize for the notification!

Read the full incident report →

Major July 23, 2026 [Automated] Chat (/api/v1/chat/completions) is inaccessible 10m Chat (/api/v1/chat/completions)

Started Jul 23, 2026, 08:57 PM UTC· resolved Jul 23, 2026, 09:08 PM UTC

  1. investigating Jul 23, 2026, 08:57 PM UTC

    Chat (/api/v1/chat/completions) cannot be reached by our automated monitoring.

Read the full incident report →

Major July 5, 2026 Scheduled Database Maintenance 29m Clerk (UI account auth) (Clerk Auth Backend API), Clerk (UI account auth) (Clerk Auth Webhooks)

Started Jul 05, 2026, 06:00 AM UTC· resolved Jul 05, 2026, 06:30 AM UTC

  1. investigating Jul 02, 2026, 06:58 PM UTC

    We will be conducting scheduled database maintenance on Sunday, July 5 6:00AM to 6:30AM UTC. All inference endpoints will continue to work as normal. What will continue as normal: All inference endpoints (Chat Completions(opens in new tab), Embeddings(opens in new tab), etc.) will continue to work. OpenRouter will continue to service your API requests as before. Budget enforcement Logs and analytics pages will continue to update Read-only dashboard capabilities (viewing API keys, usage, workspaces, guardrails, settings, etc.) What will not be available: Credit purchases Edits, creations, and deletions of account settings, API keys, budgets, workspaces, and guardrails New OAuth connections Account registration and deletion During this period, auto top-up and low-balance notifications may be delayed until the end of the maintenance window. If you frequently exceed your top-up threshold, consider increasing your top-up amount or preemptively purchasing additional credits to avoid potential interruption.

  2. investigating Jul 05, 2026, 06:00 AM UTC

    Scheduled maintenance is currently in progress.

  3. investigating Jul 05, 2026, 06:30 AM UTC

    Scheduled maintenance has been completed.

Read the full incident report →

Major April 14, 2026 [Automated] Generation (/api/v1/generation) was inaccessible 1h 4m Data API (Generation (/api/v1/generation))

Started Apr 14, 2026, 05:02 PM UTC· resolved Apr 14, 2026, 06:07 PM UTC

  1. investigating Apr 14, 2026, 05:02 PM UTC

    Generation (/api/v1/generation) cannot be reached by our automated monitoring.

  2. resolved Apr 14, 2026, 06:07 PM UTC

    Generation (/api/v1/generation) is operational again.

Read the full incident report →