AI API outages on July 30, 2026
UTC day · measured every 5 minutes from 4 regions · method
On July 30, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): sarvam API: 1; 01.AI API: 1. Providers’ own status pages opened 2 entries (Anthropic).
This page is history. Is it down right now?
Live status, updated every 30 minutes: sarvam API, 01.AI API, Claude API (Anthropic), Gemini API (Google), writer API · all AI APIs, last 72 hours
Was the sarvam API down on July 30, 2026?
Yes, measured. 1 outage(s) attributed to sarvam: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 18:44 UTC, each shorter than one 5-minute probe cycle. At least once sarvam’s own host answered with an HTTP 5xx.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 18:44–18:45 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | <5 min | 2 | provider outage | http 502 |
Was the 01.AI API down on July 30, 2026?
Yes, measured. 1 outage(s) attributed to 01.AI: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 06:06 UTC, at least 3 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 06:06–06:10 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥3 min | 2 | provider outage | timeout |
Was the Claude API (Anthropic) down on July 30, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- major Elevated errors across many models · resolved Jul 30, 10:48 UTC
- minor Degraded performance on Claude Opus 4.8 · resolved Jul 30, 14:24 UTC
Current Claude API (Anthropic) status
Was the Gemini API (Google) down on July 30, 2026?
Not attributably. 1 multi-region failure(s) of Google coincided with failures of other providers, so the cause sat above Google and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 15:50–15:55 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | ≥5 min | 2 | shared with 1 other provider(s) — not attributed | The read operation timed out |
Current Gemini API (Google) status
Was the writer API down on July 30, 2026?
Not attributably. 1 multi-region failure(s) of writer coincided with failures of other providers, so the cause sat above writer and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 15:25–15:25 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
50 single-region failure(s) were also recorded that day (yi-01ai 21, google 10, deepinfra 4, sarvam 2, nebius 2, cohere 2, iflytek 2, openai 1, deepseek 1, sambanova 1). A failure seen from one region cannot be separated from a problem on that network path, so none of them is called an outage.
How is an outage told apart from a network problem?
Each provider is probed every five minutes from 4 independent regions. A failure is attributed to the provider only when it is seen from two or more regions at once and no other provider fails in the same minutes; a failure shared with other providers has a cause above all of them and is not blamed on anyone. Durations are lower bounds: we see the first and last failed probe, not the real start and end. Status-page entries are the provider’s own words, shown next to the measurement, not instead of it.
Previous: Jul 29 · Last 72 hours · Next: Jul 31
Machine-readable: incidents.json · Licence: CC BY 4.0