Previous incidents

We replaced and swap the motherboard for a new one.

CosmicGuard Official Update:

We are addressing a mitigation issue. A temporary fix has been applied, and we are currently testing a comprehensive solution in our lab environment, which will be deployed later tonight.

All servers are now coming back online.

We’re working with our backup, there’ll be a small “lag” once we switch over to our full routes.

For now, we’ll mark as resolved but will provide a better detail report later.

Official CosmicGuard report regarding the degraded performance:

This morning, a bug in the filtering code caused lag spikes and, in some instances, outages in specific locations. The issue was promptly identified and addressed, and throughout the day, we implemented several fixes to prevent it from happening again. These updates will not only resolve the problem but also enhance filtering performance on our end.

CosmicGuard has posted an update located here, we'll update that.

https://status.as30456.net/cm2p2qiwq0076miqcgbpcscuc

The server is now back online, and we apologize for the extended wait time. The motherboard on the previous server was faulty, and we have replaced it with a brand-new one. Compensation will be credited to your accounts shortly.

We’ve identified that the recent issue occurred because the default route was utilizing the session that experienced disruptions, even though the specific routes themselves weren’t affected.

To address this, we’ve added a backup default route within the routing instance. This change ensures that if the primary default route to Cosmic becomes unavailable for any reason, the system will switch to our main ISP for outbound traffic. While this failover may not be completely seamless, it will pre...

CosmicGuard rerouted around the NTT outage to minimize impact for our customers.