North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

odd hijack

  • From: Josh Karlin
  • Date: Thu Nov 09 19:53:05 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=faY5N8OzTc7KjubxL4DRlx07BSuE86ad8JVBhkw2Mt4nfIRTuECzwZdWZXE+nmWXb0itSz6N8ofTzWH5rgNJYMUP0rigRux//kD7KEWNXHbn7V/LDWyO9ui92H76TeSQR4+5SdA+WySHYJLWGvwGoXF22cj8XUp7nXxr26DokwQ=

I recently brought up a prefix hijack that the NANOG community solved,
the AS had accidentally started announcing their bogon list.

Here is one that is somewhat the opposite, the AS announced a
significant portion of IANA allocated space.  Note, they are large
blocks and as such probably did not cause much damage because most
networks announce more specifics.  My question to the community is,
what kind of misconfiguration could cause this set of prefixes to be
announced?   I asked the AS responsible, but have not had a response.

If you would like more information on the hijack, please see the
Internet Alert Registry forums at

Following are the AS's announced prefixes during the ~10 minute hijack
from earlier today: