Live / Hetzner / Incident
Hetzner: Fault report for Cloud DNS API and reverse DNS APIs (Primary IP, Floating IPs, Cloud Server, Load Balancer)
Hetzner · hetzner.comResolved2026-11-03 09:42 UTC
Public — what happened
Summary
Hetzner said it ran into a problem with its Cloud DNS API and the reverse DNS interfaces used for Primary IPs, Floating IPs, Cloud Servers and Load Balancers, starting at 08:58 UTC on 2026-11-03. The company said it identified the cause at 09:40 UTC and that its technicians were working on a fix. By 09:42 UTC Hetzner reported the cause as resolved and said it was monitoring its systems, and the incident is marked resolved.
Timeline
- Started — 2026-11-03 08:58 UTC
- Resolved — 2026-11-03 09:42 UTC · 45 min after it started
What SquidGrid measured
SquidGrid measured 166 internet paths into Hetzner’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
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 →
More from Hetzner
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.