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 21h 4m since the last recorded problem.
Operational · 24h
97.22%
1 incident · ≈40m degraded
288 checks
Operational · 7d
99.55%
1 incident · ≈45m degraded
2016 checks
Operational · 30d
94.17%
1 incident · ≈1d 17h degraded
8634 checks
Operational · since Jun 22, 2026
94.90%
2 incidents · ≈2d 7h degraded
13138 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
- 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.