At 17:54 UTC, our monitoring systems detected a disruption in Path-routed traffic in Chicago. At 17:58 UTC, monitoring showed traffic was traversing as expected.
Our investigation has concluded that the outage was caused by a JunOS bug triggered when additional monitoring filters were applied to the equipment in Chicago. While the same configuration was successfully implemented in London without issues, the equipment in Chicago, running an older firmware version, experienced disruptions. After reviewing the logs and comparing firmware versions, we identified the JunOS bug as the root cause. This issue has been documented and reported to Juniper for further analysis.
We understand the importance of keeping our customers informed about potential disruptions. We aim to minimize unnecessary notifications, especially for routine changes to the routers that are expected to have no impact on customers. Given the frequency of these changes, it is not practical to announce every update. However, we issue alerts for planned changes that are anticipated to cause potential disruptions. Since this configuration had been successfully applied in London without issues, we did not anticipate any problems in Chicago and, therefore, did not send out a notification.
We apologize for any inconvenience caused. If you have any questions or concerns, please contact our client relations team via ticket, and we will be happy to assist you.
