Maintenance work on the webmail system (webmail.your-server.de)
Due to maintenance work, our webmail system will be unavailable during this specified time period. This will affect the login at https://webmail.your-server.de, as well as ActiveSync for the managed server and web hosting packages. As an alternative during this time, you can access your emails via an email client. You can set up an email client as follows: https://docs.hetzner.com/konsoleh/account-management/email/setting-up-an-email-account/ Thank you for your understanding.
The latest update from Hetzner.
State
Planned
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Hetzner
Due to maintenance work, our webmail system will be unavailable during this specified time period. This will affect the login at https://webmail.your-server.de, as well as ActiveSync for the managed server and web hosting packages. As an alternative during this time, you can access your emails via an email client. You can set up an email client as follows: https://docs.hetzner.com/konsoleh/account-management/email/setting-up-an-email-account/ Thank you for your understanding.
Affected components
1Hetzner in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
4
Median duration
58 min
This incident
Not comparable
Other Hetzner incidents
All incidentsHetzner·Cloud Resource Creation Delay
Hetzner Cloud had a delay in creating and modifying resources. The problem is resolved and the outage lasted 45 minutes.
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.
Hetzner·DHCP degraded in FSN1 and NBG1
The issue was found and solved.
Hetzner·Fault report on mirror (mirror.hetzner.de / download.hetzner.com / packages.hetzner.com)
We have fixed the fault. The system is accessible again.
Hetzner·Object Storage in location nbg1 partially degraded
The problem is fixed.
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.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.
https://outages.cc/feed.xml?providers=hetzner/feed subscribe https://outages.cc/feed.xml?providers=hetznerFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane