AI API outages on August 24, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 24, 2026 (UTC) our probes attributed 3 outage(s) to 1 provider(s): Gemini API (Google): 3. Providers’ own status pages opened 3 entries (Anthropic).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), Claude API (Anthropic), SambaNova API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on August 24, 2026?
Yes, measured. 3 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 10:05 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:05–10:05 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | The read operation timed out |
| 10:30–10:30 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | The read operation timed out |
| 13:50–13:50 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | The read operation timed out |
Is the Gemini API (Google) down right now? Live status →
Was the Claude API (Anthropic) down on August 24, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. Anthropic’s own status page opened 3 entries that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- major Elevated errors for multiple models · resolved Aug 24, 08:30 UTC
- minor Errors logging into Claude.ai · resolved Aug 24, 17:16 UTC
- minor Issues logging into Claude.ai · resolved Aug 24, 20:26 UTC
Is the Claude API (Anthropic) down right now? Live status →
Was the SambaNova API down on August 24, 2026?
Not attributably. 1 multi-region failure(s) of SambaNova coincided with failures of other providers, so the cause sat above SambaNova and is not blamed on it. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 17:45–17:53 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥8 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Is the SambaNova API down right now? Live status →
84 single-region failure(s) were also recorded that day (yi-01ai 21, nscale 14, baseten 12, cohere 10, google 9, sambanova 6, hunyuan 2, glm 1, aleph-alpha 1, anthropic 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.
← Aug 23 · Last 72 hours · Aug 25 →
Machine-readable: incidents.json · Licence: CC BY 4.0