Meta Provider API calls are failing on OpenRouter with error 401.

What to do

• Check whether your product depends on OpenRouter. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-09-25 00:33 UTC and 2026-09-25 00:33 UTC may need a replay.

• Subscribe to OpenRouter's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=openrouter works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

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

Updates from OpenRouter 1

1. resolvedSep 25, 2026, 12:33 AM UTC

   Sep 25, 00:33 UTC 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. Sep 24, 23:46 UTC Monitoring - Meta Provider API calls are operational again. We are continuing to monitor. Sep 24, 23:28 UTC Monitoring - The Meta team has begun applying remediations and success rate is improving. Root cause is still unknown. Sep 24, 23:15 UTC Identified - The Meta team is continuing to investigate and is beginning work on remediation. Root cause is still unknown. Sep 24, 22:55 UTC Investigating - The Meta team has been pinged and is investigating.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.