DeepInfra outage history
We record DeepInfra's status every five minutes and have not recorded an incident from DeepInfra's status page yet. We never invent one.
Uptime & history
Tracking since Jun 22, 2026% of our checks that found DeepInfra fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.
How DeepInfra fails
Since Jun 27, 2026, DeepInfra's status page has marked 6 DeepInfra components as impaired, across 70 of our five-minute readings. DeepSeek-V3.2-Exp accounts for the most: 28 readings (about 2.3 hours) on 5 days, 28 of them marked as an outage rather than degraded, most recently on Jul 29, 2026. Next is GLM-4.6, with 14 readings on 1 day.
| Component | Outage | Degraded | Maint. | Days | Last |
|---|---|---|---|---|---|
| DeepSeek-V3.2-Exp | 28 | — | — | 5 | Jul 29, 2026 |
| GLM-4.6 | 14 | — | — | 1 | Jul 27, 2026 |
| DeepSeek-V3.1-Terminus | 10 | — | — | 6 | Jul 24, 2026 |
| gpt-oss-120b | 9 | — | — | 3 | Jul 23, 2026 |
| Qwen/Qwen3-235B-A22B-Instruct-2507 | 6 | — | — | 3 | Jul 26, 2026 |
| DeepSeek V3.1 | 3 | — | — | 2 | Jul 6, 2026 |
Counts are five-minute readings of DeepInfra's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.
Incidents and their updates are DeepInfra's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with DeepInfra.