A100 hardware partial outage
A record of the Replicate incident on August 27, 2026 (Japan time): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
3 other incident(s) at different providers overlapped with this one. It may not have been limited to a single service — several providers were degraded at once.
- ElevenLabsElevated latency on Text-to-Speech and Speech-to-Text Requests
- GitHubIncident with Actions and Pull Requests
- GitHubDisruption with GitHub Billing
Derived from our own archive of official status pages across 13 providers. Items lasting more than 24 hours and unresolved items are excluded, as they would misrepresent the moment.
How big was this outage?
This outage lasted 188 minutes. Across 12 major incidents recorded for Replicate, the median duration is 182 minutes, making this the 6th longest.
Longer than a typical outage.
Only incidents recorded as major-or-worse and already resolved are counted.
Current status
Replicate is operating normally now. This incident has been resolved.
See current Replicate status →What you can do during an outage
Source: Replicate's official status page.
Other Replicate incidents
- Delayed scaling due to node failureAugust 11, 2026
- Significant degradationAugust 5, 2026
- API degraded for A100sAugust 3, 2026
- Degraded scale-out due to failed setups pulling from huggingfaceAugust 1, 2026
- Hitting GPU Capacity for H100s creating large queue times for some modelsJuly 22, 2026