vulpecula.uberspace.de IPv4 connection issues Thursday 25th June 2026 12:46:00


The host vulpecula.uberspace.de isn't reachable by IPv4 anymore, while IPv6 works fine. As IPv4 works fine for all other hosts, it's not yet obvious what's the reason for it. We spotted quite some DDoS attacks over the last days and suspect that the attack got bigger and our IP upstream might have temporarily blocked the IP. We're investigating.

Unfortunately the attacks continued since about 14:00 local time. IPv4 connectivity will once again be impacted temporarily while active attacks are ongoing.

We will close this for now as connectivity has been stable for half a day now.

It seems like the attacks have ended or at least suspended since about 3:30 local time. While no attack is running, vulpecula is reachable as usual. We still closely keep an eye on the situation.

Unfortunately, while the temporary measurements - a mitigation by routing traffic through a dedicated DDoS protection provider - have been successful so far; they have also been extremely expensive, in a way, that neither our upstream provider or we can afford to have it running for more hours. We were hoping for the DDoS attack to end anytime soon, but so far that's not the case.

Our upstream provider resorts to blackholing/nullrouting the IPv4 address of vulpecula while the attack is still ongoing, in order to keep the rest of our network stable. This means that vulpecula as of now is only being accessible through IPv6. This affects all services vulpecula is offering: SSH, Webserver, Mailserver.

We are deeply sorry that we can't provide you with better or more optimistic news. We will continue to evaluate the situation and potential strategies and keep you updated.

vulpecula has been singled out onto its own cluster node in order to minimize affections. Adapted filtering rules are in place. Since 15:24 the measurements seem to be working well and connectivity for now is stabilized. Our upstream providers and us are keeping an eye on it.

Besides vulpecula itself, antares, crux and dorado are also indirectly affected as they share one cluster node. We're separating those VMs now.

Unfortunately we start seeing connectivity problems again. We're at it.

We're blocking the DDoS attack on our routers, and we also involved our upstream provider for additional protection outside of our network. For now we see stable IPv4 connectivity again.

DDoS indeed, we're seeing traffic flooding from many IPs to an unused port which we're currently seeking to firewall these packets away.

We're seeing IPv4 packets partially coming through which hardens the suspicion that the host vulpecula.uberspace.de is under a DDoS attack. Other hosts in the network seem unaffected so far.