Level3 and more

[wilderness]

There's an interesting thread ISP has outage going on here [paceadvantage.com]

8.8.8.8 & 8.8.4.4 (Level3/Google)

Today I had a valid google search referal from a Homeland Security IP.
Mixed in with the HS IP's were some requests from Level3, one of which was for a directory name without a trailing slash (which this website does not have, as well as a successive request for the valid (with slash) directory.

8.28.16.254 - - [17/Aug/2011:07:46:05 -0600] "GET MyFolder HTTP/1.1" 301 565 "-" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 1.1.4322; MS-RTC LM 8; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)"

FWIW the Homeland Security IP used a different UA (below) than the Level3 IP.

"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 1.1.4322)"

I denied the Level3 to the Class C.
Were this my own website (s), I'd also deny the HS range.

Unable to recall seeing anything good come from the Level3 ranges.

[dstiles]

I've got some of level3 blocked but thanks to the very sloppy IP-block registration requirements it's very difficult to determine what parts of it are "broadband" and which "servers", and level3's method is even less helpful.

Now added 8.28.16/23 to the blocked ranges. Thanks.

What was the homeland IP? I've seen a few of them recently.

Any idea what's coming from the two google ranges? Something unpleasant? Although it LOOKS as if it's just DNS...

Blocked anyway. I also have a yahoo range at 8.12.144/24

[wilderness]

Thanks for the Yahoo.

Homeland; 216.81.80.0 - 216.81.95.255, specifically 216.81.94.68

I noted this Level3 because there was a recent other thread were 3 was discussed.
After the thread ended I looked at my saved references to 3 and found that since I was unable to determine the sub-nets of 4.0 that I had taken to doing tracerts on 4.0 ranges to establish localities, which I had forgotten.
I've perhaps a couple of dozen cities. The problem with the tracerts is the absence of ranges, rather than a distinct Class D.

This tracert on a Phoenix, AZ from 2008, course all the early lines are simply relay centers.
ae-61-61.ebr1.Washington1.Level3.net [4.69.134.129]
ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
ae-63-63.csw1.Dallas1.Level3.net [4.69.136.154]
ae-61-61.ebr1.Dallas1.Level3.net [4.69.136.121]
ae-8-8.car1.Phoenix1.Level3.net [4.69.133.29]

Tracerts provide some interesting insights into relay centers and the hoops that providers jump through to balance server loads.

[dstiles]

Hmm. Although I noticed it, Homeland didn't get listed so it didn't (to me) look bad. I'll keep an eye open. Thanks.

Level3 - interesting but sadly doesn't help me. :(

[Pfui]

Speaking of Level 3, see also "Level 3 redux" (re: 8.18.46. ) [webmasterworld.com...]