Hugging Face Outage Check

Is Hugging Face Down Right Now?

✅ Hugging Face is up and working normally. Checked: 5:10 PM (GMT+8).

Auto-refreshing live data in 60s

Component Breakdown

Specific service features status
ComponentStatus
API Portal Operational
Core Service Operational
OAuth Integrations Operational
Website Operational

90-Day Uptime Performance

History & recovery averages
99.444%
Uptime
64m
MTTR
6.7
Avg Incidents / Mo
90 Days AgoToday

Past Incidents & Outage Archives

View Full 2026 Archive

Hugging Face API Gateway Timeout and Increased Error Rates

Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.

Duration: 36m Affected: API Requests, API Portal

Hugging Face API Gateway Timeout and Increased Error Rates

Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.

Duration: 28m Affected: API Requests, API Portal

Hugging Face API Gateway Timeout and Increased Error Rates

Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.

Duration: 44m Affected: API Requests, API Portal

Hugging Face Network Congestion in Transit Provider

A major tier-1 network transit provider experienced packet loss in Europe and North America.

Duration: 52m Affected: Website, DNS Services

Hugging Face Database Failover and Connection Backlog

A hardware failure on the primary database cluster triggered an automatic failover to the replica.

Duration: 1h 4m Affected: Core Service, Website

Community Outage Pulse

Are you having problems with Hugging Face?

Submit your report to help alert other developers.

Downtime Reports: Last 2 Hours
2 Hours AgoNow

Troubleshooting Guide

  1. 1
    Hard Refresh
    Bypass cache (Ctrl+F5 or Cmd+Shift+R).
  2. 2
    Flush DNS
    Run ipconfig /flushdns.

Uptime Alternatives

GitHub

Leading developer platform.

View Status

Slack

Real-time team communication.

View Status

Frequently Asked Questions

Yes, Hugging Face maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 64 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.

Related services you might be checking