Replacement of power supply components and UPS in NBG1-DC2
During this time, technicians will be upgrading various power supply components, including the UPS system in NBG1-DC2 . The work should not negatively affect our server systems. You can see which data center your server is located in by doing a trace route (for example, by using https://dnstools.ws/).
The latest update from Hetzner.
State
Planned
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Hetzner
During this time, technicians will be upgrading various power supply components, including the UPS system in NBG1-DC2 . The work should not negatively affect our server systems. You can see which data center your server is located in by doing a trace route (for example, by using https://dnstools.ws/).
Affected components
1Hetzner in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
6
Median duration
1 h
This incident
Not comparable
Other Hetzner incidents
All incidentsHetzner·Fault report on Hetzner Console
Hetzner reports that a fault made the Cloud API and the Hetzner Console unavailable. The fault is resolved. All systems are reachable again. The outage lasted 1 hour and 2 minutes.
Hetzner·Cloud Router fault nbg1-cloud1-core_spine_rdev1
The fault has been fixed. All systems are accessible again
Hetzner·Outage of DHCP and Rescue Boot in FSN1
DHCP does not work in FSN1. This affects the rescue boot and installations through Robot. Hetzner reports that the issue is resolved. The outage lasted about 7 hours and 34 minutes.
Hetzner·Cloud Resource Creation Delay
Hetzner Cloud had a delay in creating and modifying resources in the Cloud component. The problem is resolved. The outage lasted 45 minutes. Creating and modifying resources works as usual.
Hetzner·Fault report for Cloud DNS API and reverse DNS APIs (Primary IP, Floating IPs, Cloud Server, Load Balancer)
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.
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.
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.
https://outages.live/feed.xml?providers=hetzner/feed subscribe https://outages.live/feed.xml?providers=hetznerFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane