even if customer router crash fault, should have been filtered via prefix list blocking to only allow customer network prefixs to be anounced onwards ? as per best practice colin Sent from my iPhone
On 17 Jul 2015, at 09:55, Matsuzaki Yoshinobu <maz@iij.ad.jp> wrote:
Colin Johnston <colinj@gt86car.org.uk> wrote
any idea why error happened ? what config needs fixing to mitigate mistake? it was easy to see problem via ripe atlas :)
I just got brief explanation from a friend in AS7514.
A router in their network suddenly went out of control, and it seems this somehow generated wrong routing information. They solved the issue by disconnecting the router and are now investigating it. ----- Matsuzaki Yoshinobu <maz@iij.ad.jp> - IIJ/AS2497 INOC-DBA: 2497*629