Hugging Face
AI. Source: Hugging Face status page.
History starts 2026-08-07 15:14 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 3+
- Median to mitigation
- not reported
- Median to resolution
- 15h 57m
- p95 to resolution
- 2d 23h
- Naming an upstream provider
- 33%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 1 |
| A provider or third-party service this vendor depends on failed | 1 |
| CDN or edge layer failed or served bad content | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Some GPU Jobs and Spaces failing to start
Affected: Spaces Proxy, Jobs
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
degraded
Between 18:00 UTC on September 24 and 09:10 UTC on September 25, some GPU Jobs and GPU Spaces failed to start. Affected jobs ended with an ERROR status before the container started.
-
resolved
The issue is resolved. If your job failed between 18:00 UTC on September 24 and 09:10 UTC on September 25, please resubmit it. If your Space is still showing a Runtime error, restart it from the Space settings.
Excerpts are shortened. Read the full incident on Hugging Face's status page.
Slower downloads in the Asia-Pacific region
Affected: AWS CDN
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
degraded
We're seeing slower download speeds for some users in the Asia-Pacific region who are served by our Singapore CDN location. Reduced network capacity between cloud regions is impacting our ability to download files that aren't already cached in the region. We are not seeing an...
-
degraded
The Asia Pacific region continues to experience degraded performance due to impaired underlying network capacity. The root cause is identified as the rupture of a subsea cable between China and Japan, rerouting traffic onto the remaining capacity. We continue to monitor the...
-
resolved
The upstream network capacity issue affecting our Singapore CDN location has been resolved, and download performance for Asia-Pacific users is back to normal. We've returned traffic routing to its usual configuration. Thank you for your patience.
Excerpts are shortened. Read the full incident on Hugging Face's status page.
Elevated error rate - AWS CDN (Singapore)
Affected: AWS CDN
Failure mode: CDN or edge layer failed or served bad content. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
degraded
Some file downloads from our Singapore region (ap-southeast-1) failed with 500 errors during two short periods, starting at 15:14 UTC. Downloads are normal again now. The cause is not fully resolved, so short bursts of errors can return until our fix is in place. Other CDN...
-
resolved
Our fix is now in place and this incident is resolved. Applying it caused one final short period of failed downloads between 23:00 and 23:14 UTC, as we noted could happen. Downloads from the Singapore region have been stable since, and we have added capacity to prevent this from...
Excerpts are shortened. Read the full incident on Hugging Face's status page.