I forgot to mention that you can get the RIPE data perspective
on this as well by running a prefix-exact query for "166.84.0.0/16"
at bgp-inspect-RIPE:
http://bgpinspect.merit.edu:9090
If there are enough requests I will probably archive those as well.
thanks
-manish
---------- Forwarded message ----------
Date: Mon, 23 Jan 2006 11:25:58 -0500 (EST)
From: Manish Karir <[EMAIL PROTECTED]>
To: NANOG <nanog@merit.edu>
Subject: Re: oof. panix sidelined by incompetence... again.
in case some people want to look at routeviews data for themselves,
I have archived a couple of pdf file at:
http://bgpinspect.merit.edu/reports.php
-manish
-----
Re: oof. panix sidelined by incompetence... again.
* From: william(at)elan.net
* Date: Sun Jan 22 13:34:47 2006
Can there be a confirmation of this? I see no such MOTD at
http://www.panix.com/panix/help/Announcements/
and my connection to panix is fine and route I see is 166.84.0.0/17
with origin in 2033. I also checked at routeviews.org and similarly
all their peers see origin in in 2033. Is there some other route
that has been hijacked then or has it now ben resolved?
BTW - Its interesting to note that its almost exactly one year after
their domain hijacking which happened on weekend of Jan 15 & 16, 2005 (friday
jan 14th to be more precise).
-------------
