BGP Incident:
Summary: | Prefix hijacking by AS20115 |
---|---|
Start: | 2015-09-29 00:00:00 |
End: | Unknown |
Details: | 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? |
Affected ASes
AS | How Affected |
---|---|
32 | misoriginated someone else's prefix (104.73.161.0/24) and refused to stop announcing it within a number of hours |
References
Summary | Link |
---|---|
Nanog thread | http://www.gossamer-threads.com/lists/nanog/users/184040 |
Affected AS 'Route Views' Connection Map
(note: not all connections may be shown for big graphs)