Degraded performance - AWS CDN (Singapore)
Hugging Face reports degraded performance on the AWS CDN in the Singapore region. The problem started at 06:30 UTC. Hugging Face is investigating. Downloads of files that are not yet cached may be slower than usual. Error rates remain low.
State
Degraded
Started
Ongoing for
2 h 20 min
Worst impact
Degraded
Timeline
1 updateDegraded
2 h 20 min 100%
Updates
Times in UTCAs posted by Hugging Face
We are investigating degraded performance on the AWS CDN in the Singapore region since 06:30 UTC. Downloads of files that are not yet cached may be slower than usual. Error rates remain low. We will share an update as soon as we know more.
Affected components
1Hugging Face in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
5
Median duration
43 h 56 min
This incident
95% shorter than the median
Other Hugging Face incidents
All incidentsHugging Face·Some GPU Jobs and Spaces failing to start
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.
Hugging Face·Slower downloads in the Asia-Pacific region
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.
Follow Hugging Face
Your coding agent knows when Hugging Face is down, and tells you when a failure is theirs, not yours. You can also get Hugging Face incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "huggingface" and tell me if Hugging Face has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=huggingface/feed subscribe https://outages.live/feed.xml?providers=huggingfaceFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane