Resolved
on May 17, 2026 —
Sunday May 17, 13:48
We have determined that the issue was caused by a kernel panic on one of our routers. As a result, the router rebooted, and it took several minutes for traffic to switch over to the secondary router. This behavior is expected in this type of incident.
We will be performing emergency maintenance on our routers this afternoon. During this maintenance, the kernel will be upgraded and each router will be restarted. You should experience little to no disruption, as our routers are configured redundantly and traffic will normally fail over smoothly and automatically to the remaining device.
We will now close this incident and shortly open a new maintenance notification regarding the planned work on our routers.