Skip to content

Outage tracker

Hugging Face: incident history

The last 24 hours in detail, Hugging Face's declared incident record, and our regional check results beside it.

← Back to Hugging Face's check readings

We started checking Hugging Face on August 20, 2026, which is 66 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Hugging Face reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Hugging Face's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Hugging Face's own status page declared. Below it, any public chatter we saw about Hugging Face and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Hugging Face's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Hugging Face in the last 24 hours, which is not evidence that nothing is wrong.
Hugging Face's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Hugging Face's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Hugging Face next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%3092
US-West100.00%3093
Europe100.00%3090
Asia-Pacific99.93%3068
US-Central100.00%1240
Canada100.00%1240
UK100.00%1240
Southeast Asia99.92%1237
Australia99.92%1237
South America99.60%1239

Their declared record

Hugging Face's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Scheduled maintenance: Inference Endpoints (H200)Maintenance
Oct 7, 2026, 7:33 AM UTC to Oct 7, 2026, 12:30 PM UTC (4h 57m)completed
their latest update (Oct 7, 2026, 12:30 PM UTC): Maintenance ended
Some GPU Jobs and Spaces failing to startMinor incident
Sep 24, 2026, 6:00 PM UTC to Sep 25, 2026, 9:57 AM UTC (15h 57m)resolved
their latest update (Sep 25, 2026, 9:57 AM UTC): 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.
Slower downloads in the Asia-Pacific regionMinor incident
Sep 22, 2026, 6:48 PM UTC to Sep 25, 2026, 6:42 PM UTC (2d 23h)resolved
their latest update (Sep 25, 2026, 6:42 PM UTC): 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.
Scheduled maintenance: HubMaintenance
Sep 16, 2026, 7:00 AM UTC to Sep 16, 2026, 9:00 AM UTC (2h)completed
their latest update (Sep 16, 2026, 9:00 AM UTC): Maintenance ended
Scheduled maintenance: HubMaintenance
Sep 2, 2026, 7:00 AM UTC to Sep 2, 2026, 8:00 AM UTC (1h)completed
their latest update (Sep 2, 2026, 8:00 AM UTC): Maintenance ended
Scheduled maintenance: SpacesMaintenance
Aug 17, 2026, 7:00 AM UTC to Aug 17, 2026, 9:00 AM UTC (2h)completed
their latest update (Aug 17, 2026, 9:00 AM UTC): Maintenance ended
Elevated error rate - AWS CDN (Singapore)Minor incident
Aug 7, 2026, 3:14 PM UTC to Aug 7, 2026, 11:14 PM UTC (8h)resolved
their latest update (Aug 7, 2026, 11:14 PM UTC): 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 …

These entries are Hugging Face's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Hugging Face's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.