Replicatestatus history & uptime
How reliable has Replicatebeen? We record a status check every few minutes and keep the history — uptime, recent incidents, and the upstream providers whose outages cascade here. We never invent numbers; where we're still collecting, we say so.
Uptime & history
Tracking since Jun 22, 2026Currently up for 1d 23h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
99.65%
0 incidents · ≈30m down · ≈5m degraded
2016 checks
Operational · 30d
99.85%
0 incidents · ≈45m down · ≈20m degraded
8639 checks
Operational · since Jun 22, 2026
97.38%
3 incidents · ≈45m down · ≈2d 11h degraded
27491 checks
% of our checks that found Replicate 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.
Recent checks
oldernow
Past incidents
- A100 hardware partial outageAug 26, 2026 · ongoing · monitoring
- Delayed scaling due to node failureAug 10, 2026 · ongoing · monitoring
- Limited H100 capacityJun 30, 2026 · ongoing · identified
History is recorded from Replicate's official status plus our own independent checks. AIDownCheck is independent and not affiliated with Replicate.