Speeds all over the place...

Marcin541 · December 11, 2004

Around 6-10Pm my speed is all over the place. I mean, all over... Sometimes 3.1Mbps, sometimes 600kbps. Is anyone else experiancing these problems? My guess is packet loss. Upload is fine though.

This is my tracert to testmy.net, anything wrong in there? It seems like a pretty long route though lol

Microsoft Windows XP [Version 5.1.2600]

C:Documents and SettingsMarcin B.HOMEPC>tracert testmy.net

Tracing route to testmy.net [67.19.36.6]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dslrouter [192.168.1.1]

2 31 ms 32 ms 33 ms 10.32.107.1

3 23 ms 24 ms 23 ms at-3-0-0-1727.CORE-RTR2.NY325.verizon-gni.net [1

30.81.11.53]

4 26 ms 27 ms 28 ms so-4-0-0-0.BB-RTR2.NY325.verizon-gni.net [130.81

.8.29]

5 23 ms 24 ms 23 ms so-1-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.

81.4.14]

6 28 ms 28 ms 30 ms so-6-2-0-0.gar2.NewYork1.Level3.net [65.59.196.1

7]

7 30 ms 62 ms 30 ms ae-1-51.bbr1.NewYork1.Level3.net [4.68.97.1]

8 75 ms 115 ms 81 ms so-0-0-0.bbr2.Dallas1.Level3.net [64.159.0.137]

9 70 ms 71 ms 73 ms ge-1-2-56.car3.Dallas1.Level3.net [4.68.122.166]

10 67 ms 66 ms 67 ms 4.78.220.10

11 82 ms 75 ms 73 ms dist-vlan31.dsr3-2.dllstx3.theplanet.com [70.85.

127.30]

12 77 ms 77 ms 76 ms dist-vlan22.dsr1-2.dllstx2.theplanet.com [70.85.

127.76]

13 66 ms 67 ms 67 ms dsr2-1-v1.dllstx4.theplanet.com [12.96.160.7]

14 69 ms 69 ms 70 ms gig1-0-2.tp-car9-2.dllstx4.theplanet.com [67.18.

116.86]

15 67 ms 67 ms 67 ms 6.67-19-36.reverse.theplanet.com [67.19.36.6]

Trace complete.

C:Documents and SettingsMarcin B.HOMEPC>

RTB · December 12, 2004

8 75 ms 115 ms 81 ms so-0-0-0.bbr2.Dallas1.Level3.net [64.159.0.137

That one is awfully high, but I'm not sure if it is your ISP's fault, or just a failing node on your route. In the second case there is nothing you can do about it.

Marcin541 · December 12, 2004

Its not just testmy.net that is slow, its all testing sites

Mr. Hahn · December 12, 2004

That node is in Dallas, so I doubt it's in his ISP's network since he lives in NY. Your second hop starts you off higher than I normally see. I beleive it's located somewhere within your home network somewhere after the router.

VanBuren · December 12, 2004

this is your first hop after router 31 ms 32 ms 33 ms 10.32.107.1

it seems too high it suppose to be between 5-15 ms for you.

is this node unstable? Do you sometimes get lower pings on this node?

VanBuren

Mr. Hahn · December 12, 2004

Yeah, that's the one I was talking about. I just called it the second hop so he could reference it on the tracert results.

Marcin541 · December 12, 2004

Microsoft Windows XP [Version 5.1.2600]

C:Documents and Settings>tracert testmy.net

Tracing route to testmy.net [67.19.36.6]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dslrouter [192.168.1.1]

2 23 ms 23 ms 23 ms 10.32.107.1

3 * 33 ms 36 ms at-3-0-0-1726.CORE-RTR1.NY325.verizon-gni.net [1

30.81.11.49]

4 24 ms 24 ms 24 ms so-4-0-0-0.BB-RTR1.NY325.verizon-gni.net [130.81

.8.25]

5 30 ms 29 ms 29 ms so-0-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.

81.4.10]

6 23 ms 23 ms 24 ms so-6-2-0-0.gar2.NewYork1.Level3.net [65.59.196.1

7]

7 30 ms 24 ms 23 ms ae-1-53.bbr1.NewYork1.Level3.net [4.68.97.65]

8 63 ms 64 ms 65 ms so-0-0-0.bbr2.Dallas1.Level3.net [64.159.0.137]

9 63 ms 64 ms 63 ms ge-1-1-55.car3.Dallas1.Level3.net [4.68.122.134]

10 68 ms 71 ms 71 ms 4.78.220.10

11 65 ms 66 ms 67 ms dist-vlan31.dsr3-2.dllstx3.theplanet.com [70.85.

127.30]

12 83 ms 69 ms 67 ms dist-vlan22.dsr1-2.dllstx2.theplanet.com [70.85.

127.76]

13 75 ms 77 ms 80 ms dsr2-1-v2.dllstx4.theplanet.com [12.96.160.39]

14 68 ms 76 ms 73 ms gig1-0-2.tp-car9-2.dllstx4.theplanet.com [67.18.

116.86]

15 67 ms 67 ms 71 ms 6.67-19-36.reverse.theplanet.com [67.19.36.6]

Trace complete.

When i ping the first one i get an average of 27ms

VanBuren · December 12, 2004

do you have modem installed on your first incoming phone socket?

VanBuren

The Reverend · December 12, 2004

There is no need to "guess" if it's packet loss. Just get to a command prompt and type:

ping www.google.com ..then hit the Enter Key. All four pings should come back as 100%. (....meaning that under the "ping returns" it should say Lost = 0 If you are losing packets it will show less than 100% (loss = ? (higher than 0), which means it is time to call your ISP to get it nailed down

It's normal to DROP packets, because they are just resent, but you never want to be LOSING packets ...that will screw up the works bigtime my friend. Loss = 0 is the only acceptable thing you want to see.

RTB · December 12, 2004

When testing out if it's packet loss I think that 4 pings is not enough. Either specify a much larger amount of pings (like 25 - 50), or set it up to go on forever. That way you can see packetloss much better.

Marcin541 · December 12, 2004

A ping to google,

Microsoft® Windows DOS

©Copyright Microsoft Corp 1990-2001.

C:DOCUME~1MARCIN~1.HOM>ping google.com

Pinging google.com [216.239.37.99] with 32 bytes of data:

Reply from 216.239.37.99: bytes=32 time=31ms TTL=243

Reply from 216.239.37.99: bytes=32 time=30ms TTL=243

Reply from 216.239.37.99: bytes=32 time=31ms TTL=243

Reply from 216.239.37.99: bytes=32 time=32ms TTL=243

Ping statistics for 216.239.37.99:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 30ms, Maximum = 32ms, Average = 31ms

C:DOCUME~1MARCIN~1.HOM>

And Van, do you mean, is my phone cord connected directly into the main phone jack? I dont understand

VanBuren · December 12, 2004

your modem has a middlebox socket right? So you can use both modem and a phone in main jacket?

What i mean is that its best to have the modem direct connected to the main phone jacket. And if your pc in further away, then use a long LAN cable from modem instead.

alot of phone extension wires will bring down your speed.

VanBuren

Marcin541 · December 12, 2004

I thought that at first, but then how come it slows down only between 6-10PM, not all the time? Its not like the phone wire grows any longer at that time.

EDIT:

Speed test run at 11:40AM

:::.. Download Stats ..:::

Connection is:: 2842 Kbps about 2.8 Mbps (tested with 2992 KB)

Download Speed is:: 347 KB/s

Tested From:: http://www.testmy.net/

Bottom Line:: 51 times faster than 56K you can download 1MB in 2.95 second(s)

Validation Link:: https://testmy.net/cgi-bin/get.cgi?Test_ID=BNQRGUFAS

VanBuren · December 12, 2004

yea thats correct, phone wire dosent grow

But using your modem in first phone jacket, will minimize the risk that the problem is at your home.

This problem is out of your control, you need to contact your ISP and complain, make tracerts and add date and time so they got something to work with.

VanBuren

Marcin541 · December 12, 2004

The problem,

My tracert and pings are pretty much the same all day long, but my speed is crazy. So me making tracert's and pings wont help much.

xs1 · December 12, 2004

When testing out if it's packet loss I think that 4 pings is not enough. Either specify a much larger amount of pings (like 25 - 50)' date=' or set it up to go on forever. That way you can see packetloss much better.[/quote']

start > run > cmd ping -t <address here > - unlimited ping

start > run > cmd ping -t -l <value> <address here> unlimited ping w/ value set ; could get you banned from many servers tho.

VanBuren · December 12, 2004

you should get Neotrace, then leave it on pinging the complete route for a few min each time.

Here is a ss how the ping can look like, max min values for each node,

my guess its just very unstable at those times,

VanBuren

Marcin541 · December 12, 2004

One timed out,

Microsoft Windows XP [Version 5.1.2600]

C:Documents and SettingsMarcin B.HOMEPC>ping -t -l 999 google.com

Pinging google.com [216.239.37.99] with 999 bytes of data:

Reply from 216.239.37.99: bytes=56 (sent 999) time=44ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=51ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=42ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=45ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=53ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=43ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=46ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=43ms TTL=243

Request timed out.

Reply from 216.239.37.99: bytes=56 (sent 999) time=42ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=44ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=43ms TTL=243

Reply from 216.239.37.99: bytes=56 (sent 999) time=41ms TTL=243