Skip to content

Outage tracker / Hugging Face

Is Hugging Face down?

I'm having a problem

Vendor reports no incidentWhat Hugging Face reports

Hugging Face reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:59 UTC.

Hugging Face's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 9 minutes ago

Our checks of Hugging Face pass from all 10 regions we check.

As of Nov 5, 2026, 2:51 PM UTC, RealUptime's checks of Hugging Face passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:51 PM UTC
US-East653 msChecks passing
US-West994 msChecks passing
Europe417 msChecks passing
Asia-Pacific1029 msChecks passing
US-Central197 msChecks passing
Canada723 msChecks passing
UK257 msChecks passing
Southeast Asia2723 msChecks passing
Australia980 msChecks passing
South America829 msChecks passing
their status pagetheir claim, not our reading

Hugging Face publishes no status feed we can read, so the only reading here is our check reading on the left.

Hugging Face response time, by region

US-East
987msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 545ms2026-10-08 UTC: p95 591ms2026-10-09 UTC: p95 520ms2026-10-10 UTC: p95 596ms2026-10-11 UTC: p95 613ms2026-10-12 UTC: p95 579ms2026-10-13 UTC: p95 478ms2026-10-14 UTC: p95 472ms2026-10-15 UTC: p95 404ms2026-10-16 UTC: p95 461ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 955ms2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 955ms2026-10-28 UTC: p95 785ms2026-10-29 UTC: p95 839ms2026-10-30 UTC: p95 895ms2026-10-31 UTC: p95 831ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 987ms
Oct 7Oct 21Nov 5
US-West
1.6sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 553ms2026-10-08 UTC: p95 538ms2026-10-09 UTC: p95 708ms2026-10-10 UTC: p95 646ms2026-10-11 UTC: p95 636ms2026-10-12 UTC: p95 574ms2026-10-13 UTC: p95 480ms2026-10-14 UTC: p95 437ms2026-10-15 UTC: p95 578ms2026-10-16 UTC: p95 646ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 998ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 949ms2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 992ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Europe
2.2sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 548ms2026-10-08 UTC: p95 432ms2026-10-09 UTC: p95 478ms2026-10-10 UTC: p95 518ms2026-10-11 UTC: p95 499ms2026-10-12 UTC: p95 479ms2026-10-13 UTC: p95 458ms2026-10-14 UTC: p95 282ms2026-10-15 UTC: p95 333ms2026-10-16 UTC: p95 309ms2026-10-17 UTC: p95 628ms2026-10-18 UTC: p95 848ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 864ms2026-10-21 UTC: p95 994ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 965ms2026-10-24 UTC: p95 903ms2026-10-25 UTC: p95 925ms2026-10-26 UTC: p95 899ms2026-10-27 UTC: p95 768ms2026-10-28 UTC: p95 706ms2026-10-29 UTC: p95 758ms2026-10-30 UTC: p95 841ms2026-10-31 UTC: p95 358ms2026-11-01 UTC: p95 400ms2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
Asia-Pacific
2.4sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 719ms2026-10-08 UTC: p95 740ms2026-10-09 UTC: p95 722ms2026-10-10 UTC: p95 806ms2026-10-11 UTC: p95 686ms2026-10-12 UTC: p95 876ms2026-10-13 UTC: p95 690ms2026-10-14 UTC: p95 733ms2026-10-15 UTC: p95 764ms2026-10-16 UTC: p95 770ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 5.3s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
US-Central
623msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 691ms2026-10-08 UTC: p95 548ms2026-10-09 UTC: p95 602ms2026-10-10 UTC: p95 606ms2026-10-11 UTC: p95 791ms2026-10-12 UTC: p95 521ms2026-10-13 UTC: p95 668ms2026-10-14 UTC: p95 712ms2026-10-15 UTC: p95 616ms2026-10-16 UTC: p95 776ms2026-10-17 UTC: p95 677ms2026-10-18 UTC: p95 972ms2026-10-19 UTC: p95 868ms2026-10-20 UTC: p95 739ms2026-10-21 UTC: p95 724ms2026-10-22 UTC: p95 732ms2026-10-23 UTC: p95 514ms2026-10-24 UTC: p95 561ms2026-10-25 UTC: p95 659ms2026-10-26 UTC: p95 461ms2026-10-27 UTC: p95 577ms2026-10-28 UTC: p95 413ms2026-10-29 UTC: p95 310ms2026-10-30 UTC: p95 366ms2026-10-31 UTC: p95 463ms2026-11-01 UTC: p95 447ms2026-11-02 UTC: p95 501ms2026-11-03 UTC: p95 591ms2026-11-04 UTC: p95 824ms2026-11-05 UTC: p95 623ms
Oct 7Oct 21Nov 5
Canada
863msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 594ms2026-10-08 UTC: p95 645ms2026-10-09 UTC: p95 643ms2026-10-10 UTC: p95 640ms2026-10-11 UTC: p95 598ms2026-10-12 UTC: p95 535ms2026-10-13 UTC: p95 695ms2026-10-14 UTC: p95 631ms2026-10-15 UTC: p95 523ms2026-10-16 UTC: p95 825ms2026-10-17 UTC: p95 708ms2026-10-18 UTC: p95 819ms2026-10-19 UTC: p95 912ms2026-10-20 UTC: p95 882ms2026-10-21 UTC: p95 714ms2026-10-22 UTC: p95 715ms2026-10-23 UTC: p95 636ms2026-10-24 UTC: p95 719ms2026-10-25 UTC: p95 632ms2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 805ms2026-10-31 UTC: p95 770ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 982ms2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 863ms
Oct 7Oct 21Nov 5
UK
350msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 352ms2026-10-08 UTC: p95 362ms2026-10-09 UTC: p95 400ms2026-10-10 UTC: p95 349ms2026-10-11 UTC: p95 359ms2026-10-12 UTC: p95 393ms2026-10-13 UTC: p95 588ms2026-10-14 UTC: p95 415ms2026-10-15 UTC: p95 434ms2026-10-16 UTC: p95 401ms2026-10-17 UTC: p95 543ms2026-10-18 UTC: p95 610ms2026-10-19 UTC: p95 825ms2026-10-20 UTC: p95 518ms2026-10-21 UTC: p95 456ms2026-10-22 UTC: p95 588ms2026-10-23 UTC: p95 444ms2026-10-24 UTC: p95 315ms2026-10-25 UTC: p95 576ms2026-10-26 UTC: p95 568ms2026-10-27 UTC: p95 587ms2026-10-28 UTC: p95 392ms2026-10-29 UTC: p95 374ms2026-10-30 UTC: p95 278ms2026-10-31 UTC: p95 229ms2026-11-01 UTC: p95 495ms2026-11-02 UTC: p95 641ms2026-11-03 UTC: p95 671ms2026-11-04 UTC: p95 442ms2026-11-05 UTC: p95 350ms
Oct 7Oct 21Nov 5
Southeast Asia
2.3sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 782ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 930ms2026-10-10 UTC: p95 976ms2026-10-11 UTC: p95 896ms2026-10-12 UTC: p95 985ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 864ms2026-10-15 UTC: p95 929ms2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 937ms2026-10-24 UTC: p95 513ms2026-10-25 UTC: p95 449ms2026-10-26 UTC: p95 584ms2026-10-27 UTC: p95 523ms2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 577ms2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 557ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Australia
2.3sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 948ms2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 962ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 992ms2026-10-21 UTC: p95 825ms2026-10-22 UTC: p95 671ms2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 980ms2026-10-25 UTC: p95 775ms2026-10-26 UTC: p95 759ms2026-10-27 UTC: p95 855ms2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 910ms2026-10-31 UTC: p95 802ms2026-11-01 UTC: p95 703ms2026-11-02 UTC: p95 965ms2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
South America
1.4sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 921ms2026-10-08 UTC: p95 891ms2026-10-09 UTC: p95 732ms2026-10-10 UTC: p95 896ms2026-10-11 UTC: p95 771ms2026-10-12 UTC: p95 830ms2026-10-13 UTC: p95 842ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 954ms2026-10-16 UTC: p95 870ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 793ms2026-10-21 UTC: p95 742ms2026-10-22 UTC: p95 914ms2026-10-23 UTC: p95 8.8s2026-10-24 UTC: p95 941ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5

Check your own site while you wait on Hugging Face

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Hugging Face. It cannot diagnose Hugging Face's own systems.

What we measured, function by function

Hugging Face answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Dataset viewerUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DatasetsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DocumentationUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Inference ProvidersUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Model downloadsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • SpacesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

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

Get an email when Hugging Face reports an incident

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

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

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

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 653msstatus code: 200checked: Nov 5, 2026, 2:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Hugging Face normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 994msstatus code: 200checked: Nov 5, 2026, 2:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Hugging Face normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 197msstatus code: 200checked: Nov 5, 2026, 2:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Hugging Face normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 723msstatus code: 200checked: Nov 5, 2026, 2:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Hugging Face normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 829msstatus code: 200checked: Nov 5, 2026, 2:11 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Hugging Face normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 417msstatus code: 200checked: Nov 5, 2026, 2:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Hugging Face normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 257msstatus code: 200checked: Nov 5, 2026, 2:46 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Hugging Face normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1029msstatus code: 200checked: Nov 5, 2026, 2:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Hugging Face normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2723msstatus code: 200checked: Nov 5, 2026, 2:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Hugging Face normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 980msstatus code: 200checked: Nov 5, 2026, 2:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Hugging Face normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Hugging Face, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Hugging Face yet, which is not evidence that nothing is wrong.

Recent probe events

Scheduled maintenance: Inference Endpoints (H200), 4h 57mdeclared on their status page2026-10-07
Some GPU Jobs and Spaces failing to start, 15h 57mdeclared on their status page2026-09-24
Slower downloads in the Asia-Pacific region, 71h 54mdeclared on their status page2026-09-22
Scheduled maintenance: Hub, 2hdeclared on their status page2026-09-16
Scheduled maintenance: Hub, 1hdeclared on their status page2026-09-02
Scheduled maintenance: Spaces, 2hdeclared on their status page2026-08-17
Elevated error rate - AWS CDN (Singapore), 8hdeclared on their status page2026-08-07

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Hugging Face since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Hugging Face covering any window you pick, with our check readings and Hugging Face's own claim at the time, side by side.

Full check history for Hugging Face: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Hugging Face uptime by RealUptime's checksLive, from this page's own readings.
[![Hugging Face uptime by RealUptime's checks](https://realuptime.io/outages/hugging-face/badge.svg?days=30)](https://realuptime.io/outages/hugging-face)
<a href="https://realuptime.io/outages/hugging-face"><img src="https://realuptime.io/outages/hugging-face/badge.svg?days=30" alt="Hugging Face uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Hugging Face down?", https://realuptime.io/outages/hugging-face. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://huggingface.co/api/models?limit=1
secondary
https://status.huggingface.co/
secondary
https://huggingface.co/openai-community/gpt2/resolve/main/config.json
secondary
https://huggingface.co/api/datasets?limit=1
secondary
https://huggingface.co/api/spaces?limit=1
secondary
https://router.huggingface.co/v1/models
secondary
https://datasets-server.huggingface.co/healthcheck
secondary
https://huggingface.co/docs

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: huggingface.co

RealUptime is not affiliated with Hugging Face; the name identifies what we checked, and nothing here speaks for Hugging Face's own team. We send a single web request to Hugging Face from 10 regions on our own schedule and time the response. We do not see inside Hugging Face's systems, do not use an account or real transaction, and are not the same signal Hugging Face's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Hugging Face is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.