BGP Incident:
Summary:Prefix hijacking by AS20115
Start:2015-09-29 00:00:00

Starting discussion on nanog from Seth Mattinen sethm at 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?

Affected ASes
ASHow Affected
32misoriginated someone else's prefix ( and refused to stop announcing it within a number of hours
Affected AS 'Route Views' Connection Map

(note: not all connections may be shown for big graphs)