AI API outages on August 18, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 18, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): sarvam API: 1; 01.AI API: 1. Providers’ own status pages opened 4 entries (Anthropic, baseten).
This page is history. Is it down right now?
Live status, updated every 30 minutes: sarvam API, 01.AI API, Claude API (Anthropic), baseten API · all AI APIs, last 72 hours
Was the sarvam API down on August 18, 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 05:15 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 05:15–05:15 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | timeout |
Was the 01.AI API down on August 18, 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 15:30 UTC, at least 10 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 15:30–15:40 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥10 min | 3 | provider outage | timeout |
Was the Claude API (Anthropic) down on August 18, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- minor Degraded performance for multiple models · resolved Aug 18, 19:01 UTC
Current Claude API (Anthropic) status
Was the baseten API down on August 18, 2026?
Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten’s own status page opened 3 entries that day (self-reported, listed below).
Self-reported on baseten’s status page, not verified by our probes:
- minor Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated In · resolved Aug 18, 17:14 UTC
- minor Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated In · resolved Aug 18, 17:35 UTC
- minor Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated In · resolved Aug 18, 20:21 UTC
44 single-region failure(s) were also recorded that day (yi-01ai 18, google 6, iflytek 4, sambanova 3, aleph-alpha 2, friendli 2, openrouter 2, sarvam 2, deepinfra 1, stepfun 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: Aug 17 · Last 72 hours · Next: Aug 19
Machine-readable: incidents.json · Licence: CC BY 4.0