Frustrated gamer... advise needed

Funky_K · Post by **Funky_K** » Thu Sep 27, 2001 2:47 pm

I have had a 1.5MB/128kb cable connection (@Home) for the last 2+ years. I do alot of online gaming, and typically have pings between 100-150. 2 weeks ago, my pings drastically worsenned. Ever since then, I haven't been able to get a ping under 600 on servers that I typically get <150 to.

My first thought was that there was a problem with my connection. I spoke with a technical agent at AT&T, and ran through several diagnostic tests to check my connection. We could not find a problem. I can still upload at speeds of 16k/s, and I can still dowload at up to 300k/s, just as always.

Next, I thought maybe I had accidentally messed up some internet registry setting, or an obscure setting in the game that I play (Quake2). So, I reformatted my harddrive, reinstalled Windows, and put a fresh install of Quake2 on. This did not change anything.

Something has obviously changed, but I can't figure out the problem. Could there be something the @Home tech overlooked? Could there be a problem with my cable modem, nic card, motherboard???

My next thought was to replace the cable modem and nic cable to see if that fixed the problem, but I couldn't convince AT&T to switch out my modem... and I can't afford to buy one, especially if it doesn't fix the problem.

Any suggestions or comments would be greatly appreciated. This is my first post here, but I don't know where else to turn.

Thanks.

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 2:58 pm

Welcome to SpeedGuide!

High latency could be attributed to several factors. You might as well start from your end. Have you checked your house wiring? Have you added any coax splitters and/or TV sets to your cable feed?

Funky_K · Post by **Funky_K** » Thu Sep 27, 2001 3:30 pm

Thanks MosDef112.

I haven't made any changes to my home wiring setup. Unless something just "went bad", it should all be just like it was before the problem.

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 3:40 pm

Okay.. Try tracing these sites, copy and paste the result files in here:

C:\WINDOWS\TRACERT OMARNYC.COM > c:\trace1.txt
C:\WINDOWS\TRACERT PCMAGLABS.COM > c:\trace2.txt

Funky_K · Post by **Funky_K** » Thu Sep 27, 2001 3:53 pm

Sorry... could you specify how to run those traces??

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 4:00 pm

If you have Windows 95, 98, or ME, type

C:\WINDOWS\TRACERT OMARNYC.COM > c:\trace1.txt
C:\WINDOWS\TRACERT PCMAGLABS.COM > c:\trace2.txt

If you have Windows 2000, or XP type

C:\WINNT\TRACERT OMARNYC.COM > c:\trace1.txt
C:\WINNT\TRACERT PCMAGLABS.COM > c:\trace2.txt

Copy and paste those two files in here. Change the IP address on the first hop to some other phony number, you don't want others to know what it is.

Funky_K · Post by **Funky_K** » Thu Sep 27, 2001 4:05 pm

Nevermind... I figured it out:

Tracing route to omarnyc.com [24.185.59.218]

over a maximum of 30 hops:

1 27 ms 14 ms 28 ms changed
2 13 ms 28 ms 27 ms r1-fe1-0.belvil1.il.home.net [24.14.191.161]
3 13 ms 28 ms 27 ms 10.83.192.25
4 13 ms 42 ms 27 ms c1-se6-0-8.kscymo1.home.net [24.7.74.9]
5 28 ms 27 ms 28 ms c1-pos4-0.omahne1.home.net [24.7.64.145]
6 27 ms 55 ms 42 ms c1-pos1-0.desmia1.home.net [24.7.64.138]
7 41 ms 42 ms 41 ms c2-pos1-0.chcgil1.home.net [24.7.64.166]
8 42 ms 55 ms 41 ms 24.7.70.106
9 41 ms 41 ms 41 ms ord2-core2-pos7-0.atlas.icix.net [165.117.48.86]
10 68 ms 55 ms 69 ms jfk3-core2-pos5-0.atlas.icix.net [165.117.48.37]
11 69 ms 82 ms 69 ms jfk3-core4-pos6-0.atlas.icix.net [165.117.48.166]
12 55 ms 69 ms 68 ms r2-pos9-0-622M.in.hcvlny.cv.net [198.180.44.234]
13 55 ms 68 ms 55 ms r2-srp10-0.cr.hcvlny.cv.net [167.206.12.4]
14 69 ms 55 ms 68 ms r4-srp-5-0.cr.hcvlny.cv.net [167.206.12.20]
15 69 ms 69 ms 55 ms r2-srp5-0.dr.hcvlny.cv.net [167.206.12.82]
16 96 ms 69 ms 69 ms ubr104.cmts.nycxny.cv.net [167.206.251.181]
17 68 ms 69 ms 69 ms ool-18b93bda.dyn.optonline.net [24.185.59.218]

Trace complete.

Tracing route to pcmaglabs.com [64.0.229.170]

over a maximum of 30 hops:

1 27 ms 14 ms 27 ms changed
2 14 ms 27 ms 14 ms r1-fe1-0.belvil1.il.home.net [24.14.191.161]
3 14 ms 27 ms 28 ms 10.83.192.25
4 27 ms 28 ms 41 ms c1-se6-0-5.kscymo1.home.net [24.7.73.173]
5 41 ms 28 ms 27 ms c1-pos2-0.tulsok1.home.net [24.7.64.154]
6 82 ms 41 ms 110 ms c1-pos1-0.dllstx1.home.net [24.7.64.162]
7 42 ms 41 ms 41 ms 64.3.0.133
8 28 ms 41 ms 41 ms ge9-0.tran1.dal-tx.us.xo.net [64.220.0.145]
9 41 ms 41 ms 27 ms ge10-0.tran2.dal-tx.us.xo.net [64.220.0.146]
10 69 ms 68 ms 69 ms p0-0.tran2.was-dc.us.xo.net [64.0.0.38]
11 69 ms 68 ms 69 ms ge9-0.tran1.was-dc.us.xo.net [64.220.0.209]
12 69 ms 82 ms 69 ms p1-0.tran1.nyc-ny.us.xo.net [64.0.0.42]
13 110 ms 82 ms 69 ms ge10-0.tran2.nyc-ny.us.xo.net [64.220.0.242]
14 69 ms 68 ms 69 ms p1-0.dist2.hud-ny.us.xo.net [64.0.0.66]
15 69 ms 82 ms 69 ms ge12-0-0.access1.hud-ny.us.xo.net [64.220.3.86]
16 82 ms 83 ms 110 ms rb-209-220-116-42.hud-ny.us.xo.net [209.220.116.42]
17 82 ms 96 ms 96 ms w155.z209220187.nyc-ny.dsl.cnc.net [209.220.187.155]
18 96 ms 96 ms 83 ms w170.z064000229.nyc-ny.dsl.cnc.net [64.0.229.170]

Trace complete.

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 4:32 pm

Interesting.. Part of your problem might be your routing. Your @Home ISP did some real funny routing with these two sites I had you trace. For example:

Tracing route to pcmaglabs.com [64.0.229.170]

over a maximum of 30 hops:

1 27 ms 14 ms 27 ms changed

2 14 ms 27 ms 14 ms r1-fe1-0.belvil1.il.home.net [24.14.191.161]

3 14 ms 27 ms 28 ms 10.83.192.25

4 27 ms 28 ms 41 ms c1-se6-0-5.kscymo1.home.net [24.7.73.173]

5 41 ms 28 ms 27 ms c1-pos2-0.tulsok1.home.net [24.7.64.154]

6 82 ms 41 ms 110 ms c1-pos1-0.dllstx1.home.net [24.7.64.162]

7 42 ms 41 ms 41 ms 64.3.0.133

8 28 ms 41 ms 41 ms ge9-0.tran1.dal-tx.us.xo.net [64.220.0.145]

9 41 ms 41 ms 27 ms ge10-0.tran2.dal-tx.us.xo.net [64.220.0.146]

Your trace went from Illinios, which is where I assume you live, down to Kansas City, then to Oklahoma, then to Dallas, TX, then it hit the network in which PCMAGLABS.COM resides, with XO Communications, then XO routed your packet all the way to NYC where that server resides. Yet, on the other trace:

Tracing route to omarnyc.com [24.185.59.218]

over a maximum of 30 hops:

1 27 ms 14 ms 28 ms changed

2 13 ms 28 ms 27 ms r1-fe1-0.belvil1.il.home.net [24.14.191.161]

3 13 ms 28 ms 27 ms 10.83.192.25

4 13 ms 42 ms 27 ms c1-se6-0-8.kscymo1.home.net [24.7.74.9]

5 28 ms 27 ms 28 ms c1-pos4-0.omahne1.home.net [24.7.64.145]

6 27 ms 55 ms 42 ms c1-pos1-0.desmia1.home.net [24.7.64.138]

7 41 ms 42 ms 41 ms c2-pos1-0.chcgil1.home.net [24.7.64.166]

8 42 ms 55 ms 41 ms 24.7.70.106

9 41 ms 41 ms 41 ms ord2-core2-pos7-0.atlas.icix.net [165.117.48.86]

10 68 ms 55 ms 69 ms jfk3-core2-pos5-0.atlas.icix.net [165.117.48.37]

11 69 ms 82 ms 69 ms jfk3-core4-pos6-0.atlas.icix.net [165.117.48.166]

12 55 ms 69 ms 68 ms r2-pos9-0-622M.in.hcvlny.cv.net [198.180.44.234]

13 55 ms 68 ms 55 ms r2-srp10-0.cr.hcvlny.cv.net [167.206.12.4]

Your packet went from Chicago, and directly onto Business Internet Inc.'s network, allegedly in Florida from doing a WHOIS search. I'm wondering why your network would need to route your line that way, especially when both hosts reside in New York City. Better yet, try tracing these other hosts: 64.81.221.182, and 64.192.208.182.

Funky_K · Post by **Funky_K** » Thu Sep 27, 2001 4:36 pm

thanks for the help MosDef112:

Tracing route to dsl081-221-182.nyc2.dsl.speakeasy.net [64.81.221.182]

over a maximum of 30 hops:

1 27 ms 28 ms 13 ms changed
2 14 ms 27 ms 14 ms r1-fe1-0.belvil1.il.home.net [24.14.191.161]
3 27 ms 28 ms 27 ms 10.83.192.25
4 28 ms 41 ms 27 ms c1-se6-0-8.kscymo1.home.net [24.7.74.9]
5 27 ms 41 ms 28 ms c1-pos2-0.tulsok1.home.net [24.7.64.154]
6 27 ms 41 ms 42 ms c1-pos1-0.dllstx1.home.net [24.7.64.162]
7 42 ms 41 ms 41 ms 24.7.70.214
8 28 ms 41 ms 41 ms 138.at-5-0-0.XR1.DFW9.ALTER.NET [152.63.100.218]
9 110 ms 27 ms 41 ms 0.so-3-0-0.TR1.DFW9.ALTER.NET [152.63.10.13]
10 69 ms 110 ms 82 ms 128.at-5-1-0.TR1.NYC8.ALTER.NET [152.63.3.213]
11 69 ms 69 ms 82 ms 185.at-2-0-0.XR1.BOS4.ALTER.NET [152.63.19.65]
12 110 ms 82 ms 82 ms 179.ATM6-0.GW5.BOS4.ALTER.NET [152.63.25.57]
13 68 ms 69 ms 82 ms internap-gw.customer.alter.net [65.194.79.74]
14 69 ms 82 ms 82 ms border4.ge3-0-bbnet2.bsn.pnap.net [63.251.128.73]
15 83 ms 123 ms 83 ms spk-1-bos.dsl-isp.net [63.251.141.193]
16 96 ms 82 ms 97 ms dsl081-204-151.nyc2.dsl.speakeasy.net [64.81.204.151]
17 83 ms 96 ms 82 ms dsl081-221-182.nyc2.dsl.speakeasy.net [64.81.221.182]

Trace complete.

Tracing route to dsl-64-192-208-182.telocity.com [64.192.208.182]

over a maximum of 30 hops:

1 27 ms 55 ms 28 ms changed
2 14 ms 27 ms 28 ms r1-fe1-0.belvil1.il.home.net [24.14.191.161]
3 14 ms 27 ms 28 ms 10.83.192.25
4 27 ms 28 ms 27 ms c1-se6-0-5.kscymo1.home.net [24.7.73.173]
5 28 ms 27 ms 69 ms c1-pos2-0.tulsok1.home.net [24.7.64.154]
6 41 ms 83 ms 68 ms c1-pos1-0.dllstx1.home.net [24.7.64.162]
7 82 ms 28 ms 41 ms pos1-2.core2.Dallas1.Level3.net [209.245.240.189]
8 41 ms 69 ms 82 ms gigabitethernet6-0.ipcolo2.Dallas1.Level3.net [209.244.15.26]
9 28 ms 41 ms 41 ms 100m-core2.dfw.tlct.net [63.209.48.74]
10 82 ms 83 ms 68 ms pos8-1-hfr1.atl.tlct.net [216.227.126.21]
11 69 ms 82 ms 69 ms ge-v5-hfr2.atl.tlct.net [216.227.126.58]
12 69 ms 137 ms 83 ms so-1-0-0-core2.was.tlct.net [216.227.126.13]
13 109 ms 83 ms 82 ms 100m-core1.phl.tlct.net [63.208.96.26]
14 68 ms 96 ms 69 ms 100m-core2.phl.tlct.net [63.208.100.30]
15 83 ms 82 ms 83 ms 100m-core1.nyc.tlct.net [63.209.170.98]
16 82 ms 83 ms 82 ms 64.34.48.82
17 110 ms 110 ms 96 ms dsl-64-192-208-182.telocity.com [64.192.208.182]

Trace complete.

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 4:47 pm

You're welcome.

Yep, your routing may be part of your problem. Both of the last two hosts that I had you run a trace for traced all the way down to Dallas, TX, then back up the ISP's networks for those two hosts. Both hosts are here in New York City, one from Speakeasy.net, and the other from Telocity. I expected you to report more hops for the Telocity host, but I guess Telocity's network isn't doing so bad today. LOL. My only suggestion would be to contact @Home and explain this to them, hopefully they can look into it for you. Do you know the IP addresses of the game servers you're trying to log into? Maybe the problem is on their end.

Post by **YeOldeStonecat** » Thu Sep 27, 2001 6:22 pm

What's more important in his case is running a tracert to the game servers that he plays on.

@home changed backbones mid summer....many many MANY of the regular players on our gaming servers who use @home can no longer play on our servers....they all lag out at 999 even the guy I co-run our servers with, he cannot play on his own server, cannot even PcAnywhere in without getting disconnected. I forget which routers, but something to do with sprintnet....their tracerts are great up til that router.

OK, I just ran a ton of tracert's to my buddy, hoping to ID the router that spring was using in New York that was hammered. But I see their routing is going to Chicago now...and all the pings are flat. Starting today. Hmmm......

I know so many peeps called and complained...wonder if they finally found the problem.

Anyways, run tracerts to your game server and see where the lag spikes.

funky · Post by **funky** » Thu Sep 27, 2001 7:45 pm

The Worm might be still lurking around, people!

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 8:34 pm

*** To YeOldeStonecat ***

Yeah.. Even so, his routing does seem a bit whacked out, so overall performance will be shady unless his routing is fixed.

Funky_K · Post by **Funky_K** » Thu Sep 27, 2001 9:24 pm

I talked with AT&T... here is the chat log:

Michael S has joined this session!
Michael S says, Good Evening! Thank you for contacting AT&T@home Customer Support! How may I assist you today?
You say, i was wondering about my routing
Michael S says, I apologize that I do not completely understand what you are asking. Please help me understand so we can work together to put things back in order. Is this Jeff?
You say, i think there was a change 2 weeks ago, that has caused my online latencies to dramatically increase
You say, yes... this is jeff
You say, i've been running trace routes to check my hops
You say, and they seem to be going all over the place
You say, out of the way
Michael S says, Please allow me a few moments to research your account.
You say, im in the midwest... trace route to new york goes through dallas... that is way out of the way
You say, my latencies are 4X higher than they have always been... until 2 weeks ago
You say, i've chatted with tech reps already... and my upload and download bandwidth seems to be ok
You say, there must be a problem with my routing... did this change a couple weeks ago??
Michael S says, It may have been changed, your internet connection may be routed differently at any time.
Michael S says, As long as your speeds seem okay, I do not see any need for concern.
You say, this was a big change then.... because i always (for 2 years) got pings
of <150... now i can't get <600
You say, it is a big concern because i cannot do online gaming with those latencies
Michael S says, can you ping "changed" and give me the idea of the results, please?
You say, the main reason i am paying for cable is for online gaming... 1 sec on the ping
You say, request timed out... i can't even ping my modem???
Michael S says, What do you gsay, avg 27ms
Michael S says, One moment please.
You say, why can't i ping the modem???
Michael S says, I'm not sure why you can't ping the modem.
You say, maybe you should switch out my modem... to see if that corrects the problem... it is over 2 years old
Michael S says, I do apologize for any inconveniences, however I am not showing any speed issue in your connection.
You say, ... and is it normal for the routing to be that far off
Michael S says, If you wish to purchase a modem for use on the @Home network, you may do so. You are in an area which allows this and this will save you $10 per month on your monthly rate.
You say, can you switch out my modem... to see if that is the problem???
Michael S says, The routing is sent through in the best and fastest way for it to be routed at that time.
Michael S says, No, we can not do this as there does not appear to be an issue with your connection.
You say, michael... there is an issue with my connection... i never had this problem before
Michael S says, I apologize if you are experiencing slower speeds in gaming, however, gaming is not something that AT&T@home can support.
You say, at&t sucks... i'll be switching to DSL
The session ha

Here is a traceroute to a server I often playED on:

Tracing route to chaos.dynastynet.net [209.213.76.242]

over a maximum of 30 hops:

1 14 ms 55 ms 54 ms changed
2 27 ms 41 ms 42 ms r1-fe1-0.belvil1.il.home.net [24.14.191.161]
3 69 ms 27 ms 41 ms 10.83.192.25
4 28 ms 41 ms 41 ms c1-se6-0-8.kscymo1.home.net [24.7.74.9]
5 41 ms 55 ms 68 ms c1-pos2-0.tulsok1.home.net [24.7.64.154]
6 41 ms 41 ms 41 ms c1-pos1-0.dllstx1.home.net [24.7.64.162]
7 55 ms 68 ms 42 ms home-gw.dlstx.ip.att.net [192.205.32.241]
8 41 ms 82 ms 42 ms gbr4-p50.dlstx.ip.att.net [12.123.16.246]
9 54 ms 42 ms 55 ms gbr2-p30.kszmo.ip.att.net [12.122.2.114]
10 54 ms 55 ms 83 ms gbr1-p60.kszmo.ip.att.net [12.122.1.93]
11 55 ms 55 ms 55 ms gbr4-p40.sl9mo.ip.att.net [12.122.2.42]
12 69 ms 68 ms 83 ms gbr3-p40.cgcil.ip.att.net [12.122.2.205]
13 55 ms 55 ms 55 ms gbr4-p60.cgcil.ip.att.net [12.122.1.126]
14 96 ms 124 ms 96 ms gbr4-p40.cb1ma.ip.att.net [12.122.2.186]
15 82 ms 82 ms 69 ms gbr1-p100.cb1ma.ip.att.net [12.122.5.58]
16 69 ms 82 ms 82 ms ar1-p310.prvri.ip.att.net [12.123.202.33]
17 * 82 ms 69 ms 12.124.0.70
18 97 ms 109 ms 83 ms hssi-03-1-ip-cascade1.prv.ri.meganet.net [216.237.96.254]
19 110 ms 83 ms 68 ms cascade1.bos.ma.meganet.net [209.213.64.233]
20 110 ms 110 ms 83 ms ip16.bepeterson.com [209.213.76.241]
21 96 ms 83 ms 96 ms chaos.dynastynet.net [209.213.76.242]

Trace complete.

I really appreciate the responses... Thanks.

Post by **YeOldeStonecat** » Thu Sep 27, 2001 10:09 pm

Just for yucks for MosDef...

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 21 ms 19 ms 19 ms gateway.113.sn.ct.dsl.thebiz.net [216.238.113.1]

3 21 ms 22 ms 23 ms neca2.cyberzone.net [209.150.0.11]
4 22 ms 22 ms 23 ms sl-gw4-spr-4-0-ts1.sprintlink.net [160.81.249.9]

5 20 ms 22 ms 23 ms sl-bb11-spr-0-0.sprintlink.net [144.232.21.50]
6 27 ms 28 ms 26 ms sl-bb21-pen-10-3.sprintlink.net [144.232.8.161]

7 27 ms 27 ms 25 ms sl-bb22-pen-15-0.sprintlink.net [144.232.16.30]

8 30 ms 29 ms 30 ms sl-bb23-nyc-15-0.sprintlink.net [144.232.9.17]
9 29 ms 30 ms 30 ms sl-gw27-nyc-14-0.sprintlink.net [144.232.7.22]
10 29 ms 29 ms 32 ms sl-cable1-1-0.sprintlink.net [144.223.37.234]
11 30 ms 29 ms 29 ms r2-srp10-0.cr.hcvlny.cv.net [167.206.12.4]
12 28 ms 30 ms 30 ms r4-srp-1-0.cr.hcvlny.cv.net [167.206.12.68]
13 30 ms 29 ms 30 ms r2-srp5-0.dr.hcvlny.cv.net [167.206.12.82]
14 31 ms 30 ms 30 ms ubr104.cmts.nycxny.cv.net [167.206.251.181]
15 41 ms 40 ms 40 ms omarnyc.com [24.185.59.218]

Trace complete.

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 11:00 pm

*** To Funky_K ***

Yeah.. I was afraid they were going to blow you off that way too. That's the bad thing about national carriers, they'll route your traffic in a financially sensible way, as opposed to regional carriers that actually do realize issues when they do arise. That server you just ran a trace to is located in Avon, MA. Here's the results of my trace to it:

Tracing route to chaos.dynastynet.net [209.213.76.242]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms winroute-gateway.omarnyc.com [10.11.12.1]
2 <10 ms <10 ms <10 ms rt314-router.omarnyc.com [10.14.12.1]
3 14 ms 13 ms <10 ms 10.180.192.1
4 14 ms 14 ms 14 ms 167.206.251.177
5 14 ms <10 ms 13 ms r4-srp9-0.cr.hcvlny.cv.net [167.206.12.84]
6 14 ms <10 ms 14 ms r2-srp5-0.cr.hcvlny.cv.net [167.206.12.18]
7 14 ms <10 ms 27 ms r1-srp5-0.in.hcvlny.cv.net [167.206.12.1]
8 14 ms 13 ms 14 ms pos2-2.gw9.nyc1.alter.net [157.130.61.161]
9 13 ms 14 ms 14 ms 0.so-7-0-0.xr3.nyc1.alter.net [152.63.9.26]
10 27 ms 14 ms 27 ms 207.atm6-0.xr1.bos1.alter.net [152.63.27.109]
11 14 ms 27 ms 14 ms 191.atm7-0.gw3.bos1.alter.net [146.188.177.209]
12 13 ms 28 ms 27 ms meganet-gw.customer.alter.net [157.130.15.14]
13 14 ms 27 ms 28 ms hssi-03-1-ip-cascade1.bos.ma.meganet.net [209.21
3.71.10]
14 55 ms 27 ms 28 ms ip16.bepeterson.com [209.213.76.241]
15 28 ms 27 ms 28 ms chaos.dynastynet.net [209.213.76.242]

Trace complete.

I do feel your pain, I used to have Telocity DSL and their routing was just as bad, if not worse. I guess you can wait for things to get better, or move on to the realm of DSL (ugh!). Good luck!

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 11:05 pm

*** To YeOldeStonecat ***

That's not too bad, considering Sprint is routing your ISP's traffic as opposed to alter.net. I think alter.net has a much more ample national footprint, next to UUNet.

MosDef112 · Post by **MosDef112** » Thu Sep 27, 2001 11:11 pm

*** To YeOldeStonecat ***

You live in Albany, NY?

Post by **YeOldeStonecat** » Fri Sep 28, 2001 6:59 am

I live in Mystic CT...the southeastern corner of the state on the shoreline.

You mention Sprint and Alter...my ISP used to use Alternet up til mid summer.

MosDef112 · Post by **MosDef112** » Fri Sep 28, 2001 7:56 am

Oh, okay. Cool.. Why did your ISP switch?

DaveM · Post by **DaveM** » Fri Sep 28, 2001 10:47 am

None of the trace routes you gave us show pings in the 600ms range.

This leads me to believe you are not running some program that you normally run,except when you are doing the tests, like an FTP server.

However, if your upload reaches your speed cap ie. you're running a an ftp server and somebody is downloading full speed from you, your pings will be 600ms.

The only way to lower your pings, if you are running an FTP server or some other server that is max'ing out your upload, is to set a speed limit on the maximum rate your server can send data, and to limit the number of concurrent connections.

Again, you have not shown us any traceroutes that have a destination ping greater than the lower 100 range !!!

MosDef112 · Post by **MosDef112** » Fri Sep 28, 2001 10:53 am

True, but his latency isn't that low either, and the way his routing takes place isn't exactly the best that could be had. His latency could average 70ms, but if his network routes his traffic to any game server the way it is, he will never be able to participate in interactive games in real-time, but rather in near real-time. Average latency in any given Internet line simply suggests the network isn't congested, it does not suggest that the path it's taking from your node to the remote host isn't excessively lengthy.