Previous incidents

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.

CosmicGuard is currently in the process of transitioning away from their Dallas data center. Unfortunately, a data center technician prematurely unplugged a patch panel that was not scheduled for disconnection until later tonight, resulting in an outage.

We sincerely apologize for any inconvenience this may have caused.

The Ethernet cable has been replaced, and the server is back online. However, the remote hands connected the cable to the wrong port. We’ll switch it back tomorrow after peak hours.

Please expect maintenance on this node tomorrow around 1 PM EST when our on-site team arrives.

Server is back online, there is a faulty cable that needs to be replaced.

We will replace it on Monday with our on site tech. For now, we will leave it alone but we will keep an eye on it and on stand by in case we need to replace it before then.

• We scheduled internal maintenance from 5:00 AM to 6:00 AM CT to deploy a core mitigation update to our global network.
• As part of our standard process, we apply configuration changes and core updates during off-peak hours on weekdays to minimize risk, and we typically do not expect any customer impact.

Incident Timeline

• 5:00 AM CT: The mitigation update was deployed to AMS as part of a staged rollout. As a result, AMS began sending synchronization pulses to other edge PoPs. T...

Cable is now fixed and server is back online.