Skip to main content
Hugging Face Inference API logo

Is Hugging Face Inference API Down?

No — Hugging Face Inference API is up

Reachable from all 8 checked regions

Average response time: 204ms

Last checked · checks run every 6 hours

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

Hugging Face Inference API uptime

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

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

30-day history

57-day clean streak
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 46 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 31 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 31 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: no data
Sep 13 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.

iad
35ms
DNS 15ms TCP 2ms TLS 5ms TTFB 34ms
jnb
496ms
DNS 222ms TCP 4ms TLS 4ms TTFB 496ms
lax
141ms
DNS 59ms TCP 2ms TLS 4ms TTFB 140ms
lhr
286ms
DNS 20ms TCP 40ms TLS 43ms TTFB 286ms
nrt
181ms
DNS 14ms TCP 1ms TLS 5ms TTFB 180ms
ord
73ms
DNS 34ms TCP 1ms TLS 3ms TTFB 72ms
sin
322ms
DNS 78ms TCP 2ms TLS 3ms TTFB 322ms
sjc
98ms
DNS 18ms TCP 1ms TLS 4ms TTFB 98ms

What Hugging Face Inference API 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 Inference API is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Hugging Face Inference API 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 Inference API's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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 Inference API 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 Inference API goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required