ARCHIVED OFFICIAL INCIDENT

Elevated error rate - AWS CDN (Singapore)

Hugging Face · Last saved provider status: resolved

Current service report →
This is historical evidence.

The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.

Saved event details

Provider status
resolved
Provider impact
resolved
Provider record created
07 Aug 2026, 15:14:00 UTC
Provider record updated
07 Aug 2026, 23:14:00 UTC
Explicit provider start
07 Aug 2026, 15:14:00 UTC
Explicit provider end
Not available

Affected components reported by the provider

Component associations were not provided or have not been recovered for this saved revision.

These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.

A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.

Hugging Face's published platform resources and current or upcoming reports. These are provider reports, not independent checks of any model, account or region.

Provider updates in saved revisions

Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.

  1. published update

    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.

    Seen in a saved revision at 06 Oct 2026, 13:59:07 UTC
  2. published update

    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.

    Seen in a saved revision at 06 Oct 2026, 13:59:07 UTC