AlphaVPS incident

Network DDoS

AlphaVPS is currently experiencing a major incident affecting Network Infrastructure in Sofia and Network Infrastructure in Nuremberg and 1 more component, which began 9h ago. The vendor's full update timeline is below.

Started
Jun 29, 2026, 06:42 PM UTC
Resolved
Ongoing
Duration
● 9h 6m
Detected by Pingoru
Jun 29, 2026, 06:42 PM UTC

Affected components

Network Infrastructure in SofiaNetwork Infrastructure in NurembergNetwork Infrastructure in New York

Update timeline

  1. identified Jun 29, 2026, 06:42 PM UTC

    We are currently experiencing a large-scale DDoS attack targeting portions of our network infrastructure. This attack is causing intermittent connectivity issues and increased latency for some customers. Our network engineering team is actively working to deploy additional permanent mitigation measures to fully address this attack and further strengthen the resilience of our infrastructure. Temporary mitigation is already in place, and we continue to monitor and adapt our defenses as the attack evolves. We sincerely apologize for any disruption this may cause and appreciate your patience while we work toward a complete and permanent resolution. Further updates will be provided as progress is made.

  2. identified Jun 29, 2026, 07:39 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Jun 29, 2026, 08:01 PM UTC

    We've applied mitigation in Nuremberg. Sofia is pending and should be applied shortly. As we're dealing with an extortion/ransom DDoS attacks, we're unable to share more details publically.

  4. identified Jun 29, 2026, 09:22 PM UTC

    While the malicious attackers are constantly changing the attack patterns, we're applying mitigation and the majority of our customers are back online. We're engaging local law enforcement in the situation as well. Further information to follow.

  5. monitoring Jun 30, 2026, 12:52 AM UTC

    We've implemented mitigation across all of our locations and traffic has returned to normal. There might be variances in ICMP, but we trust that the issue is getting resolved in full.