Is Hugging Face Down?
Hugging Face Hub, Inference Endpoints, Spaces, and model hosting services.
Official status data last reflected here:
[ STATUS AT A GLANCE ]
System Components
Current status of individual Hugging Face services
Hugging Face down? Route around it.
When Hugging Face has issues, Bifrost automatically routes your requests to a healthy alternative provider. Zero code changes. 99.999% effective uptime.
About Hugging Face
What Hugging Face does, where the data on this page comes from, and recent reliability
[ ABOUT HUGGING FACE ]
About Hugging Face
Hugging Face provides Hugging Face Hub, Inference Endpoints, Spaces, and Model hosting. Hugging Face outages can affect both developer workflows and live inference systems, especially when teams rely on Hub access, endpoints, or Spaces for demos and tooling.
This page pulls data from Hugging Face's official status page to show current service health, any active incidents, and a history of recent issues, all in one view.
[ DATA SOURCES ]
Component history and status reports
Hugging Face publishes per-component availability history and status reports. Incident detail may be lighter than providers using Statuspage.
- Data pulled from Hugging Face's official status page (status.huggingface.co)
- Refreshed every 60 seconds
- Covers Hugging Face Hub, Inference Endpoints, Spaces, and Model hosting
- Includes component-level availability history and published status reports
[ RELIABILITY ]
Recent reliability
- 3 incidents reported over the last 90 days.
- Last reported incident was 26 days ago.
- All 8 monitored components are currently operational.
- Most frequently affected: AWS CDN, Spaces Proxy, and Jobs.
[ COMMON USE CASES ]
How teams use Hugging Face
Hugging Face outages can affect both developer workflows and live inference systems, especially when teams rely on Hub access, endpoints, or Spaces for demos and tooling.
Incidents & Maintenance
Active incidents, scheduled maintenance, and incident history for Hugging Face
Scheduled Maintenance
Scheduled maintenance: Inference Endpoints (H200)
ScheduledOct 7, 2026, 7:33 AM UTC to Oct 7, 2026, 12:30 PM UTC
Scheduled maintenance: Hub
ScheduledSep 16, 2026, 7:00 AM UTC to Sep 16, 2026, 9:00 AM UTC
Scheduled maintenance: Hub
ScheduledSep 2, 2026, 7:00 AM UTC to Sep 2, 2026, 8:00 AM UTC
Scheduled maintenance: Spaces
ScheduledAug 17, 2026, 7:00 AM UTC to Aug 17, 2026, 9:00 AM UTC
Active Incidents (3)
Slower downloads in the Asia-Pacific region
Sep 22, 2026
The upstream network capacity issue affecting our Singapore CDN location has been resolved, and download performance for Asia-Pacific users is back to normal. We've returned traffic routing to its usual configuration. Thank you for your patience.
The Asia Pacific region continues to experience degraded performance due to impaired underlying network capacity. The root cause is identified as the rupture of a subsea cable between China and Japan, rerouting traffic onto the remaining capacity. We continue to monitor the situation and are diverting part of traffic to healthy regions.
We're seeing slower download speeds for some users in the Asia-Pacific region who are served by our Singapore CDN location. Reduced network capacity between cloud regions is impacting our ability to download files that aren't already cached in the region. We are not seeing an increased error rate, so downloads should complete successfully. To reduce the impact, we're sending some Asia-Pacific traffic to our other CDN locations. Some users may see higher latency while this is in place. We're monitoring this closely and will post updates as things change.
Some GPU Jobs and Spaces failing to start
Sep 24, 2026
The issue is resolved. If your job failed between 18:00 UTC on September 24 and 09:10 UTC on September 25, please resubmit it. If your Space is still showing a Runtime error, restart it from the Space settings.
Between 18:00 UTC on September 24 and 09:10 UTC on September 25, some GPU Jobs and GPU Spaces failed to start. Affected jobs ended with an ERROR status before the container started.
Elevated error rate - AWS CDN (Singapore)
Aug 7, 2026
Our fix is now in place and this incident is resolved. Applying it caused one final short period of failed downloads between 23:00 and 23:14 UTC, as we noted could happen. Downloads from the Singapore region have been stable since, and we have added capacity to prevent this from recurring. We are sorry for the disruption.
Some file downloads from our Singapore region (ap-southeast-1) failed with 500 errors during two short periods, starting at 15:14 UTC. Downloads are normal again now. The cause is not fully resolved, so short bursts of errors can return until our fix is in place. Other CDN regions are not affected. We are sorry for the disruption.
Frequently Asked Questions
Is Hugging Face down right now?
Check the status indicator at the top of this page. It pulls directly from Hugging Face's official status page. If Hugging Face is experiencing any issues, you'll see it reflected here. This real-time monitoring helps teams quickly identify whether performance problems are caused by Hugging Face infrastructure or their own systems.
What does this Hugging Face status page track?
This page tracks Hugging Face Hub, Inference Endpoints, Spaces, and Model hosting using data from Hugging Face's official status page. You can see current component health, active incidents, and a history of past issues. This visibility is crucial for teams building resilient AI applications that need to route around provider outages.
How often is Hugging Face status updated here?
We check Hugging Face's status page every 60 seconds to ensure you get near real-time status updates. How quickly issues show up here depends on how fast Hugging Face updates their own official status. For production systems that need instant failover, Bifrost can automatically detect and route around degraded providers.
Why monitor Hugging Face status?
Hugging Face outages can affect both developer workflows and live inference systems, especially when teams rely on Hub access, endpoints, or Spaces for demos and tooling. Real-time status monitoring enables proactive incident response and helps teams decide when to route traffic to alternative providers for maximum uptime.
What should I do when Hugging Face goes down?
When Hugging Face experiences an outage, the best practice is automatic failover to alternative AI providers. Bifrost is an open-source AI gateway that automatically detects Hugging Face degradation and routes LLM traffic to healthy alternatives like Replicate, Together AI, keeping your application running with zero manual intervention. This intelligent routing ensures your users never experience downtime from a single provider's issues.
How can I prevent Hugging Face downtime from affecting my application?
Production AI applications should never depend on a single provider. Bifrost AI Gateway provides automatic multi-provider failover, intelligent load balancing, and health-based routing. When Hugging Face degrades, Bifrost instantly routes requests to operational alternatives while maintaining API compatibility. This architecture approach is used by teams running mission-critical AI features.
What are common causes of Hugging Face outages and degraded performance?
Based on incident history, Hugging Face issues most frequently affect AWS CDN, Spaces Proxy, and Jobs. Common causes include infrastructure scaling issues, regional cloud provider problems, API gateway overload, and deployment errors. Teams using Bifrost can configure automatic routing rules based on component-level status to minimize impact.
Alternative Providers for Automatic Failover
When Hugging Face experiences issues, Bifrost AI Gateway can automatically route your LLM traffic to these alternatives
💡 Build resilient AI apps: Configure Bifrost to automatically detect Hugging Face outages and route requests to healthy alternatives. This multi-provider approach ensures your application maintains uptime even when individual providers experience issues. Learn more about Bifrost AI Gateway
Hugging Face Models & Pricing
Hugging Face offers 190 models across 1 mode (190 chat)