http://webtrace.info/asn?q=1234&submit=asn
2009/9/25 Ronan Mullally <ro...@iol.ie> > Hi Andy, > > On Fri, 25 Sep 2009, Andy Saykao wrote: > > > This is why I needed to know what IP blocks belong to AS1234, so I could > > find out how much traffic was actually coming from AS1234 on our > > Internet link. > > Some (possibly all?) Whois servers can provide you with this information > with: > > whois -h whois.ripe.net -i origin AS1234 > > % Information related to '194.110.40.0/23AS1234' > > route: 194.110.40.0/23 > descr: Imatran Voima Corporation > descr: EUnet-FI aggregate > origin: AS1234 > mnt-by: AS790-MNT > source: RIPE # Filtered > > % Information related to '194.110.44.0/23AS1234' > > route: 194.110.44.0/23 > descr: Carelcomp Power > descr: EUnet-FI aggregate > origin: AS1234 > mnt-by: AS790-MNT > source: RIPE # Filtered > > % Information related to '193.110.32.0/21AS1234' > > route: 193.110.32.0/21 > descr: Fortum > origin: AS1234 > mnt-by: TE-ENERGY-NOC > source: RIPE # Filtered > > (an inverse query looking for objects with an origin of AS1234). > > I don't know how definitive it is - I've queried several large AS and got > nothing back. It may be this functionality is only available in the RIPE > whois server. There's also no guarantee the results are going to be > current or accurate. > > > -Ronan > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- With best regards, Andrey 'sshd' Petrenko xmmp: sshd at jabber.org gtalk: andy.petrenko at gmail.com skype: andy.petrenko web: http://sshd.by _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/