- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- ap-southeast-1, apac
What to do
Check whether you use Hugging Face in ap-southeast-1, apac. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 7m it lasted.
Anything that failed between 2026-06-30 07:58 UTC and 2026-06-30 08:05 UTC may need a replay.Subscribe to Hugging Face's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=huggingface works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Hugging Face 2
- update
Between 07:58 and 08:05 UTC, the AWS CDN returned an elevated rate of HTTP 500 errors for a portion of requests in the Asia-Pacific (Singapore / ap-southeast-1) region. The cause was a transient internal service disruption, which has been mitigated.
provider
- resolved
Resolved. Error rates returned to normal at 08:05 UTC and the CDN is operating normally. The disruption lasted approximately 7 minutes. We apologize for any inconvenience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-75d85885c4
Is Hugging Face still down?
No, this incident was resolved 2026-06-30 08:05 UTC. For Hugging Face's live state, see https://down.guide/huggingface.
How long did it last?
7m, from 2026-06-30 07:58 UTC to 2026-06-30 08:05 UTC, by the times Hugging Face posted.
What was affected?
Hugging Face named in ap-southeast-1, apac.
What caused it?
Hugging Face hasn't published a root cause. If it does, it shows here.
Where does this come from?
Hugging Face's official status page, https://status.huggingface.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.