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
Resolved
Started
Lasted
2 h 27 min
Worst impact
Maintenance
Timeline
2 updatesPlanned
2 h 27 min 100%
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
19
Days with an incident
15
Median duration
1 h 37 min
This incident
Not comparable
Other Hetzner incidents
All incidentsHetzner·Object Storage in location fsn1 partially degraded
Hetzner Object Storage in location fsn1 is partially degraded. Requests to some buckets may fail or time out. Hetzner reports that it fixed the error and monitors the systems closely.
Hetzner·API failure for metrics
The API for metrics on the Cloud component did not work. Hetzner identified the issue and applied a fix. Hetzner reports that the problem is resolved after 4 hours and 57 minutes.
Hetzner·Object Storage in location HEL partially degraded
Hetzner reports that Object Storage in location HEL is partially degraded. Write operations may take a long time, fail, or time out. Hetzner is investigating and works on a fix.
Hetzner·Fault report on Cloud API and Hetzner Console
The Cloud API and the Hetzner Console did not work. Hetzner resolved the fault after 38 minutes. All systems are reachable again.
Hetzner·API failure for metrics
Hetzner reports that the API endpoints for metrics on Cloud, /servers/{id}/metrics and /loadbalancers/{id}/metrics, failed or returned incomplete data. Hetzner identified the issue and applied a fix. The incident is resolved and lasted 97 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