Some GPU Jobs and Spaces failing to start
Hugging Face · Last saved provider status: resolved
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
- 24 Sep 2026, 18:00:00 UTC
- Provider record updated
- 25 Sep 2026, 09:57:00 UTC
- Explicit provider start
- 24 Sep 2026, 18:00: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.
- published update
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.
Seen in a saved revision at 06 Oct 2026, 13:59:07 UTC - published update
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.
Seen in a saved revision at 06 Oct 2026, 13:59:07 UTC