(Resolved) 2017-04-06 15:40 UTC: BGP reachability alerts

Last updated: Sat Apr 22 00:14:22 GMT 2017

2017-04-07 08:30 UTC Update: San Jose, CA-4, San Jose, CA-5 and Washington, DC-6 BGP Monitors have been removed from our BGP data collection. This will prevent further alerts from any customer tests that had those monitors assigned to a test. New Routing/BGP tests or tests with the BGP Visualization view will not be able to select these Monitors until they are restored.

2017-04-06 22:30 UTC Update: We have begun disabling the San Jose, CA-4, San Jose, CA-5 and Washington, DC-6 BGP Monitors from our BGP data collection.  This will prevent further alerts from any customer tests that had those monitors assigned to a test.

Please be advised that you may have received alert notifications for BGP alerts triggered based on lack of reachability to your monitored prefixes by the following public BGP monitors:

San Jose, CA-4 (205.171.3.22)
San Jose, CA-5 (74.40.7.35)
Washington, DC-6 (205.171.202.202)

Each of these monitors peers with the route-views3 route collector, which has shown a steady decline in number of prefixes over the past 24 hours.  In most cases, the updates published by the Route Views project do not show withdrawals for these prefixes - the prefixes are missing from the dumps.

If you'd like to analyze the BGP dumps yourself, check out this article.

If you'd like clarification on the issue, please feel free to contact our Customer Success team - otherwise, we'll publish updates to this article as we have more information.