Hugging Face Outage History

Hugging Face is up right now

Hugging Face had 12 outages in the last 2 years totaling 101h 25m of downtime — averaging 0.5 incidents per month.

There were 12 Hugging Face outages since January 26, 2026 totaling 101h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.huggingface.co

Minor September 24, 2026

Some GPU Jobs and Spaces fa...

Detected by Pingoru
Sep 24, 2026, 06:00 PM UTC
Resolved
Sep 25, 2026, 09:57 AM UTC
Duration
15h 57m
Affected: Spaces (Spaces Proxy)Jobs (Jobs)Spaces (Spaces Proxy)
Timeline · 2 updates
  1. investigating Sep 24, 2026, 06:00 PM UTC

    Between 18:00 UTC on September 24 and 09:10 UTC on September 25, some GPU Jobs and GPU Spaces failed to start. Affected jobs ended with an ERROR status before the container started.

  2. resolved Sep 25, 2026, 09:57 AM UTC

    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.

Read the full incident report →

Minor September 22, 2026

Slower downloads in the Asi...

Detected by Pingoru
Sep 22, 2026, 06:48 PM UTC
Resolved
Sep 25, 2026, 06:42 PM UTC
Duration
2d 23h
Affected: CDN (AWS CDN)CDN (AWS CDN)
Timeline · 3 updates
  1. investigating Sep 22, 2026, 06:48 PM UTC

    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. We're monitoring this closely and will post updates as things change.

  2. investigating Sep 22, 2026, 06:48 PM UTC

    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.

  3. resolved Sep 25, 2026, 06:42 PM UTC

    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.

Read the full incident report →

Minor August 7, 2026

Elevated error rate - AWS C...

Detected by Pingoru
Aug 07, 2026, 03:14 PM UTC
Resolved
Aug 07, 2026, 11:14 PM UTC
Duration
8h
Affected: CDN (AWS CDN)CDN (AWS CDN)
Timeline · 2 updates
  1. investigating Aug 07, 2026, 03:14 PM 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.

  2. resolved Aug 07, 2026, 11:14 PM 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.

Read the full incident report →

Minor July 16, 2026

Jobs recovered

Detected by Pingoru
Jul 16, 2026, 08:45 AM UTC
Resolved
Jul 16, 2026, 08:45 AM UTC
Duration
—
Timeline · 1 update
  1. investigating Jul 16, 2026, 07:57 AM UTC

    Jobs went down

Read the full incident report →

Major July 16, 2026

Hub unavailable

Detected by Pingoru
Jul 16, 2026, 08:30 AM UTC
Resolved
Jul 16, 2026, 10:07 AM UTC
Duration
1h 37m
Affected: Current status by service (Huggingface Hub)Current status by service (Git Hosting and Serving)Inference Endpoints (Inference Endpoints UI)Current status by service (Huggingface Hub)Current status by service (Git Hosting and Serving)
Timeline · 2 updates
  1. investigating Jul 16, 2026, 08:30 AM UTC

    Hugging Face platform is unavailable from most regions in the world due following a global outage from Amazon Web Services. We are working on a mitigation.

  2. resolved Jul 16, 2026, 10:07 AM UTC

    Services are back to nominal operations. Root cause confirmed to global Amazon Web Services outage.

Read the full incident report →

Minor June 30, 2026

Elevated error rate – AWS C...

Detected by Pingoru
Jun 30, 2026, 07:58 AM UTC
Resolved
Jun 30, 2026, 08:05 AM UTC
Duration
7m
Affected: CDN (AWS CDN)CDN (AWS CDN)
Timeline · 2 updates
  1. investigating Jun 30, 2026, 07:58 AM UTC

    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.

  2. resolved Jun 30, 2026, 08:05 AM UTC

    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.

Read the full incident report →

Minor June 10, 2026

Data serving slowness in As...

Detected by Pingoru
Jun 10, 2026, 07:00 AM UTC
Resolved
Jun 10, 2026, 10:50 AM UTC
Duration
3h 50m
Affected: CDN (AWS CDN)CDN (AWS CDN)
Timeline · 2 updates
  1. investigating Jun 10, 2026, 07:00 AM UTC

    We are experiencing slowness on large file downloads in Asia region since 7AM UTC. This only affects downloads via the huggingface CLI. Root cause identified and mitigation in progress.

  2. resolved Jun 10, 2026, 10:50 AM UTC

    Issue is solved, Asia traffic back to nominal bandwidth performances.

Read the full incident report →