As of this morning, I am seeing BGP from AS 54271
* 62.77.196.0/22 38.101.161.1166991 0 174 3549
3549 3549 12301 8696 20922 54271 i
* 62.77.254.0/23 38.101.161.1166991 0 174 3549
3549 3549 12301 8696 20922 54271 i
* 81.17.184.0/22 38.101.161.116
Patrick W. Gilmore schrieb:
On Jul 13, 2008, at 1:01 PM, Marshall Eubanks wrote:
As of this morning, I am seeing BGP from AS 54271
Maybe someone mistyped 65271? Which is still bad, but not at bad
(IMHO).
Interestingly, AS54271 is the last # of an unassigned block:
46080-47103Assigned
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marshall Eubanks wrote:
As of this morning, I am seeing BGP from AS 54271
* 62.77.196.0/22 38.101.161.1166991 0 174 3549
3549 3549 12301 8696 20922 54271 i
I would be willing to bet that the IP netblocks being advertised
This ip space is from Bahrain 89.148.0.0/19 but some how has ended up in
Hungary from an unknown owner. Definitely looks suspicious in my book.
Manolo
Joel Jaeggli wrote:
those prefixes all have ripe route object with origin AS 20922
all the routes I see for a given prefix look like the
Wouldn't it be better to ask the folks in Hungary (AS20922) who are peering
with this site?
One side, I'd buy the typo. Both sides, mutual typos are a little more
difficult.
Not that conspiracy theories are all that much fun, but I'm finding the
one-sided mistake hard to believe. Either that
interestingly, before july 7th these prefixes were originating from another
private as - 65501, until sometime that day routes were withdrawn from 65501
and began being announced from 54271...
On Sun, Jul 13, 2008 at 4:10 PM, Joel Jaeggli [EMAIL PROTECTED] wrote:
Scott Morris wrote:
6 matches
Mail list logo