Table of Contents
Is Hetzner webmail down and how can I access my emails?
Service Status Report: Hetzner and ING Bank (February 3, 2026)
Users across Europe have reported concurrent service interruptions affecting both financial and hosting infrastructure today, February 3, 2026. While these incidents appear technically unrelated, their simultaneous occurrence has impacted business workflows. Below is a technical breakdown of the outages and verify solutions for restoring connectivity.
ING Bank: Application Connectivity Failures
While the ING public-facing website remains accessible and loads quickly, internal application routing is failing. Users can successfully authenticate via the mobile app, but the session terminates immediately post-login with a generic error message. This behavior suggests a backend API failure rather than a total system blackout. Third-party monitoring data from allestörungen.de corroborates this, showing a sharp spike in user reports.
Advisor Note: Avoid repeated login attempts, as this may trigger automated security lockouts. Wait for the API gateway to stabilize.
Hetzner Online: Mail Server Infrastructure Outage
Hetzner has confirmed a specific incident affecting their Managed Server and Webhosting environments. Unlike a general network outage, this issue was isolated to their centralized mail relays.
Incident Timeline (CET):
- Start: February 3, 2026, 06:20
- End: February 3, 2026, 08:57
- Status: Resolved
Technical Root Cause
The disruption took down mail.your-server.de and webmail.your-server.de. These are the default incoming/outgoing mail servers used by standard configurations. When these central nodes fail, email clients attempting to route traffic through them lose connection, even if the actual hosting server storing the data is online.
Workaround Strategy for Email Access
Although the incident is marked as resolved, understanding the bypass method is critical for future continuity. The failure occurred at the generic alias level. The physical server hosting your data remained operational.
To bypass future alias outages, reconfigure your local email client (Outlook, Thunderbird, Apple Mail) manually:
- Locate Your Host: Log into the konsoleH administration panel.
- Identify the Server: Select your domain to view the specific hosting server name in the overview (e.g., dedi123.your-server.de instead of the generic mail.your-server.de).
- Update Settings: Replace the incoming (IMAP/POP3) and outgoing (SMTP) server addresses in your client settings with this direct server name.
This configuration routes your connection directly to the hardware, bypassing the shared alias layer that experienced the fault.