Past Incidents

Since August 27th, 2025, both of our centralized mail gateways (mailgate01.uberspace.is, mailgate02.uberspace.is) seem to be on a Microsoft blocklist.

When we first reported this to Microsoft, we were told that "Nothing was detected to prevent your mail from reaching Outlook.com customers".

When we insisted that there are indeed delivery problems, Microsoft suddenly seemed to agree and declared that "these IPs are not eligible for mitigation" because they show "a pattern of irregular mail traffic", referring us to Microsoft's Smart Network Data Services (SNDS) - a debugging service that we are subscribed to for years, that we regularly check, and that continues to tell us that "All of the specified IPs have normal status".

We are also subscribed to Microsoft's Junk Mail Reporting Program (JMRP) so we directly receive complaints. Those complaints are usually bogus and often refer to mail that's clearly not spam at all, but Microsoft customers marked them as spam nevertheless. SNDS itself declares a complaint rate of <0.1% for mails coming from our mail gateways.

Generally, if there's any kind of spam incident that we get aware of by any means (our own queue monitoring, external abuse reports, our IPs appearing on a well-known blocklist, ...) we immediately investigate and block mail accounts that happen to send spam (e.g. because their password got compromised). No other well-known blocklist reports our mail gateways as problematic.

We continue to communicate with Microsoft's "Outlook.com Deliverability Support Team" and try to have our mail gateways removed from their blocklist. If and when they do is not under our control.

While working on the SSH issue some hosts where stuck in a reboot process that resulted in an outage for about 60 minutes. The affected hosts where:

• borrelly.uberspace.de
• carina.uberspace.de
• cressida.uberspace.de
• gale.uberspace.de
• halimede.uberspace.de
• hercules.uberspace.de
• johnson.uberspace.de
• kopff.uberspace.de
• shoemaker.uberspace.de
• tritton.uberspace.de
• wolf.uberspace.de

While trying to fix an issue with Let's Encrypt certificates updating too often, we inadvertently broke the HTTPS config on ferdinand.uberspace.de. The issue has been fixed.

The host is down because the underlying piece of hardware crashed. We are rebooting it on a different one.

The system needs to be rebooted and will reappear in a few minutes.

We're currently experiencing packet loss at our FRA4 location and investigate.

There is a major outage at our FRA3 site. We're investigating.

We encounter network problems due to a failed switch at our site FRA4

Mails to Microsoft accounts are rejected, we are not given a reason and our request to unblock our mailgates is not responded to. We change the mail gateways as far as we can, but unfortunately the block seems to take effect after a few hours on the gateway we changed.

Google Mail (googlemail.com; gmail.com) no longer accepts mails when the sender domain does not have valid SPF and/or DKIM set up. To set up SPF and/or DKIM for your domain hosted at Uberspace.de, please refer to our manual.