On Sunday, September 13th, 2015 during the wee hours of the morning a change was made by AS7122 which silenced four Manitoban ASNs, and removed several other routes from the global routing table. Shortly after the start of their 1AM maintenance window AS7122 enabled BGP atomic aggregate on 220.127.116.11/16 and 18.104.22.168/16, causing AS21876, AS23001, AS32433, and AS54937 to disappear from the global routing table.
Below is an animation of the withdrawal of AS54937’s 22.214.171.124/24 route as observed from RIPE’s route collectors.
Coincidentally, all four of these ASNs were single homed to 7122 and advertising /24 more specific routes of 7122’s /16 advertisements.
Doing some deeper digging on an MTS customer’s looking glass, I see that these routes are only suppressed to external peering peers.
I wonder if it was intentional to suppress the above ASNs and routes? If it was intentional, was it an altruistic move to keep the global routing table size down?
I wonder what their reasoning was? Perhaps they only intended to summarize internal routes and clobbered customer routes accidentally in the process?
Do they have a plan to un-hide routes should these ASNs choose to become multihomed (again) at some point? Having only one upstream sending the specific route advertised will result in making it near impossible to utilize more than one connection effectively for inbound.