Re: Routing Issues - 173.x.x.x
prisaz
Legend

Anyone know where this is? Still Level 3 See here. http://www.ip-adress.com/ip_tracer/166.90.136.34

Name: Unknown
IP Address: 166.90.136.34
Location: Unknown
Network: LEVEL5-CIDR

My route. Yea this one seems a little slower but????? At least you are not routed to a private PPPOE subnet first. Not that it matters. My public IP is not shown so perhaps that is good.

image

image

0 Likes
Re: Routing Issues - 173.x.x.x
ElizabethS
Moderator Emeritus

On another forum, that IP shows as belonging to Symantec.

0 Likes
Re: Routing Issues - 173.x.x.x
prisaz
Legend

@ElizabethS wrote:

On another forum, that IP shows as belonging to Symantec.


ARIN says Level 3 has that range. The ARIN record has not been updated since 2005? But Symantec could be using that IP. We all know how IP address ranges move arround based on the FiOS expansion and that one range that showed in Canada and took for ever to get updated.

http://whois.arin.net/rest/net/NET-166-90-0-0-1

NetRange166.90.0.0 - 166.90.255.255
CIDR166.90.0.0/16
NameLEVEL5-CIDR
HandleNET-166-90-0-0-1
ParentNET166 (NET-166-0-0-0-0)
Net TypeDirect Allocation
Origin AS
NameserversNS2.LEVEL3.NET
NS1.LEVEL3.NET
OrganizationLevel 3 Communications, Inc. (LVLT)
Registration Date1993-11-17
Last Updated2005-03-02
Comments
RESTful Linkhttp://whois.arin.net/rest/net/NET-166-90-0-0-1
0 Likes
Re: Routing Issues - 173.x.x.x
lasagna
Community Leader
Community Leader

Everyone does recognize that the source of the "location" information for these addresses is a combination of ISP provided topology and WHOIS address information for the address registrations, right?     I routinely have people asking me why their traffic is showing up as being in a different part of the country than where they're located -- and it's simply because the contact address which is registered for the space is associated with a corporate mailing address location and not the location of the city where the address may actually be being used.

Those little maps might look pretty -- but "pretty useless" is what they really are in terms of relevent networking information.

The OP's assertions are simply unfounded.

0 Likes
Re: Routing Issues - 173.x.x.x
prisaz
Legend

@lasagna wrote:

Everyone does recognize that the source of the "location" information for these addresses is a combination of ISP provided topology and WHOIS address information for the address registrations, right?     I routinely have people asking me why their traffic is showing up as being in a different part of the country than where they're located -- and it's simply because the contact address which is registered for the space is associated with a corporate mailing address location and not the location of the city where the address may actually be being used.

Those little maps might look pretty -- but "pretty useless" is what they really are in terms of relevent networking information.

The OP's assertions are simply unfounded.


YEP> I agree 100%. My map didn't show anywhere near Kansas. We're not in Kansas anymore Toto.Smiley Very Happy

The resisterant may have had an address there at some point. I had a straight line to NY.

I have traced a route through the next state which I believe was the next state based on Comsasts routers. But in cyber space what do you want it to say?

Rather neat discussion with pretty picture eh?

0 Likes
Re: Routing Issues - 173.x.x.x
smith6612
Community Leader
Community Leader
Without a name on Hops 14 and 15 I can't say for sure where it is located. Obviously it's routing to New York City but after that, the jump in latency is convincing it's leaving, but it isn't. If It's in New York City, just looks like a really bad route from that point. Visiting the IP address in the final part of the trace brings up SquirrelMail, apparently one of SpeakEasy's servers. Here's a trace route from my DSL line to the final IP address. Not FiOS's issue with that. http://pastebin.com/aZCyhj1a