RoyaleHosting B.V. had 18 outages in the last 2 years totaling 13h 6m of downtime — averaging 0.7 incidents per month.
There were 18 RoyaleHosting B.V. outages since August 21, 2025 totaling 13h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're experiencing connectivity issues on our AMS cluster
The issue has been resolved.
We're currently experiencing extremely large DDoS attacks, which are causing issues. We're currently working on this
The incident has been resolved, and all services are operating normally. We traced the issue to extremely large-scale DDoS traffic that caused congestion across several upstream paths. Upstream mitigation has been applied, and the affected routes have been stabilized. We understand this disruption was frustrating, and we want to be clear that we’re doing everything we can to prevent a repeat. The network upgrades we announced earlier are being fast-tracked, including doubling our edge capacity and significantly expanding our DDoS mitigation capabilities. Work on these improvements is already underway and being prioritized across the board. We’ll continue to share updates as additional capacity is brought online. Thanks for your patience while we worked through this. If you have any further questions regarding this incident, please feel free to reach out via a ticket. We’re happy to assist.
Digital Realty AMS5-R01B03 - Colocation recovered
We have noticed degraded performance on our AMS VPS Cluster and are currently investigating the root cause. We expect to implement further changes tonight to address the current issues we are experiencing. We will provide updates through this channel as soon as they are available.
We're performing final changes later today for improved network stability and performance
We are experiencing an partal outage on our VPS cluster in Amsterdam, we're investigating the root cause.
We have resolved the issue and are further investigating the root cause.
Between 13:30 and 14:20, our network experienced intermittent, network-wide packet loss caused by large-scale DDoS attacks targeting our infrastructure. During this time, some services may have been partially unreachable or experienced degraded performance. Our team identified the attack patterns and took immediate action to mitigate the impact. Traffic was filtered and rerouted where possible to stabilize network connectivity. At this time, all services are operating normally, and we continue to closely monitor the network. We apologize for any inconvenience this incident may have caused and appreciate your understanding. If you have any questions or continue to experience issues, please contact our support team.
At this time, all services are operating normally, and we continue to closely monitor the network.
We're investigating the network issues in Amsterdam
The issue appears to be fully resolved. Our NOC is taking a deep dive into what exactly happened. It appears to be a firmware-related issue, occurring on multiple routers and multiple sites at the same time. We're investigating this further and will provide a detailed post-mortem response once the core issue has been found and resolved.
We have detected an hardware issue with VPS Node 08 in AMS and are working on resolving the issue
The technician has managed to resolve the issue; this incident has been marked as resolved, and the node is fully operational again. We're running a full hardware check internally and will schedule maintenance for any components needing replacement if necessary. We appriciate your understanding and apologize for the incovienence caused
At 22:52:45 (AMS time), we detected network issues on one of our VPS hypervisors (AMS07), resulting in packet loss for some services. Our team began investigating immediately. The packet loss issue on the affected hypervisor was successfully resolved at 23:02. However, during recovery, this triggered a chain reaction that caused temporary service degradation across the wider AMS cluster. These secondary issues were fully identified and resolved by 23:06:15, at which point all services returned to normal operation. We sincerely apologize for the inconvenience this incident may have caused and appreciate your patience while our team worked to restore stability. If you have any questions, concerns, or believe you are still experiencing issues, please do not hesitate to open a support ticket, and our team will be happy to assist you.
The issue has been resolved
We’ve experienced four exceptionally large attacks that caused packet loss.
Additional measures have now been implemented to better handle this attack.
Due to a misconfiguration we're experiencing packet loss during a large attack
We've fixed the configuration error.
Due to large scale carpet bomb attacks targeting more than 100 subnets we're experiencing issues.
The issue seems to have been solved, we're continuing to monitor the situation.
We received a large DDoS attack which caused network issues.
Full Status Report: At 21:10, our Amsterdam (AMS) site was hit by multiple unusually large 3 Gpps (3 billion pps) DDoS attacks. This temporarily degraded mitigation, affecting customers using the “Always On” protection filter. Between 21:10 and 22:03, we adjusted filtering configurations to reduce load on the filtering servers. At 22:03, we deployed a final change. During a subsequent large attack, an unforeseen configuration issue caused packet filtering to revert to less efficient mechanisms on our edge routers, which became overloaded as a result. At 22:06, we reverted the change and service stabilized. We are increasing upstream capacity in Amsterdam by 2Tbit (expected completion in two weeks) and adding more filtering servers to better handle very high packets-per-second attacks.
Full Status Report: At 21:10, our Amsterdam (AMS) site was hit by multiple unusually large 3 Gpps (3 billion pps) DDoS attacks. This temporarily degraded mitigation, affecting customers using the “Always On” protection filter. Between 21:10 and 22:03, we adjusted filtering configurations to reduce load on the filtering servers. At 22:03, we deployed a final change. During a subsequent large attack, an unforeseen configuration issue caused packet filtering to revert to less efficient mechanisms on our edge routers, which became overloaded as a result. At 22:06, we reverted the change and service stabilized. We are increasing upstream capacity in Amsterdam by 2Tbit (expected completion in two weeks) and adding more filtering servers to better handle very high packets-per-second attacks.
We're experiencing high packet loss in New York due to a DDoS attack, we're working on this.
We've implemented a solution.
AMS09 is experiencing packetloss.
It seems like a connection limit was reached, we've resolved the issue by increasing the limit.
We're aware of degraded network performance due to large DDoS attacks exceeding our DDoS protection of 2.5Tbit/s. We're currently working on this.
We've implemented a solution, we're already in the process of upgrading our protection capacity to prevent this in the future.
Between 18:18 and 18:20 CEST, we detected a partial outage affecting two transit ports on Edge Router 1 (AMS17). Our network automatically rerouted traffic around the affected ports. While this caused a brief reroute for a small portion of traffic, the majority of traffic remained unaffected.