ARCHIVED OFFICIAL INCIDENT

Activity logs, usage metrics reporting are experiencing delays

OpenRouter · Last saved provider status: resolved

Current service report →
This is historical evidence.

The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.

Saved event details

Provider status
resolved
Provider impact
not normalized
Provider record created
15 Oct 2026, 14:50:26 UTC
Provider record updated
17 Oct 2026, 04:43:26 UTC
Explicit provider start
Not available
Explicit provider end
17 Oct 2026, 04:43:26 UTC

Affected components reported by the provider

  • Web & Application Services 2347916e-1f82-448c-b07d-8cfbbad57322

These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.

A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.

OpenRouter's seven reviewed gateway and web components, including its reported incidents and maintenance. It does not establish the status of upstream providers or individual models.

Provider updates in saved revisions

Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.

  1. resolved

    The issue is now resolved.

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC
  2. monitoring

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

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC
  3. identified

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

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC
  4. identified

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

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC
  5. identified

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

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC
  6. identified

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

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC
  7. identified

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

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC
  8. investigating

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

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC
  9. investigating

    We are investigating the issue.

    Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC

Cookie preferences

With your permission, we use Google Analytics and Umami to understand service queries. These tools use cookies or browser storage. Optional analytics stay off until you accept.

Cookies and storage details