|Summary:||Prefix hijacking by AS20115|
Starting discussion on nanog from Seth Mattinen sethm at rollernet.us: I've got a problem where AS20115 continues to announce prefixes after BGP neighbors were shutdown. They claim it's a wedged BGP process but aren't in any hurry to fix it outside of a maintenance window. I'm at a loss of what else I can do. They admit the problem but won't take action saying it needs to wait for a maintenance window. Am I out of line insisting that's an unacceptable response to a problem that results in prefix/traffic hijacking?
|32||misoriginated someone else's prefix (184.108.40.206/24) and refused to stop announcing it within a number of hours|
(note: not all connections may be shown for big graphs)