Time for a new ISP?

*89Laredo*

*89Laredo*

NAXJA Forum User
Location
Sheffield, IA
Our internet sucks..
Tonight I got bored and did a Tracert, Looks like my ISP has alot of problems. What do you guys think?

Windows Vista:

C:\Users\Dylan>tracert naxja.org

Tracing route to naxja.org [66.228.124.214]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 55 ms 55 ms 54 ms h75-100-144-1.snfrmi.dsl.dynamic.tds.net [75.100.144.1]
3 106 ms 81 ms 153 ms chcgildthed01-a6-0-2240033.network.tds.net [69.128.252.157]
4 141 ms 88 ms 75 ms chcgildtcor01.peering.tds.net [206.223.119.64]
5 121 ms 85 ms 103 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223.119.63]
6 152 ms 121 ms 171 ms po3.bbr01.eq01.dal01.networklayer.com [173.192.18.136]
7 127 ms 111 ms 108 ms po4.bbr01.sr01.dal01.networklayer.com [173.192.18.193]
8 137 ms 108 ms 166 ms po4.dar01.sr01.dal01.networklayer.com [173.192.18.179]
9 135 ms 114 ms 110 ms po1.fcr01.dal01.networklayer.com [66.228.118.154]
10 155 ms 165 ms 171 ms 66.228.121.2-static.reverse.softlayer.com [66.228.121.2]
11-30 * * * Request timed out.


Trace complete.
Click to expand...
XP:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Admin>tracert naxja.org

Tracing route to naxja.org [66.228.124.214]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 55 ms 55 ms 54 ms h75-100-144-1.snfrmi.dsl.dynamic.tds.net [75.100.144.1]
3 73 ms 63 ms 86 ms chcgildthed01-a6-0-2240033.network.tds.net [69.128.252.157]
4 158 ms 133 ms 117 ms chcgildtcor01.peering.tds.net [206.223.119.64]
5 153 ms 152 ms 135 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223.119.63]
6 220 ms 209 ms 246 ms po3.bbr01.eq01.dal01.networklayer.com [173.192.18.136]
7 189 ms 176 ms 192 ms po4.bbr01.sr01.dal01.networklayer.com [173.192.18.193]
8 188 ms 226 ms 252 ms po4.dar01.sr01.dal01.networklayer.com [173.192.18.179]
9 186 ms 231 ms 174 ms po1.fcr01.dal01.networklayer.com [66.228.118.154]
10 169 ms 181 ms 154 ms 66.228.121.2-static.reverse.softlayer.com [66.228.121.2]
11-30 * * * Request timed out.


Trace complete.
Click to expand...
 
Looks normal, ping response is a little high.
 
I think thats more than a little, I usually see ping times of ~40ms around here...
Looks like their servers are overloaded. Im only 3 miles from one of their service stations.

It also looks like they send my requests all the way to Chicago (CHCG).
 
TDS is a wasteland, in my opinion. Might just be me though.

At least it isn't AOL or Verizon DSL.

Chicago is a major network crossroads in the midwest (probably due to fiber optics being strung predominantly along powerline corridors, highways, and rail lines), so I am not too surprised that they're sending everything there before it goes outward. It's all about where your ISP actually peers with other providers; in this case it appears to be Chicago. Around here it tends to be Boston or New York City.

Shouldn't depend on your OS - the routing past your router/modem is pretty much out of your hands.
 
TDS was offering 28K dialup in this area as recently as last year- and you were lucky to only have 30% PL. I've been told that the backbone providers have been the main culprits behind the congestion in Chicago, overselling their bandwidth (Savvis was especially bad about this for a long time), but it's hard to get a concrete answer. It's always everyone else's fault, you know.
 
28k dial-up means multiple A-D conversions. 56k analog (really 53k due to FCC power restrictions) requires a single analog to digital conversion. I'm not too surprised this still exists, and where it does, there will be very little impetus to fix the problem any more.

Your pings might be a bit high, mine are running 45-65 ms per hop from here. I've gotten as much as 20mpbs download speeds (like 0330 in the morning on a Wednesday.)
 
kastein said:
TDS is a wasteland, in my opinion. Might just be me though.

At least it isn't AOL or Verizon DSL.

Chicago is a major network crossroads in the midwest (probably due to fiber optics being strung predominantly along powerline corridors, highways, and rail lines), so I am not too surprised that they're sending everything there before it goes outward. It's all about where your ISP actually peers with other providers; in this case it appears to be Chicago. Around here it tends to be Boston or New York City.

Shouldn't depend on your OS - the routing past your router/modem is pretty much out of your hands.
Click to expand...

Yeah, TDS sucks..
Its quite annoying when you click on something and have to wait for it to start loading.. Or it just sits there and times out. I had to do that Tracert twice...

I know its not dependent on OS, but I figured I would post both.
 
Why is that LOL-worthy?

Some of us are actually quite technical. I know Jeff runs some huge datacenter somewhere, and I'm a computer engineer with fairly decent network skills...

So far my favorite internet services have been Verizon FIOS (ignore their DSL) and Charter Cable. Both played stupid "squeeze every last penny out of the customer" tricks by returning the IP for their godaddy ad server instead of a proper NXDOMAIN response when you queried a nonexistent or offline domain, but simply telling my router to use 4.2.2.1 (or 8.8.8.8, or 4.2.2.4, or whatever your favorite DNS server is) instead of my ISP's DHCP-advertised DNS services fixes that problem. TDS, Verizon DSL, and a few others just plain suck, on the other hand.

Next you're gonna tell him to go check WebHostingTalk for info on web hosting :rolleyes:
 
Yeah, I dislike any provider that does that ad BS. If I make a URL input error on my end, I do not wanna see ads. Turds.
 
I had my own for a while but I got too lazy when I shut that server off, never moved the daemon to another. So now I make use of the fine services of 4.2.2.1 for my DNS needs :thumbup:

Anyone else remember the level3 incident on October 20th 2005? Now *that* was an internet failure...
 
My "server" is an older dell with Server 2003 on it, running DNS, FTP, and a "under construction" place holder web page.

Another reason why TDS sucks, they wont let me run a web page unless I get a "business" account. Every outgoing port I have tried doesnt work.

I heard about it, but I dont think I was very affected by it at 14...
 
Wow, that kinda sucks. Verizon consumer DSL/FIOS do the same but only block port 80.

I mostly run FreeBSD - 8.0, 7.2, 6.x, 5.x, and way back, 4.11. Runs on everything except my corporate laptop from work.
 
I dont care about the HTTP.. I just wish they would let me run a FTP page.

Not much of a linux person, Ive tried it and would rather stick with windows.


...Im starting college for computer tech in september, maybe I should do networking. lol
 
Defiance665 said:
My "server" is an older dell with Server 2003 on it, running DNS, FTP, and a "under construction" place holder web page.

Another reason why TDS sucks, they wont let me run a web page unless I get a "business" account. Every outgoing port I have tried doesnt work.

I heard about it, but I dont think I was very affected by it at 14...
Click to expand...
I'm mildly surprised that more ISP's don't NAT segregate segments of their networks. Does 2 things, makes much more efficient use of their address blocks, and pretty much will eliminate servers like HTTP and FTP (won't do a thing for existing connections, though.)

Ken, I wouldn't say I run a huge data center.... but it does run a $12b/year business across 5 time zones.
 
Personally, I refuse to expose a windows machine directly to the 'net if I can help it. Not always avoidable, though.
 
You must log in or register to reply here.

Similar threads

5-90
  • Locked
Slow going...
Replies
1
Views
582
ChiXJeff
C
Back
Top