Live / Incidents / Hetzner
Hetzner: Object Storage in location HEL1 degraded
Hetzner · hetzner.comImpact: object storageResolved2026-09-21 14:56 UTC
Public — what happened
Summary
Start: 2026-09-09T12:00:00+00:00 We are observing elevated response times and stalled requests. Monitoring 2026-09-21T14:56:05+00:00 Our cluster is back online; we are continuing to monitor the situation In_progress 2026-09-21T11:52:08+00:00 We were able to use a workaround to contain the problem to such an extent that it no longer directly affects buckets; however, it is still not entirely clear how the situation occurred. We are still investigating the issue. In_progress 2026-09-14T11:34:19+00:00 Unfortunately, the issue remains unresolved. Requests may still sometimes be delayed or time out for buckets located on the affected cluster. We have managed to narrow it down to certain low-level
Timeline
- Started — 2026-09-09 12:00 UTC
- Last update — 2026-09-21 14:56 UTC
- Resolved — 2026-09-21 14:56 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Hetzner against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Hetzner: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Hetzner report →