Skip to main content

Is Hugging Face Down?

No — Hugging Face is up

Reachable from all 8 checked regions

Average response time: 98ms

Last checked · checks run every 6 hours

Official status page: https://status.huggingface.co

Hugging Face uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
121ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 8 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

8-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: 100.00% uptime, 16 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 40 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
106ms
DNS 1ms TCP 1ms TLS 6ms TTFB 105ms
arn
129ms
DNS 1ms TCP 1ms TLS 3ms TTFB 129ms
bom
210ms
DNS 1ms TCP 2ms TLS 4ms TTFB 209ms
cdg
102ms
DNS 0ms TCP 1ms TLS 4ms TTFB 101ms
dfw
50ms
DNS 0ms TCP 0ms TLS 3ms TTFB 50ms
ewr
25ms
DNS 0ms TCP 1ms TLS 4ms TTFB 24ms
fra
114ms
DNS 1ms TCP 1ms TLS 3ms TTFB 113ms
gru
135ms
DNS 0ms TCP 2ms TLS 5ms TTFB 134ms
iad
21ms
DNS 0ms TCP 1ms TLS 4ms TTFB 20ms

What Hugging Face does

Hugging Face hosts the model and dataset repository most machine learning work pulls from, along with hosted inference endpoints and Spaces demos. Training scripts, build pipelines, and production applications download weights from it at runtime, which makes it a build-time and deploy-time dependency for teams who never open the website themselves.

What an outage looks like

Model downloads fail partway with connection or 5xx errors, and code loading a pretrained model hangs or raises a repository-not-found error for models that plainly exist. Git pushes and pulls of large model files stall separately from the website. Spaces demos show a proxy error, and hosted Inference Endpoints time out.

What to do about it

Check status.huggingface.co, which separates the Hub, git hosting, Spaces, the CDN, and Inference Endpoints, because these fail independently and the component you depend on may be fine. Locally cached models keep working, so setting HF_HUB_OFFLINE stops libraries revalidating against the network mid-incident and turns long timeouts into immediate cache hits.

Is it down for everyone, or just you?

If this page says Hugging Face is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

AWS
AWS
Cloudflare
Cloudflare
GitHub
GitHub
Vercel
Vercel

Hugging Face outage FAQ

Will my running application break if Hugging Face goes down?
Only if it fetches from the Hub at runtime. Applications that downloaded weights at build time and hold them in a local cache or image layer keep serving normally. Those loading a pretrained model on every cold start will fail once the cache is empty, which is why baking models into the image is common practice.
Is the Hub down or just Inference Endpoints?
They are tracked as separate components and often fail apart. The status page lists the Hub, git hosting, Spaces, the CDN, and Inference Endpoints on their own lines. A CDN fault can break model downloads while the website loads fine, so match the component to the call your code is actually making.
Can I keep working offline during an outage?
Yes, if the models are already cached. Setting HF_HUB_OFFLINE to 1 makes the libraries use the local cache without contacting the network, which avoids a long timeout on every call. Anything not yet downloaded stays unavailable, so the technique rescues work in progress rather than letting you start something new.
Does a Hugging Face outage affect other model APIs?
No. Commercial model providers run separate infrastructure with their own status pages. A Hugging Face incident affects downloading open models and calling endpoints hosted there. Applications routing to a commercial API for generation but to Hugging Face for tokenisers or embeddings may find one path works and the other does not.

How we measure this

  • We request Hugging Face's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Hugging Face publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Hugging Face goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required