Is Hugging Face down?

Last checked 4m ago
Current status
Hugging Face is up

No incidents right now.

Hugging Face is operational right now. Last checked 4m ago; the most recent incident resolved 23d ago.

Real-time Hugging Face status, recent outages, and incident history: pulled directly from Hugging Face's official status page at status.huggingface.co every 5 minutes. Pingoru tracks 13 Hugging Face services and has captured 9 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Hugging Face reports a new incident, free for 3 monitors, no credit card.

Users who monitor Hugging Face also follow these AI services: Tungsten Automation Americas Together AI Laserfiche Observe.AI Quest Retell AI Braintrust Cerebras Modal Forethought AI View all 8,000+ providers
Hugging Face uptime 98.89% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 15h 57m
    Started Sep 24, 2026, 06:00 PM UTC · Resolved Sep 25, 2026, 09:57 AM UTC
    Spaces ProxyJobsSpaces ProxyJobs
    Timeline · 2 updates
    • 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.

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

    Latest: 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, resta…

  2. Resolved 2d 23h
    Started Sep 22, 2026, 06:48 PM UTC · Resolved Sep 25, 2026, 06:42 PM UTC
    AWS CDNAWS CDN
    Timeline · 2 updates
    • 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.

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

    Latest: 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 traffi…

  3. Resolved 8h
    Started Aug 07, 2026, 03:14 PM UTC · Resolved Aug 07, 2026, 11:14 PM UTC
    AWS CDNAWS CDN
    Timeline · 2 updates
    • 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.

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

    Latest: 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. Download…

  4. Resolved –
    Started Aug 06, 2026, 06:48 PM UTC · Resolved Aug 06, 2026, 06:48 PM UTC
  5. Resolved –
    Started Aug 06, 2026, 06:46 PM UTC · Resolved Aug 06, 2026, 06:46 PM UTC

Incident record

Since April 2026 · Better Stack · 13 components checked every 5 minutes
31incidents recorded
31last 12 months
5last 90 days
3 hourstypical duration, 12 months

The longest incident in the last year, Slower downloads in the Asia-Pacific region on September 22, 2026, ran for 3 days. 7 maintenance windows announced in the same period.

Most affected components, last 12 months

  • AWS CDN4
  • AWS CDN4
  • Git Hosting and Serving1
  • Git Hosting and Serving1
  • Huggingface Hub1

Latest incidents

  • Some GPU Jobs and Spaces failing to start September 24, 2026 · 16 hours · degraded service

    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…

  • Slower downloads in the Asia-Pacific region September 22, 2026 · 3 days · degraded service

    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…

  • Elevated error rate - AWS CDN (Singapore) August 7, 2026 · 8 hours · degraded service

    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…

Outage history

Past 90 days · 5 incidents View full outage history →