outages.live
Live
HetznerMaintenance ·

Replacement of power supply components and UPS in NBG1-DC2

MaintenanceOfficial update

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 UTC

As posted by Hetzner

Planned

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

1
NBG1-DC2

Hetzner in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

6

Median duration

58 min

This incident

Not comparable

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

2 h 15 min
median 58 min
90 days agoToday

Other Hetzner incidents

All incidents

Hetzner·Fault report on Hetzner Console

The Hetzner Console and the Cloud API in the Cloud component did not work. Hetzner restored the systems and now monitors them. Hetzner reports that the outage is resolved. It lasted about 62 minutes.

Resolved

Hetzner·Cloud Router fault nbg1-cloud1-core_spine_rdev1

The fault has been fixed. All systems are accessible again

Resolved

Hetzner·Cloud Resource Creation Delay

Hetzner Cloud had a delay in creating and modifying resources. The problem is resolved and the outage lasted 45 minutes.

Resolved

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 resolved the outage after 58 minutes.

Resolved

Hetzner·DHCP degraded in FSN1 and NBG1

The issue was found and solved.

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.cc/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.cc/feed.xml?providers=hetzner
Slack
/feed subscribe https://outages.cc/feed.xml?providers=hetzner

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane