Meta Provider API calls are failing on OpenRouter with error 401.
OpenRouter · Last saved provider status: resolved
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
- 24 Sep 2026, 22:55:23 UTC
- Provider record updated
- 25 Sep 2026, 00:33:18 UTC
- Explicit provider start
- Not available
- Explicit provider end
- 25 Sep 2026, 00:33:18 UTC
Affected components reported by the provider
- TTS (/api/v1/audio/speech)
15c7d7e9-e2b7-43dd-aa56-77c4959fc603 - STT (/api/v1/audio/transcriptions)
93008741-4362-4fb6-85c4-6cddb8412116 - Chat (/api/v1/chat/completions)
9fb5ccff-e128-455a-be20-59572f8d363a
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.
- resolved
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.
Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC - monitoring
Meta Provider API calls are operational again. We are continuing to monitor.
Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC - monitoring
The Meta team has begun applying remediations and success rate is improving. Root cause is still unknown.
Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC - identified
The Meta team is continuing to investigate and is beginning work on remediation. Root cause is still unknown.
Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC - investigating
The Meta team has been pinged and is investigating.
Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC