Resolved after 12 hours 28 minutes, affecting Main Site, on October 8, 2024.
At around [13:20 UTC] 6:20 this morning, there was an issue with traffic to/from the router wasn't routing. - Significant increase in router CPU usage leading up to this incident. - Despite sending the router for a reboot, it has not yet returned online. - Router may still be in the process of rebooting, it might still be in the midst of trying to reboot (stuck kernel thread, etc.).
Affected components
Update timeline
- identified Oct 08, 2024, 02:45 PM UTC
We have identified a router issue at the DC causing both sites to be unavailable. We will update once we get more information
- identified Oct 08, 2024, 03:02 PM UTC
At around [13:20 UTC] 6:20 this morning, there was an issue with traffic to/from the router wasn't routing. - Significant increase in router CPU usage leading up to this incident. - Despite sending the router for a reboot, it has not yet returned online. - Router may still be in the process of rebooting, it might still be in the midst of trying to reboot (stuck kernel thread, etc.).
- resolved Oct 09, 2024, 03:14 AM UTC
This incident has been resolved.
Your product runs on more than nwilhelm
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services