AS 54271

2008-07-13 Thread Marshall Eubanks
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

Re: AS 54271

2008-07-13 Thread Fredy Kuenzler
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

Re: AS 54271

2008-07-13 Thread Jon Kibler
-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

Re: AS 54271

2008-07-13 Thread manolo
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

RE: AS 54271

2008-07-13 Thread Scott Morris
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

Re: AS 54271

2008-07-13 Thread Christian Koch
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: