OpenRouter Outage History
2 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded OpenRouter Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 23, 2026 | [Automated] Chat (/api/v1/chat/completions) is inaccessible | 263h 3m | Resolved |
| Jul 2, 2026 | Scheduled Database Maintenance | 769h 2m | Resolved |
How to Read This OpenRouter Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before OpenRouter acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single OpenRouter outage in this window ran 32d 1h, against a mean recovery of 21d 12h. If you depend on OpenRouter in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.