Otava incident
Ashburn (AB1) Router loss of redundancy - 07/30/2026
Otava experienced a notice incident on August 3, 2026 affecting Internet Backbone, lasting 9d 6h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 03, 2026, 04:48 PM UTC
Ashburn (AB1) Router loss of redundancy - 07/30/2026 Start Time: 07/30/2026 - 4:11 PM ET Service Impacting: No, the router failed over to its HA peer, but we are currently operating on a single device. Description: OTAVA® is investigating the cause of this loss of redundancy and has opened a ticket with the hardware vendor. If you have any questions or concerns regarding this maintenance, please contact us by logging into https://support.otava.com or calling 877-740-5028, option 3.
- identified Aug 03, 2026, 08:00 PM UTC
Update: The hardware vendor has identified a hardware failure and is shipping a replacement part.
- identified Aug 03, 2026, 08:21 PM UTC
The hardware vendor has identified a hardware failure and is shipping a replacement part.
- identified Aug 04, 2026, 10:09 PM UTC
Update: Replacement hardware has arrived and OTAVA is working with the datacenter staff to replace the failed component(s).
- identified Aug 05, 2026, 11:33 PM UTC
The failed hardware has been replaced and OTAVA Engineers are working to reapply the configuration and test functionality prior to returning the device to service.
- identified Aug 07, 2026, 07:17 PM UTC
Update: OTAVA engineers have been working to restore the device to service, but have since identified a hardware issue with the replacement device. The hardware vendor has been engaged and is sending another device.
- identified Aug 10, 2026, 03:58 PM UTC
Update: The replacement hardware is expected to arrive this morning.
- identified Aug 10, 2026, 10:11 PM UTC
Update: The replacement has arrived and OTAVA is working with datacenter staff to swap the hardware.
- identified Aug 11, 2026, 05:00 PM UTC
Update: The hardware has been swapped and OTAVA Engineers are now working to apply the configuration and test functionality prior to returning the device to service.
- monitoring Aug 11, 2026, 10:04 PM UTC
Update: The secondary router is now back in production. We will continue to monitor the device for the next 24 hours, at which time we will close this incident.
- resolved Aug 12, 2026, 10:55 PM UTC
This incident has been resolved.