If you want to report packet loss or latency, please include the following:
[list]Your server's IP address
The remote IP address
Traceroute both from the remote IP to the server and from the server to the remote IP
Ping results from 100 pings sent from the remote IP to the server (and vice versa)[list]
If you don't include all of the above, then we will not be able to troubleshoot the problem effectively and we will not attempt to do so.

Thanks for your cooperation

A little note. Please dont include all 100 pings in your post. The summary will do.

Please excuse my ignorance but... Is there a special command line other than "traceroute XXX.XXX.XXX.XXX" to use for this:
"Ping results from 100 pings sent from the remote IP to the server (and vice versa)"

?

Regards,

Yves

To do 100 pings from a windows machine open your command prompt
[list]win xp: start -> run -> cmd
win 9x: start -> run -> command

[*]Then at the command prompt type
ping -n 100 xxx.xxx.xxx.xxx[list]
(xxx.xxx.xxx.xxx being your server IP)

To do 100 pings from a linux server to your home computer:
[list]login via ssh
[*]Type:
ping -c 100 xxx.xxx.xxx.xxx[list]
(xxx.xxx.xxx.xxx being your home IP)

Note:
They only want the summary of the pinging:
Ping statistics for x:
Packets: Sent = 100, Received = x, Lost = x (x% loss),
Approximate round trip times in milli-seconds:
Minimum = xms, Maximum = xms, Average = xms

edit: used a bit of formatting

Thank you Paul
Excellent How-To. All is there

Yves

Hello there SM!

How would i do a traceroute on a WindowsXP machine ?

go to start, run, then type cmd in there type

tracert yourdomain.com > C:/trace.txt

This will put all the info of the traceroute in a txt file on drive C.

PS I'm not part of SM I'm just a proud customer

Hi,

Got a guy here who says that before he used to ping 60-70 but now he pings 130.. or 100, etc

trace from client to sm

1 10 ms 10 ms 10 ms 64.230.254.12
2 9 ms 9 ms 8 ms HSE-Sherbrooke-ppp98648.qc.sympatico.ca [64.230.222.41]
3 8 ms 8 ms 8 ms HSE-Sherbrooke-ppp98628.qc.sympatico.ca [64.230.222.21]
4 65 ms 65 ms 65 ms core2-vancouver-pos10-2.in.bellnexxia.net [206.108.101.182]
5 69 ms 70 ms 69 ms core2-seattle-pos12-0.in.bellnexxia.net [206.108.102.209]
6 69 ms 70 ms 69 ms bx3-seattle-pos5-0.in.bellnexxia.net [206.108.102.202]
7 70 ms 69 ms 70 ms 206.108.108.154
8 69 ms 70 ms 69 ms P3-0.c0.sttl.broadwing.net [216.140.0.9]
9 89 ms 89 ms 90 ms 216.140.0.89
10 93 ms 93 ms 93 ms 216.140.17.53
11 94 ms 94 ms 93 ms S2-2-0.a1.dlls.broadwing.net [216.140.4.226]
12 108 ms 99 ms 99 ms 67.99.43.234
13 175 ms 215 ms 215 ms car2-6-v1.dllstx2.theplanet.com [12.96.160.22]
14 99 ms 100 ms 100 ms 243.69-56-165.reverse.theplanet.com [69.56.165.2
43]

from sm to client

traceroute to 69.158.57.3 (69.158.57.3), 30 hops max, 38 byte packets
1 17.69-93-49.reverse.theplanet.com (69.93.49.17) 0.933 ms 0.425 ms 0.383 ms
2 ibr3-ge-0-0-0-v2.dllstx2.theplanet.com (12.96.160.35) 0.389 ms 0.284 ms 0.382 ms
3 ge-0-2-1.ar1.DAL2.gblx.net (64.213.176.149) 0.594 ms 0.500 ms 0.557 ms
4 pos8-0-622m.cr1.dal1.gblx.net (67.17.73.29) 0.594 ms 1.303 ms 0.564 ms
5 so1-0-0-2488M.ar2.CHI1.gblx.net (67.17.71.82) 31.738 ms 31.824 ms 31.670 ms
6 bx2-chicago23-pos1-0.in.bellnexxia.net (206.108.108.217) 90.475 ms 90.497 ms 90.822 ms
7 core1-chicago23-pos10-3.in.bellnexxia.net (206.108.103.137) 81.310 ms 80.981 ms 81.006 ms
8 core4-toronto12-pos6-3.in.bellnexxia.net (206.108.103.133) 90.790 ms 90.751 ms 90.579 ms
9 HSE-Sherbrooke-ppp98649.qc.sympatico.ca (64.230.222.42) 92.423 ms 91.969 ms 92.432 ms

no packet loss or anything, it's just his ping is high

Is there anything SM could do to perhaps reroute around that, or use a different provider for that route?

see this thread everyone on sympatico seems affected...

http://forums.servermatrix.com/viewtopic.php?t=7852

this thing is causing all the problems:
13 175 ms 215 ms 215 ms car2-6-v1.dllstx2.theplanet.com [12.96.160.22]

Periodic spikes in the CAR2-X routers is normal. This is caused because of the BGP scanning process that runs every minute on those routers.

The traceroute shows a spike in latency at that hop because of the way that a router forwards packets destined for connected interfaces (and how traceroute works). Basically, packets destined for a connected interface on a Cisco router is process-switched. The router treats these packets as low-priority and will often even dump them if the CPU is busy with other things. Normal packets (packets that aren't destined for a connected interface, but rather are being switched THROUGH an interface) are treated with the highest priority.

To prove this, try pinging your end host while simultaneously running your mtr/pingplotter/whatever tool. The end-to-end pings should not change, while the intermediate hops in the traceroute tool will spike all over the place.

This is exactly why traceroute is a poor tool for troubleshooting latency and packet loss. Traceroute is a great tool for determining sub-optimal routing paths - and that is what it was designed for. Ping is the best tool for troubleshooting packet loss and latency issues.

None of our routers are overloaded. Nothing blew up on June 3 (as has been speculated). We're looking into complaints about packet loss and if we find something wrong we will schedule a maintenance window to repair the problem.

Packet Loss lately throuhg telus and twtelcom

Incoming route from me to the Server is fine, outgoign from server to me is where packetloss is being seen

Tracing route to 132.69-93-235.reverse.theplanet.com [69.93.235.132]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router01 [192.168.0.1]
2 19 ms 4 ms 6 ms u56n1.win.eastlink.ca [24.222.56.1]
3 5 ms 6 ms 5 ms nwmn-asr2.eastlink.ca [24.215.102.73]
4 8 ms 9 ms 8 ms hlfx-br2.eastlink.ca [24.215.102.149]
5 10 ms 8 ms 10 ms 205.150.223.97
6 40 ms 23 ms 25 ms 143.at-5-0-0.XR2.MTL1.ALTER.NET [152.63.133.90]

7 23 ms 24 ms 23 ms 0.so-0-0-0.XL2.MTL1.ALTER.NET [152.63.133.41]
8 23 ms 24 ms 24 ms 0.so-0-1-0.TL2.MTL1.ALTER.NET [152.63.133.62]
9 71 ms 70 ms 70 ms 0.so-5-2-0.TL2.DFW9.ALTER.NET [152.63.1.149]
10 70 ms 69 ms 69 ms 0.so-7-0-0.CL2.DFW13.ALTER.NET [152.63.103.222]

11 68 ms 68 ms 70 ms POS7-0.GW1.DFW13.ALTER.NET [152.63.103.89]
12 82 ms 115 ms 79 ms theplanet-gw.customer.alter.net [157.130.143.226
]
13 98 ms 79 ms 83 ms car4-1-v2.dllstx2.theplanet.com [12.96.160.49]
14 88 ms 74 ms 79 ms 132.69-93-235.reverse.theplanet.com [69.93.235.1
32]

Trace complete.


Ping statistics for 69.93.235.151:
Packets: Sent = 100, Received = 98, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 122ms, Average = 78ms



Tracing route to u203n56.hfx.eastlink.ca [24.222.203.56]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 194.69-93-219.reverse.theplanet.com [69.93.219.1
94]
2 <10 ms <10 ms <10 ms ibr5-ge-0-1-0-v2.dllstx2.theplanet.com [12.96.16
0.37]
3 <10 ms <10 ms <10 ms hagg-01-ae0-998.dlfw.twtelecom.net [168.215.241.
149]
4 <10 ms <10 ms <10 ms core-01-ge-0-3-1-510.dlfw.twtelecom.net [66.192.
253.112]
5 16 ms 15 ms 16 ms core-02-so-0-0-0-0.chcg.twtelecom.net [66.192.25
5.88]
6 16 ms 31 ms 16 ms core-01-ge-0-2-1-2.chcg.twtelecom.net [66.192.24
4.64]
7 16 ms 31 ms 15 ms 66.192.244.36
8 32 ms 31 ms 47 ms 66.192.252.90
9 32 ms 31 ms 47 ms chcnil23gr00-chcnil23gr01.bb.telus.com [154.11.1
1.17]
10 47 ms 62 ms 63 ms toroonnlbr00.bb.telus.com [154.11.11.173]
11 63 ms 62 ms 63 ms mtrlpqfbbr00.bb.telus.com [154.11.11.30]
12 * 62 ms 79 ms hlfxnsalpe01.bb.telus.com [154.11.11.218]
13 63 ms 78 ms 63 ms hlfxnsaldr03.bb.telus.com [154.11.11.233]
14 63 ms 78 ms 78 ms 209.29.247.202
15 62 ms 78 ms 78 ms nwmn-asr2.eastlink.ca [24.215.102.150]
16 78 ms 63 ms 62 ms wnds-ubr1.eastlink.ca [24.215.102.74]
17 78 ms 79 ms 78 ms u203n56.hfx.eastlink.ca [24.222.203.56]

Trace complete.

Ping statistics for 24.222.203.56:
Packets: Sent = 100, Received = 97, Lost = 9 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 110ms, Average = 70ms


one other thing i notice is if i tracert to hop 16 is it is a much more direct route

Tracing route to wnds-ubr1.eastlink.ca [24.215.102.74]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 194.69-93-219.reverse.theplanet.com [69.93.219.
94]
2 <10 ms <10 ms <10 ms ibr3-ge-0-0-0-v1.dllstx2.theplanet.com [12.96.1
0.3]
3 <10 ms <10 ms <10 ms GigabitEthernet4-1.GW1.DFW13.ALTER.NET [157.130
143.225]
4 <10 ms <10 ms <10 ms 0.so-0-0-0.CL1.DFW13.ALTER.NET [152.63.103.86]
5 <10 ms <10 ms <10 ms 0.so-0-0-0.TL1.DFW9.ALTER.NET [152.63.0.193]
6 47 ms 47 ms 47 ms 0.so-7-0-0.TL2.MTL1.ALTER.NET [152.63.0.81]
7 47 ms 47 ms 46 ms 0.so-7-0-0.XL1.MTL1.ALTER.NET [152.63.133.65]
8 47 ms 47 ms 47 ms 0.so-3-0-0.XR1.MTL1.ALTER.NET [152.63.133.46]
9 62 ms 63 ms 62 ms 193.ATM6-0.GW2.HFX1.ALTER.NET [152.63.132.161]
10 62 ms 63 ms 62 ms 205.150.223.94
11 63 ms 62 ms 63 ms hlfx-br2.eastlink.ca [24.222.79.238]
12 63 ms 62 ms 63 ms nwmn-asr2.eastlink.ca [24.215.102.150]
13 63 ms 62 ms 63 ms wnds-ubr1.eastlink.ca [24.215.102.74]

Trace complete.



also rogers in ontario Canada

1 <1 ms <1 ms <1 ms 192.168.2.1
2 28 ms 29 ms 29 ms tlgw13.mtmc.phub.net.cable.rogers.com
[24.101.6
.1]
3 27 ms 34 ms 43 ms 66.185.92.129
4 26 ms 23 ms 23 ms 66.185.82.70
5 29 ms 23 ms 23 ms gw02.ym.phub.net.cable.rogers.com
[66.185.81.17
]
6 70 ms 65 ms 65 ms igw01.chcrmk.phub.net.cable.rogers.com
[66.185.
1.190]
7 68 ms 66 ms 69 ms sp0-5-CHCGILCA.broadwing.com
[206.223.119.72]
8 69 ms 65 ms 71 ms ge-2-1-0.a1.chcg.broadwing.net
[216.140.15.17]
9 73 ms 70 ms 71 ms 216.140.15.9
10 92 ms 89 ms 89 ms P4-0-4.c0.slkc.broadwing.net [216.140.16.25]
11 93 ms 94 ms 89 ms S2-2-0.a1.dlls.broadwing.net [216.140.4.226]
12 93 ms 89 ms 89 ms 67.99.43.234
13 100 ms 90 ms 88 ms car1-2-v2.dllstx2.theplanet.com

Out to Rogers

Hi. I have expirenced a rise in ping to my server from 65 to 95. Below are my tracert's and pings.
________________

From me (68.148.129.234) to server (67.19.137.106):

1 5 ms 6 ms 6 ms 10.146.192.1
2 7 ms 6 ms 6 ms rc1ar-ge3-0-14.ed.shawcable.net [64.59.189.178]
3 23 ms 23 ms 24 ms rc1nr-pos13-0.wp.shawcable.net [66.163.76.77]
4 24 ms 24 ms 24 ms rc2nr-pos15-0.wp.shawcable.net [66.163.73.130]
5 44 ms 42 ms 42 ms rc2ch-pos7-0.il.shawcable.net [66.163.76.174]
6 42 ms 42 ms 42 ms rc1ch-pos2-0.il.shawcable.net [66.163.65.1]
7 41 ms 42 ms 42 ms ge-4-0-115.ipcolo1.Chicago1.Level3.net [4.79.64.13]
8 42 ms 42 ms 42 ms so-7-0-0.bbr1.Chicago1.Level3.net [4.68.112.201]
9 79 ms 79 ms 80 ms so-1-0-0.bbr1.Dallas1.Level3.net [209.247.11.22]
10 80 ms 78 ms 80 ms so-6-0.ipcolo1.Dallas1.Level3.net [4.68.112.178]
11 * * * Request timed out.
12 91 ms 90 ms 90 ms dsr2-1-v2.dllstx4.theplanet.com [12.96.160.39]
13 98 ms 96 ms 93 ms gig1-0-1.sm-car6-10.dllstx4.theplanet.com [67.19.255.38]
14 93 ms 92 ms 98 ms 106.67-19-137.reverse.theplanet.com [67.19.137.106]

Ping statistics for 67.19.137.106:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 103ms, Average = 91ms


__________________________________________

From server (67.19.137.106) to me (68.148.129.234):

1 <1 ms <1 ms <1 ms 105.67-19-137.reverse.theplanet.com [67.19.137.105]
2 <1 ms <1 ms <1 ms 67.19.255.165
3 1 ms 1 ms 1 ms dsr1-1-v2.dllstx2.theplanet.com [12.96.160.41]
4 <1 ms <1 ms <1 ms ibr5-ge-0-1-0-v2.dllstx2.theplanet.com [12.96.160.37]
5 1 ms 1 ms 1 ms hagg-01-ae0-998.dlfw.twtelecom.net [168.215.241.149]
6 1 ms 1 ms 1 ms core-01-ge-0-3-1-510.dlfw.twtelecom.net [66.192.253.112]
7 40 ms 40 ms 40 ms core-01-ge-2-3-0-1.nycl.twtelecom.net [66.192.255.2]
8 38 ms 38 ms 38 ms 66.192.240.54
9 41 ms 39 ms 40 ms rd1hu-fe10-0.ny.shawcable.net [198.32.160.86]
10 67 ms 66 ms 66 ms rc1sh-pos14-2.mt.shawcable.net [66.163.76.89]
11 66 ms 66 ms 66 ms rc1nr-pos14-0.wp.shawcable.net [66.163.76.74]
12 83 ms 83 ms 83 ms rc1ar-pos10-0.ed.shawcable.net [66.163.76.78]
13 84 ms 84 ms 84 ms dx1cw-g1.ed.shawcable.net [64.59.189.185]
14 89 ms 89 ms 90 ms S0106000c7655bfa2.ed.shawcable.net [68.148.129.234]

Ping statistics for 68.148.129.234:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 100ms, Average = 90ms

---------------------------------------

Dont know what you can do for me but any help is appreciated as my ping is the most important thing for my server. Thanks!

It now seems to be fixed. Im as happy as a pig in mud. ^_^

traceroute to 64.230.152.145 (64.230.152.145), 30 hops max, 38 byte packets
1 19.67-19-247.reverse.theplanet.com (67.19.247.19) 0.579 ms 0.303 ms 0.230
ms
2 dsr2-2-vl7.dllstx4.theplanet.com (67.18.116.66) 0.363 ms 0.294 ms 0.230 m
s
3 dsr1-2-v1.dllstx2.theplanet.com (12.96.160.10) 0.988 ms 0.732 ms 0.603 ms
4 ibr3-ge-0-0-0-v2.dllstx2.theplanet.com (12.96.160.35) 0.619 ms 0.700 ms 0
.608 ms
5 ge-0-2-1.ar1.DAL2.gblx.net (64.213.176.149) 0.997 ms 0.993 ms 1.090 ms
6 so1-0-0-2488M.ar2.CHI1.gblx.net (67.17.71.82) 32.359 ms 32.081 ms 32.085
ms
7 bx2-chicago23-pos1-0.in.bellnexxia.net (206.108.108.217) 81.060 ms 81.085
ms 81.121 ms
8 core1-chicago23-pos10-3.in.bellnexxia.net (206.108.103.137) 81.644 ms 81.4
49 ms 81.561 ms
9 core4-toronto63-pos6-3.in.bellnexxia.net (206.108.103.129) 81.287 ms 81.54
9 ms 81.465 ms
10 64.230.242.106 (64.230.242.106) 81.991 ms 81.737 ms 82.209 ms
11 core2-ottawa23-pos2-3.in.bellnexxia.net (64.230.229.22) 87.329 ms 87.270 m
s 89.670 ms
12 64.230.241.214 (64.230.241.214) 90.453 ms 87.478 ms 89.891 ms
13 64.230.228.42 (64.230.228.42) 92.362 ms 95.826 ms 90.169 ms
14 HSE-Kitchener-ppp232250.sympatico.ca (64.230.152.145) 92.165 ms 93.613 ms
92.292 ms
15 * *


Ping statistics for 67.19.247.20:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 104ms, Average = 94ms

Tracing route to zima.lockedonhosting.net [69.56.245.186]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms muddy-h89t9q9hb.mshome.net [192.168.0.1]
2 8 ms 7 ms 8 ms 64.230.254.46
3 6 ms 6 ms 6 ms 64.230.228.41
4 7 ms 6 ms 6 ms 64.230.241.209
5 12 ms 12 ms 12 ms core1-toronto12-pos9-3.in.bellnexxia.net [206.108.107.109]
6 12 ms 12 ms 12 ms 64.230.242.194
7 70 ms 69 ms 69 ms core2-vancouver-pos10-2.in.bellnexxia.net [206.108.101.182]
8 73 ms 72 ms 72 ms core2-seattle-pos12-0.in.bellnexxia.net [206.108.102.209]
9 73 ms 73 ms 73 ms bx3-seattle-pos5-0.in.bellnexxia.net [206.108.102.202]
10 74 ms 73 ms 73 ms 206.108.108.154
11 74 ms 73 ms 74 ms P3-0.c0.sttl.broadwing.net [216.140.0.9]
12 94 ms 94 ms 93 ms 216.140.0.89
13 87 ms 87 ms 86 ms 216.140.17.53
14 91 ms 87 ms 87 ms S2-2-0.a1.dlls.broadwing.net [216.140.4.226]
15 93 ms 93 ms 94 ms 67.99.43.234
16 94 ms 93 ms 93 ms car2-3-v1.dllstx2.theplanet.com [12.96.160.19]
17 95 ms 97 ms 98 ms zima.lockedonhosting.net [69.56.245.186]


--- 64.230.152.145 ping statistics ---
58 packets transmitted, 58 received, 0% packet loss, time 57571ms
rtt min/avg/max/mdev = 93.028/93.846/97.243/0.796 ms, pipe 2

anything new going on about this ?


jake

itd be nice to get a response from someone at theplanet.....

Have you opened a ticket or called us about this? Our network admins watch Orbit more frequently than the forums.

What's he even moaning about... that trace looks fine to me. :shock:

going from toronto to vancouver seatle to get to dfw used to ping under 50 now over 80 since they brought in broadwing.

Global Crossing maxing out:

Time Warner maxing out @ invisible 600mbit ceiling:

Packetloss according to ping plotter caused by Time Warner maxing out:


I've had a ticket open since the 22nd in orbit, we've played the cat and mouse game long enough and I'm tired of re-explaining what the problem is 4 times. Basically during peak times, Time Warner starts giving packetloss at about 600mbits. The problem has been on and off for a few weeks now. You can see the ceiling in the RTG graph. While I was waiting for a response, I noticed Global Crossing very badly maxed out so I captured that for this post as well. If there is anything else you need please let me know. Thanks.

I hate to sound nasty/repeating my self but,

give them a call! 2 ring sla, and poke them about the ticket, they will answer it quickly then


theres been a few problems with tickets lateley, i think they are just understaffed due to teh retro fits, but i could (and probally am) wrong

facecake,
I've called them twice, they said they are sorry that the problem hasn't been fixed and to respond to the ticket again via orbit.

Hey, I run ut2004 gameservers, and one of my clients that uses Adelphia is getting packetloss so I figured i'd try this..

1. Server IP is 67.19.67.196
2. Client IP is 69.167.110.37

3. From server:
Reply from 69.167.110.37: bytes=32 time=40ms TTL=47
Reply from 69.167.110.37: bytes=32 time=40ms TTL=47
Request timed out.
Reply from 69.167.110.37: bytes=32 time=41ms TTL=47
Request timed out.
Reply from 69.167.110.37: bytes=32 time=40ms TTL=47
Reply from 69.167.110.37: bytes=32 time=40ms TTL=47
Reply from 69.167.110.37: bytes=32 time=39ms TTL=47
Reply from 69.167.110.37: bytes=32 time=39ms TTL=47
Request timed out.
Reply from 69.167.110.37: bytes=32 time=39ms TTL=47
Reply from 69.167.110.37: bytes=32 time=40ms TTL=47

Ping statistics for 69.167.110.37:
Packets: Sent = 100, Received = 72, Lost = 28 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 95ms, Average = 40ms


4. From client:
Reply from 67.19.67.196: bytes=32 time=40ms TTL=111
Request timed out.
Reply from 67.19.67.196: bytes=32 time=40ms TTL=111
Reply from 67.19.67.196: bytes=32 time=42ms TTL=111
Request timed out.
Reply from 67.19.67.196: bytes=32 time=41ms TTL=111
Reply from 67.19.67.196: bytes=32 time=40ms TTL=111
Request timed out.
Reply from 67.19.67.196: bytes=32 time=40ms TTL=111
Reply from 67.19.67.196: bytes=32 time=39ms TTL=111

Ping statistics for 67.19.67.196:
Packets: Sent = 100, Received = 74, Lost = 26 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 83ms, Average = 43ms



Also, I ran a tracert using VisualRoute to the client (it pings it 100 times to get the average per route), and it's also showing packetloss.
http://n3tsplit.com/misc/report.html

Is there any way this can be fixed or maybe improved? My server from TP has been great so far, this is the only real hiccup I got with it.
He was getting no packetloss before the backbone upgrade, so i'm guessing something in that maybe did it?

Thanks.

Not sure if I would get any help opening a ticket for this. It seems to have began 2 weeks ago and mostly occurs at night.

Nothing really wrong with that trace route. It's the destination times that matter, which are excellent.

....

And I'm going to tell you bluntly to not act like an asshat.

Have you put a ticket in about this, and included everything they requested in the first post in this thread?

Actually I do know what I'm talking about. Routers prioritze traffic based on type. ICMP has a very low priority so if the router is busy, it will be slow to respond to ICMP requests. Notice that even though hop 10 had a high latency, every packet passing thru that router had excellent lateny. Who cares how long it takes a particular router to respond to ICMP if it is routing packets thru it without any issues. I would imagine if people are being dropped, then something else is going on. Perhaps you could post a traceroute from when people are being dropped.

Been having the packetloss on my box at SM since about 9:30AM CST today. Customers also reported latency and packet loss and am experiencing it on local PC, too.

From remote (managed.com DC):




From server to remote (managed.com DC):

Seeing Problems Here...









This is Horrible People.

How do you get a ping report like that?

ping -n 100 www.baddabinghosting.com > C:/pingresults2.txt

that's all I did

Linux is similar: ping <ip> -c 100 > ping.txt

Abovenet Packet Loss?

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 203-206-250-223.dyn.iinet.net.au - 0 | 354 | 354 | 0 | 9 | 120 | 0 |
| nexthop.nsw.iinet.net.au - 0 | 354 | 354 | 10 | 40 | 481 | 40 |
|gigabitethernet1-0-0-17.syd-pipe-bdr1.chime.net.au - 0 | 354 | 354 | 10 | 24 | 161 | 10 |
| GE-4-1-0.ar1.syd1.gblx.net - 0 | 354 | 354 | 10 | 25 | 200 | 10 |
| pos2-1.gw1.nrt4.asianetcom.net - 0 | 354 | 354 | 120 | 143 | 1021 | 1021 |
| ip-202-147-1-122.asianetcom.net - 0 | 354 | 354 | 120 | 144 | 611 | 251 |
| ip-202-147-1-33.asianetcom.net - 0 | 354 | 354 | 120 | 144 | 681 | 130 |
| as6461.nspixp2.wide.ad.jp - 0 | 354 | 354 | 120 | 140 | 460 | 130 |
| so-2-1-0.cr2.nrt3.jp.mfnx.net - 0 | 354 | 354 | 120 | 140 | 400 | 120 |
| so-3-2-1.cr1.sjc3.us.above.net - 0 | 354 | 354 | 190 | 207 | 440 | 200 |
| 64.125.27.105 - 55 | 354 | 162 | 190 | 215 | 881 | 221 |
| 64.125.30.2 - 63 | 354 | 131 | 190 | 216 | 821 | 291 |
| 64.125.29.54 - 47 | 354 | 191 | 260 | 290 | 2043 | 280 |
| 216.200.88.141 - 47 | 354 | 190 | 240 | 271 | 1923 | 250 |
| 70.85.127.61 - 47 | 354 | 190 | 240 | 269 | 621 | 250 |
| 70.85.127.67 - 47 | 354 | 190 | 240 | 265 | 621 | 301 |
| 12.96.160.7 - 47 | 353 | 190 | 240 | 275 | 761 | 251 |
| 67.19.255.14 - 47 | 353 | 189 | 240 | 272 | 841 | 841 |
| 70.84.245.2 - 47 | 353 | 190 | 240 | 272 | 680 | 260 |
|________________________________________________|______|______|______|______|__
____|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )

ping -n 100 67.19.170.90

Pinging 67.19.170.90 with 32 bytes of data:


Ping statistics for 67.19.170.90:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 144ms, Average = 89ms


zoominternet.net in ohio.. 2 weeks ago it was not this bad what happen

:shock:

whats so bad about that? 0% loss?

alot is, its causing very slow speeds for people trying to access demo songs for my band and our performances

here is the tracert

1 8 ms 56 ms 15 ms acs-24-239-80-1.zoominternet.net [24.239.80.1]
2 14 ms 11 ms 16 ms acs-24-154-0-75.zoominternet.net [24.154.0.75]
3 23 ms 59 ms 16 ms lco144.zoominternet.net [63.67.120.144]
4 23 ms 13 ms 47 ms lco140.zoominternet.net [63.67.120.140]
5 29 ms 19 ms 49 ms leg-208-30-204-161-RIA.sprinthome.com [208.30.20
4.161]
6 32 ms 68 ms 62 ms 144.232.13.145
7 66 ms 61 ms 68 ms sl-bb22-nyc-9-0.sprintlink.net [144.232.7.5]
8 72 ms 63 ms 68 ms sl-bb21-chi-9-0.sprintlink.net [144.232.9.149]
9 68 ms 69 ms 69 ms sl-bb21-fw-10-0.sprintlink.net [144.232.8.54]
10 71 ms 72 ms 117 ms sl-bb20-fw-14-0.sprintlink.net [144.232.11.217]

11 65 ms 125 ms 129 ms sl-st21-dal-1-0.sprintlink.net [144.232.20.17]
12 112 ms 74 ms 78 ms 144.232.29.97
13 77 ms 79 ms 67 ms sl-theplanet-3-0.sprintlink.net [144.228.250.114
]
14 74 ms 74 ms 113 ms dist-vlan31.dsr3-2.dllstx3.theplanet.com [70.85.
127.30]
15 75 ms 114 ms 75 ms dist-vlan22.dsr1-2.dllstx2.theplanet.com [70.85.
127.76]
16 75 ms 108 ms 70 ms dsr2-2-v1.dllstx4.theplanet.com [12.96.160.8]
17 69 ms 75 ms 73 ms gig1-0-2.sm-car6-3.dllstx4.theplanet.com [67.19.
255.138]
18 74 ms 79 ms 79 ms 90.67-19-170.reverse.theplanet.com [67.19.170.90
]

I don't see how 0% loss could be causing problems.

This thread is here to instruct how to report packet loss. If you need something investigated please open a support ticket with traceroutes to and from your server to the computer showing packet loss. We'll take it from there.

whoops sorry

Recently, me and everyone in my general area (Katy, Tx) on RoadRunner have been experiencing higher than average pings to every server in TP. We usually ping 18-23, but lately have been pinging 28-33. I've had problems with my 9th hop kicking my ping up before, and now it seems that it's returned. I'm not sure if this is the right place to post this, but it's worth a shot.

1 9 ms 7 ms 7 ms 10.58.32.1
2 11 ms 8 ms 16 ms gig2-2.hstntxcin-rtr2.houston.rr.com [24.28.101.70]
3 10 ms 9 ms 10 ms 24.28.100.219
4 10 ms 11 ms 9 ms pos0-0.hstntxtid-rtr1.texas.rr.com [24.93.34.98]
5 21 ms 22 ms 23 ms son1-0-2.dllatxl3-rtr1.texas.rr.com [24.93.34.38]
6 18 ms 22 ms 18 ms son2-0-0.hstqtxl3-rtr1.texas.rr.com [24.93.34.30]
7 23 ms 38 ms 21 ms so-3-2-0-0.gar2.Dallas1.Level3.net [4.78.234.17]
8 22 ms 21 ms 23 ms ge-1-1-53.car3.Dallas1.Level3.net [4.68.122.70]
9 27 ms 29 ms 26 ms 4.78.220.10
10 28 ms 27 ms 27 ms dist-vlan31.dsr3-1.dllstx3.theplanet.com [70.85.127.29]
11 26 ms 29 ms 26 ms po32.dsr1-2.dllstx5.theplanet.com [70.85.127.110]
12 30 ms 31 ms 42 ms po2.sm-car4.dllstx5.theplanet.com [70.84.160.166]
13 27 ms 29 ms 30 ms 19.70-86-107.reverse.theplanet.com [70.86.107.19]

Should I just sumbit a support ticket?

< on RoadRunner have been experiencing higher than average pings to every server in TP. We usually ping 18-23, but lately have been pinging 28-33

>Should I just sumbit a support ticket?

Are you serious or just trolling. I can't tell.

I know both are low, but there's still something going on that can possibly be fixed, so why not fix it?

Well, at least he posted here first instead of opening a ticket and wasting a tech's time with those pings. Are you running a game server at TP or something? Don't worry, those minor increases aren't going to affect your kill/death ratio.

If you're not running a game server, I definitely don't see a reason for opening a ticket.

I'm not concerned, I just saw something that wasn't working as fast as it could/should be and thought I'd report it since SM probably likes having their network running as fast as possible. I wasn't aware the earth would implode because I brought this up. ;

And yes heat, I am running a game server

I wish i got 23ms usualy mine are 98ms but then I live in cali. So that does not help.

My IP - 67.174.174.202
Server IP - 70.87.106.74

Tracing route to 74.70-87-106.reverse.theplanet.com [70.87.106.74]

over a maximum of 30 hops:



1 * * * Request timed out.

2 * * * Request timed out.

3 92 ms 119 ms 120 ms 68.87.205.117

4 3039 ms 89 ms 119 ms 68.87.207.65

5 108 ms 118 ms 116 ms 68.87.207.53

6 120 ms 119 ms 119 ms 68.87.207.58

7 71 ms 119 ms 120 ms 68.87.207.1

8 64 ms 119 ms 119 ms 68.87.207.5

9 118 ms 119 ms 119 ms 12.118.225.13

10 68 ms 120 ms 119 ms tbr2-p013801.dlstx.ip.att.net [12.123.17.62]

11 76 ms 119 ms 120 ms gar1-p370.dlrtx.ip.att.net [12.123.196.97]

12 77 ms 119 ms 120 ms 12.119.136.14

13 70 ms 119 ms 119 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61]

14 82 ms 120 ms 119 ms vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

15 93 ms 119 ms 120 ms gi1-0-1.car13.dllstx4.theplanet.com [67.19.255.58]

16 78 ms 119 ms 119 ms 74.70-87-106.reverse.theplanet.com [70.87.106.74]

Ping statistics for 70.87.106.74:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 177ms, Average = 91ms

I say it's unusual considering I live in Grapevine and the clan had a Battlefield 2 server hosted by ya'll before I never had a ping above 30ms.

That totally looks like your ISP though since it is higher from 30 all the way in... And that happens to me also on the same ISP (Comcast) every once in a while. Its just someone getting packeted/etc on your node that's causing it (or someone unlimited their modem to suck all the node's bandwidth maybe...). It will go away by tomorrow morning most of the time.

lol

Welp, after power cycling both the modem and router, latency is back to normal. YAY!