Previous incidents

CosmicGuard had a network device issue while deploying a DDoS patch. It was quickly resolved.

Sorry about that.

Server is back online. The connection to it had flopped.

Ashburn, Virginia - CosmicGuard DDoS recovered.

This incident auto recovered, we will post a post incident report regarding this.

Post Mortem Report:

We asked CosmicGuard to add a new /24 IP subnet to our Ashburn location earlier today.

CosmicGuard stopped announcing our prefixes in Ashburn because of a configuration error when adding them to the prefix list.

This misconfiguration caused an outage until the error was corrected.

DAL-5-01 is now back online, we will provide an official report later.

Official Report from Cosmic:

Hi everyone, During an emergency update to our DDoS mitigation systems, an error caused the automated rollback functionality to fail. As a result, the systems entered a continuous boot loop and, due to limited connectivity, were unable to restore the latest version automatically. What would typically be a five-second operation took over 15 minutes as we manually restored the systems.

Although we normally do not perform updates on weekends, a critical bug require...

CosmicGuard Outage & Failover Explanation

According to CosmicGuard’s official outage report, their London PoP experienced downtime due to an unexpected ASIC restart on their Arista core router. They are conducting a root cause analysis, suspecting it may be linked to new capacity planned for next week.

When our DDoS provider goes offline, we always have a fallback ISP in place, ensuring only a brief service disruption—typically no more than 5 seconds. Automated monitoring is in place to d...

We have implemented a patch to correct this.