outages.live
Live
HetznerIncident ·

Fault report for Cloud DNS API and reverse DNS APIs (Primary IP, Floating IPs, Cloud Server, Load Balancer)

ResolvedOfficial update
0

Hetzner reports that the Cloud DNS API and the reverse DNS APIs for Primary IPs, Floating IPs, Cloud Servers and Load Balancers did not work. Managed Certificate issuance was also affected. Hetzner reports that the outage is resolved. It lasted about 58 minutes.

State

Resolved

Started

Lasted

58 min

Worst impact

Major outage

Timeline

5 updates
08:5809:1209:2609:4109:55
Major outageUpdate postedTimes in UTC

Investigating

44 min 77%

Identified

3 min 5%

Monitoring

10 min 18%

Updates

Times in UTC

As posted by Hetzner

Resolved

The cause has be resolved, we currently monitor the systems.

Monitoring

The cause has be resolved, we currently monitor the systems.

Identified

The cause of the issue has been identified. Our technicians are working to resolve the issue.

Investigating

We have encountered an issue with the Cloud DNS API, the reverse DNS APIs (Primary IPs, Floating IP, Cloud Server and Load Balancers) and Managed Certificate issuance

Investigating

We have encountered an issue with the Cloud DNS API and the reverse DNS APIs (Primary IPs, Floating IP, Cloud Server and Load Balancers)

Affected components

1
Cloud

Hetzner in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

6

Days with an incident

4

Median duration

1 h 16 min

This incident

24% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 h 15 min
median 1 h 16 min
90 days agoToday

Other Hetzner incidents

All incidents

Hetzner·DHCP degraded in FSN1 and NBG1

The issue was found and solved.

Resolved

Hetzner·Fault report on mirror (mirror.hetzner.de / download.hetzner.com / packages.hetzner.com)

We have fixed the fault. The system is accessible again.

Resolved

Hetzner·Object Storage in location nbg1 partially degraded

The problem is fixed.

Resolved

Hetzner·Object Storage in location nbg1 partially degraded

We have fixed the error. All systems are reachable again.

Resolved

Hetzner·API failure for metrics

The problem is fixed.

Resolved

Follow Hetzner

Your coding agent knows when Hetzner is down, and tells you when a failure is theirs, not yours. You can also get Hetzner incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "hetzner" and tell me if Hetzner has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=hetzner
Slack
/feed subscribe https://outages.live/feed.xml?providers=hetzner

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane