Hugging Face service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for huggingface.co. Compare the regional responses with the problem you see in Hugging Face.
Find Hugging Face help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
The Hugging Face Hub, model downloads, Spaces and inference services have different failure paths.
The checker above requests huggingface.co from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Hugging Face action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse AI service checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Hub repositories, Spaces and inference endpoints need distinct support context.
Open the website in your browser and compare it with the result above.
Open Hugging Face help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Repository/model/Space, revision, endpoint or build step, client/library and error without tokens.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Hugging Face.
These are troubleshooting comparisons, not claims that Hugging Face is currently experiencing a particular incident.
Identify whether the failure concerns a repository artifact, a Space build/runtime or an inference endpoint.
Compare the exact service on its status page and inspect the failed request/build stage rather than testing only the homepage.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Hugging Face seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open huggingface.co in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Hugging Face issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Hugging Face support.
Run the huggingface.co check and compare its original timestamps and responses with your actual error. The Hugging Face Hub, model downloads, Spaces and inference services have different failure paths.
Use the community buttons on this page to share whether the service works for you. For help from Hugging Face, use the official help/reporting resource linked above. Hub repositories, Spaces and inference endpoints need distinct support context.
Identify whether the failure concerns a repository artifact, a Space build/runtime or an inference endpoint. Compare the exact service on its status page and inspect the failed request/build stage rather than testing only the homepage.
Repository/model/Space, revision, endpoint or build step, client/library and error without tokens.