it seems fair to note that: <http://lists.arin.net/pipermail/arin-issued/>
also doesn't mention this 209.250 range, nor the others from this mystery ASN. (back to 12/2008 at least) -chris On Fri, Jun 8, 2012 at 4:27 PM, Christopher Morrow <[email protected]> wrote: > err, last 3 times I asked this I was shown the error of my ways, but > here goes... > > 209.250.228.241 - seems to not have any records in ARIN's WHOIS > database, everythign seems to roll up to the /8 record :( > > I see this routed as a /23: (from routeviews) > BGP routing table entry for 209.250.228.0/23, version 2072545487 > Paths: (33 available, best #19, table Default-IP-Routing-Table) > Not advertised to any peer > 3277 3267 174 27431 14037 > 194.85.102.33 from 194.85.102.33 (194.85.4.4) > Origin IGP, localpref 100, valid, external > Community: 3277:3267 3277:65321 3277:65323 3277:65330 > > If I look at the ASN in particular: AS14037 > no records exist for that in ARIN's WHOIS database either ;( If I look > at all the networks announced by AS14037: > 14037 | 204.8.216.0/21 | > 14037 | 209.250.224.0/19 | > 14037 | 209.250.228.0/23 | > 14037 | 209.250.242.0/24 | > 14037 | 209.250.247.0/24 | > 14037 | 64.18.128.0/19 | > 14037 | 64.18.159.0/24 | > > > none of them have any records in the ARIN WHOIS database :( The > upstream for this network is AS 27431 - JTL Networks > who seems to get transit/peer with 3356/174. > > It's nice to see folk who use IRR databases to filter their customers > still permit this sort of thing to go on though: AS3356 I'm looking at > you... > > I think first: "Where are the records for this set of ip number resources?" > and second: "Why are we still seeing this on the network with no way > to contact the operators of the resources?" > > -chris
