- Level
- confirmed
- Worst impact
- Impact not stated
- Down Index
- 28of 100
Summary
Hetzner says Object Storage at the fsn1 location is partially affected and only partially available. Requests to certain buckets may fail or time out. The incident started at 00:40 UTC on 2026-11-14 and is under investigation.
Written by anthropic/claude-haiku-5.5 from Hetzner's own updates.
What to do
Check whether your product depends on Hetzner. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 3m it lasted.
Anything that failed between 2026-11-14 02:15 UTC and 2026-11-14 03:18 UTC may need a replay.Subscribe to Hetzner's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=hetzner works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Hetzner 1
- update
Start: 2026-11-14T00:40:27+00:00 Object Storage am Standort fsn1 ist derzeit teilweise nur eingeschränkt verfügbar. Anfragen an bestimmte Buckets können fehlschlagen oder wegen Zeitüberschreitung abbrechen. Wir untersuchen aktuell das Problem.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d21862dc68
Is Hetzner still down?
No, this incident was resolved 2026-11-14 03:18 UTC. For Hetzner's live state, see https://down.guide/providers/hetzner.
How long did it last?
1h 3m, from 2026-11-14 02:15 UTC to 2026-11-14 03:18 UTC, by the times Hetzner posted.
What caused it?
Hetzner hasn't published a root cause. If it does, it shows here.
Where does this come from?
Hetzner's official status page, https://status.hetzner.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.