Live  /  Providers  /  Hugging Face

Hugging Face

huggingface.coNo open incidents

Independent assessment — SquidGrid is not affiliated with Hugging Face. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

AI · SquidGrid tracks Hugging Face’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Hugging Face is reporting

Current & recent incidents

Resolved

Slower downloads in the Asia-Pacific region

Minor impact · 2026-09-25 18:42 UTC

Resolved

Some GPU Jobs and Spaces failing to start

Minor impact · 2026-09-25 09:57 UTC

Resolved

Elevated error rate - AWS CDN (Singapore)

Incident impact · 2026-08-07 23:14 UTC

Resolved

Elevated error rate - AWS CDN (Singapore)

Minor impact · 2026-08-07 23:14 UTC

Resolved

Hub unavailable

Incident impact · 2026-07-16 10:07 UTC

Resolved

Hub unavailable

Critical impact · 2026-07-16 10:07 UTC

Resolved

Elevated error rate – AWS CDN (Singapore)

Incident impact · 2026-06-30 08:05 UTC

Resolved

Data serving slowness in Asia region

Incident impact · 2026-06-10 10:50 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Hugging Face has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Hugging Face runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Hugging Face is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Hugging Face.