Live / Incidents / Hetzner
Hetzner: Object Storage in location fsn1 for some buckets degraded
Hetzner · hetzner.comImpact: object storageResolved2026-09-15 20:16 UTC
Public — what happened
Summary
Start: 2026-09-15T11:59:00+00:00 We are experiencing memory pressure on our systems that causes daemons to crash. For most requests no impact should be expected; But sometimes requests may be delayed or in rare cases aborted. We are investigating the root cause. Monitoring 2026-09-15T20:16:22+00:00 We identified the root cause and blocked it. We will extend our Monitoring in a first step in order to get alerted to such issues earlier. The system has recovered. We're investigating measures to prevent the specific triggers. In_progress 2026-09-15T17:41:41+00:00 We could narrow down the problem to a single component, and could successfully lower memory usage to non-critical levels. We are curre
Timeline
- Started — 2026-09-15 11:59 UTC
- Last update — 2026-09-15 20:16 UTC
- Resolved — 2026-09-16 08:51 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 →