Hugging Face est-il en panne ?

Opérationnelinchangé depuis il y a 2 mois · depuis le 2026-09-13 23:00 UTC

Modèles, jeux de données et inférence.

Statut actuel
Opérationnel
Disponibilité 90 j
—
Incidents 90 j
14
Dernier incident
il y a 24 j

Gravité sur 90 jours

Temps cumulé d'incident
aucun
Rétablissement moyen
aucun
Incident le plus long
aucun

Sur les incidents publiés par le fournisseur. Maintenances exclues.

Interruptions sur 90 jours

Survolez ou touchez un jour pour le détail.
il y a 90 joursaujourd'hui
aucune interruptionmoins d'une heureune heure ou pluspas de donnée

Que faire si Hugging Face est en panne

Vérifier que ça ne vient pas de chez vous

Ouvrez un autre site. S'il se charge, votre connexion va bien.

Lire la source officielle

La page de statut de Hugging Face fait foi. C'est elle que nous relevons toutes les 5 minutes.

Page de statut officielle →

Voir ce qui se dit en direct

Une panne apparaît souvent sur X avant que Hugging Face ne la publie.

Signalements « Hugging Face down » sur X →

Savoir quand c'est rétabli

Plutôt que de recharger cette page, laissez votre adresse : l'alerte part dès la mise à jour.

Historique des incidents

Publié par Hugging Face

Maintenance · résolu2026-10-07 12:30 UTC

Maintenance: Scheduled maintenance: Inference Endpoints (H200)

Durée : 0 min → 2026-10-07 12:30 UTC · communication officielle

Maintenance completed

Maintenance · résolu2026-10-07 07:33 UTC

Maintenance: Scheduled maintenance: Inference Endpoints (H200)

Durée : 0 min → 2026-10-07 07:33 UTC · communication officielle

We're performing infrastructure maintenance on H200 Inference Endpoints today until around 12:30 UTC. Creating new H200 endpoints may be temporarily limited.

Mineur · résolu2026-09-25 18:42 UTC

Slower downloads in the Asia-Pacific region

Durée : 0 min → 2026-09-25 18:42 UTC · communication officielle

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.

Majeur · résolu2026-09-25 12:18 UTC

Slower downloads in the Asia-Pacific region

Durée : 0 min → 2026-09-25 12:18 UTC · communication officielle

The Asia Pacific region continues to experience degraded performance due to impaired underlying network capacity. The root cause is identified as the rupture of a subsea cable between China and Japan, rerouting traffic onto the remaining capacity. We continue to monitor the situation and are diverting part of traffic to healthy regions.

Mineur · résolu2026-09-25 09:57 UTC

Some GPU Jobs and Spaces failing to start

Durée : 0 min → 2026-09-25 09:57 UTC · communication officielle

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.

Mineur · résolu2026-09-24 18:00 UTC

Some GPU Jobs and Spaces failing to start

Durée : 0 min → 2026-09-24 18:00 UTC · communication officielle

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.

Mineur · résolu2026-09-22 18:48 UTC

Slower downloads in the Asia-Pacific region

Durée : 0 min → 2026-09-22 18:48 UTC · communication officielle

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 tra

Maintenance · résolu2026-09-16 09:00 UTC

Maintenance: Scheduled maintenance: Hub

Durée : 0 min → 2026-09-16 09:00 UTC · communication officielle

Maintenance completed

Maintenance · résolu2026-09-16 07:00 UTC

Maintenance: Scheduled maintenance: Hub

Durée : 0 min → 2026-09-14 14:19 UTC · communication officielle

During a short window inside this period (roughly 20 minutes) write operations on the Hub may fail while we migrate database infrastructure. This includes creating repositories, pushing commits and uploading files, opening or commenting on pull requests and discussions, and changing account, organization or billing settings. It affects both the UI and the API. Reads are not affected: browsing the

Maintenance · résolu2026-09-02 08:00 UTC

Scheduled maintenance: Hub

Durée : 0 min → 2026-09-02 08:00 UTC · communication officielle

Maintenance completed

Maintenance · résolu2026-09-02 07:00 UTC

Maintenance: Scheduled maintenance: Hub

Durée : 0 min → 2026-08-31 11:14 UTC · communication officielle

During a brief window (approximately 5–10 minutes), uploads and commits to repositories may temporarily fail or need to be retried while we upgrade database infrastructure. This affects both the UI and the API. Downloads, reads, and browsing are not affected, and no action is needed on your end.

Maintenance · résolu2026-08-17 07:00 UTC

Maintenance: Scheduled maintenance: Spaces

Durée : 0 min → 2026-08-12 14:40 UTC · communication officielle

During a brief window (approximately 5–10 minutes), write and management operations on Spaces (creating or duplicating a Space, changing hardware or settings, pausing/restarting, and updating secrets and variables) may temporarily return a 503 error while we upgrade infrastructure. This affects both the UI and the API. Reads and already-running Spaces are not affected, and no action is needed on y

Majeur · résolu2026-08-07 23:14 UTC

Elevated error rate - AWS CDN (Singapore)

Durée : 0 min → 2026-08-07 23:14 UTC · communication officielle

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.

Majeur · résolu2026-08-07 15:14 UTC

Elevated error rate - AWS CDN (Singapore)

Durée : 0 min → 2026-08-07 15:14 UTC · communication officielle

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.

Maintenance · résolu2026-07-30 07:00 UTC

Maintenance: Scheduled maintenance: Inference Endpoints

Durée : 0 min → 2026-07-28 10:07 UTC · communication officielle

During a short window within this period (roughly 5–10 minutes), endpoint management operations (creating, updating, pausing, or resuming endpoints) may briefly return a 503 ("temporarily unavailable due to maintenance") while we complete infrastructure upgrades. Running endpoints and inference requests are not affected, and no action is needed on your end.

Maintenance · résolu2026-07-22 07:00 UTC

Maintenance: Scheduled maintenance: Inference Endpoints

Durée : 0 min → 2026-07-13 10:27 UTC · communication officielle

During a short window inside this period (roughly 5–10 minutes) endpoint management operations (creating, updating, pausing, or resuming endpoints) may briefly return a 503 ("temporarily unavailable due to maintenance") while we complete upgrades to infrastructure. Running endpoints and inference requests are not affected, and no action is needed on your end.

Mineur · résolu2026-07-16 10:07 UTC

Hub unavailable

Durée : 0 min → 2026-07-16 10:07 UTC · communication officielle

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

Mineur · résolu2026-07-16 08:43 UTC

Hub unavailable

Durée : 0 min → 2026-07-16 08:43 UTC · communication officielle

We are mitigating the issue, and services are coming back up.

Mineur · résolu2026-07-16 08:30 UTC

Hub unavailable

Durée : 0 min → 2026-07-16 08:30 UTC · communication officielle

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.

Maintenance · résolu2026-07-08 07:00 UTC

Maintenance: Scheduled maintenance: Jobs

Durée : 0 min → 2026-07-07 13:18 UTC · communication officielle

During a short window inside this period (roughly 5–10 minutes) write operations may briefly return a 503 ("temporarily unavailable due to maintenance") while we complete upgrades to infrastructure. Reads and already-running jobs are not affected, and no action is needed on your end.

Majeur · résolu2026-06-30 08:05 UTC

Elevated error rate – AWS CDN (Singapore)

Durée : 0 min → 2026-06-30 08:05 UTC · communication officielle

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.

Majeur · résolu2026-06-30 07:58 UTC

Elevated error rate – AWS CDN (Singapore)

Durée : 0 min → 2026-06-30 07:58 UTC · communication officielle

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.

Mineur · résolu2026-06-10 10:50 UTC

Data serving slowness in Asia region

Durée : 0 min → 2026-06-10 10:50 UTC · communication officielle

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

Mineur · résolu2026-06-10 07:00 UTC

Data serving slowness in Asia region

Durée : 0 min → 2026-06-10 07:00 UTC · communication officielle

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.

Être alerté quand Hugging Face tombe

Gratuit, 3 fournisseurs, sans carte bancaire. Vous recevez un email dès qu'un incident est publié sur la page de statut officielle.

Source officielle

Données issues de la page de statut publique de Hugging Face.

Page de statut officielle
Personne ne surveille encore Hugging Face via Upstream Status.

Badge pour votre site

Affichez le statut de Hugging Face chez vous. Mis à jour automatiquement, même adresse que cette page.

Hugging Face — Opérationnel
<a href="https://www.upstreamstatus.com/status/hugging-face"><img src="https://www.upstreamstatus.com/badge/hugging-face" width="280" height="64" alt="Hugging Face status" /></a>

Autres services Intelligence artificielle

AnthropicOpérationnel
ElevenLabsOpérationnel
Google GeminiOpérationnel
GroqOpérationnel
Mistral AIOpérationnel
OpenAIOpérationnel

Questions fréquentes

Hugging Face est-il en panne actuellement ?

Au dernier relevé (2026-10-31 22:17 UTC), Hugging Face est en état « Opérationnel » d'après sa page de statut officielle. Aucun incident en cours n'est publié.

Quelle est la disponibilité de Hugging Face sur 90 jours ?

L'historique de Hugging Face est en cours de constitution sur Upstream Status.

Comment être prévenu automatiquement d'une panne de Hugging Face ?

Créez une alerte gratuite sur Upstream Status : dès qu'un incident est publié sur la status page de Hugging Face, vous recevez un email (ou une notification Slack/webhook avec un plan payant).