outages.live
Live
Hugging FaceIncident ·

Slower downloads in the Asia-Pacific region

ResolvedOfficial update

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 latest update from Hugging Face.

State

Resolved

Started

Lasted

3 days

Worst impact

Degraded

Timeline

3 updates
Sep 22Sep 23Sep 24Sep 25Sep 25
DegradedUpdate postedDates in UTC

Degraded

3 days 100%

Updates

Times in UTC

As posted by Hugging Face

Resolved

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.

Degraded

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.

Degraded

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.

Affected components

1
AWS CDN

Hugging Face in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

5

Median duration

15 h 57 min

This incident

4.5× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 days
median 15 h 57 min
90 days agoToday

Other Hugging Face incidents

All incidents

Hugging Face·Degraded performance - AWS CDN (Singapore)

Hugging Face reports degraded performance on the AWS CDN in the Singapore region. The incident started at 06:30 UTC. Hugging Face resolved the issue at 08:46 UTC. The outage lasted 2 hours and 16 minutes.

Resolved

Hugging 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.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=huggingface
Slack
/feed subscribe https://outages.live/feed.xml?providers=huggingface

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane