Hugging Face Outage History

8 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Hugging Face status18.80% uptime history

Every Recorded Hugging Face Incident

Hugging Face incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 17, 2026Scheduled maintenance: Spaces2h 0mResolved
Aug 7, 2026Elevated error rate - AWS CDN (Singapore)402h 54mResolved
Jul 30, 2026Scheduled maintenance: Inference Endpoints28 minResolved
Jul 22, 2026Scheduled maintenance: Inference Endpoints1h 0mResolved
Jul 16, 2026Hub unavailable937h 38mResolved
Jul 8, 2026Scheduled maintenance: Jobs1h 0mResolved
Jun 30, 2026Elevated error rate – AWS CDN (Singapore)1322h 10mResolved
Jun 10, 2026Data serving slowness in Asia region1803h 8mResolved

How to Read This Hugging Face Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Hugging Face acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Hugging Face outage in this window ran 75d 3h, against a mean recovery of 23d 6h. If you depend on Hugging Face in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.