Minor impactResolvedAI/ML

Hugging Face incident: Elevated error rate - AWS CDN (Singapore)

Hugging Face reported this minor-impact incident on its official status page on Aug 7, 2026, 15:14 UTC. It was resolved after 8h.

Right now Hugging Face is operational. Live Hugging Face status →

🔔 Get alerted when Hugging Face has issuesFree · email alerts · no credit card
Aug 7, 2026, 15:14 UTC
started
Aug 7, 2026, 23:14 UTC
resolved
8h
duration
Minor
impact

Affected components

  • AWS CDN

Timeline

updates from Hugging Face's status page ↗
  1. resolvedAug 7, 2026, 23:14 UTC

    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.

  2. degradedAug 7, 2026, 15:14 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Hugging Face's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Hugging Face have incidents?

Hugging Face reported 3 incidents in the last 90 days. A typical incident lasted 15h 57m. See Hugging Face's uptime and incident history

Next: Slower downloads in the Asia-Pacific region (Sep 22, 2026) →
Hugging Face incident on Aug 7, 2026: Elevated error rate - AWS CDN (Singapore) · APIStatus.watch