Cool link, thanks! It's at least 50-60mi, means my DSL must pass through Postfalls,
ID then route back to Seattle, WA. Neotrace (really old 2001 version) did not give me
that unlike when I looked up D's IP.
Big city 45mi away is QWest telco but we're Verizon, I imagine that's coming from our
proximity to the NW Idaho border. Even with same area code as qwest customers we have
to pay long distance since it's a inter-carrier call. Unlike all of NJ/NYC/etc...
being Verizon. I'd rather have Qwest & be on same network as the rest of the area, or
at least have a FiOS option since the local Verizon CO is just 5 blocks away. We so
far up Verizon's ass here it's not funny, my AT&T cell phone has to talk 25mi to a
tower in Idaho while a VZW tower sits 6 blocks away at the local HS!
So weird after living most of my life in NJ where every town is surrounded & bordered
by neighbor towns with population everywhere. Up here it's more spread out thin
population in spoke & hub fashion with the spokes far from the hubs and hubs
sometimes not where they make sense!
Gary VanderMolen wrote:
I don't know how accurate it is, but I was using the IP Locator
at http://www.geobytes.com/IpLocator.htm?GetLocation
Gary VanderMolen, MS-MVP (Mail)
--
From: "maccrawj" <[EMAIL PROTECTED]>
Really? What lookup did you use, I get:
Name: pool-71-161-12-166.sttlwa.dsl-w.verizon.net
IP Address: 71.161.12.166
Location: Seattle (47.611N, 122.333W)
Network: VIS-BLOCK
Gary VanderMolen wrote:
Actually, your IP traces to Post Falls, ID.
