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 prevent the network from going fully offline during such events.

This is now resolved.

We’re already investigating.