Anyone experiencing packetloss on these hops?

dpr1-so-0-0-0.DallasEquinix.savvis.net (14 PL% )
aer1-po10.DallasEquinix.savvis.net (2 PL%)

dist-vlan-42.dsr2-2.dllstx4.theplanet.com (somtimes makes it increase apox 2 hops, like its looping)

And since when did the route change? I use to get routed thru Level3.

best to do a ping and see if you lose packets

ping -n 100 yourip

From my home in STL, MO - lowest ping (out of 50 pings) was 41, highest was 49. Normally my DSL pings around 40 to the Dallas area so I'd say its bad routing or bad routing at that moment.

im having problems too with packet loss on those
from the server i can start tracing and pinging inside of the datacenters network and get packet loss so i know its not my problem.
here is from the server to an ip inside thier network
Matt's traceroute [v0.52]
ns2.siteguruz.com Fri Jul 15 22:13:37 2005
Keys: D - Display mode R - Restart statistics Q - Quit
Packets Pings
Hostname %Loss Rcv Snt Last Best Avg Worst
1. 1.67-19-229.reverse.theplanet.com 0% 31 31 0 0 0 1
2. gig4-8.dsr2-2.dllstx4.theplanet.com 0% 31 31 0 0 22 197
3. dist-vlan-42.dsr3-1.dllstx3.theplanet.com 0% 30 30 0 0 9 122
4. ae0-0.ibr1.dllstx3.theplanet.com 4% 29 30 1 1 1 1


not sure if it will look correct but that hop 4 seems to be having issues, or maybe the return path back from 4. also, this should never happen unless my server gets unplugged. this is from pings to my server from home

Reply from 67.19.229.5: bytes=32 time=10ms TTL=53
Reply from 67.19.229.5: bytes=32 time=11ms TTL=53
Reply from 67.19.229.5: bytes=32 time=14ms TTL=53
Reply from 67.19.229.5: bytes=32 time=10ms TTL=53
Reply from 67.19.229.5: bytes=32 time=11ms TTL=53
Reply from 67.19.229.5: bytes=32 time=13ms TTL=53
Reply from 67.19.229.5: bytes=32 time=12ms TTL=53
Reply from 67.19.229.5: bytes=32 time=10ms TTL=53
Reply from 67.19.229.5: bytes=32 time=9ms TTL=53
Reply from 70.85.127.97: TTL expired in transit.
Reply from 67.19.229.5: bytes=32 time=11ms TTL=53
Reply from 70.85.127.97: TTL expired in transit.
Reply from 67.19.229.5: bytes=32 time=10ms TTL=53
Reply from 67.19.229.5: bytes=32 time=10ms TTL=53
Reply from 67.19.229.5: bytes=32 time=11ms TTL=53
Reply from 67.19.229.5: bytes=32 time=11ms TTL=53
Reply from 67.19.229.5: bytes=32 time=9ms TTL=53
Reply from 67.19.229.5: bytes=32 time=10ms TTL=53
Reply from 67.19.229.5: bytes=32 time=9ms TTL=53
Reply from 67.19.229.5: bytes=32 time=18ms TTL=53
Reply from 67.19.229.5: bytes=32 time=11ms TTL=53
Reply from 67.19.229.5: bytes=32 time=16ms TTL=53

those expired in transits mean the packet was looped around the network until the ttl expired, this is caused by the packet being held in a buffer too long or when its passed back and forth between 2 or more routers until the ttl runs out. then tehn icmp control message is sent back saying ttl expired. thus some of the packets made it to the datacenter and not to my server, the ip reporting the ttl expired is likely the last good one since it could speak back to me to give that error.. i also have game servers running on this box and all players on it complain of terrible lag, packet loss showing in the lagometer, and the cpu is at .04 % usage so its not a load issue.

Any SM Staff gonna respond? These packet loss are horrible, cant even enjoy the game server.

As you can see from the image I posted earlier and this new one (hours later), phatblinkie states and experiences exactly what I am experiencing. Packets are looping and timing out.

Use charter...I go through att and get 27 ms with no packet loss :-)

Only 4 hops away...my server records less than 1ms ping times.
-But to your ISP assuming 71.109.61.1 is your ISP (from my house) I'm getting no better than 110ms
-From SM-server side, to your ISP, I'm getting, 34ms.

Don't expect a SM-rep to comment on all these types of threads. Thats what phone calls and TroubleTickets are for.

Since the traffic flows through Level(3) and there's a maint-schedule for said provider...I'm wondering if thats related.

http://ws.arin.net/whois/?queryinput=70.85.127.97
the ip that was giving me the ttl expired is yours, so why didnt it forward the packet(s) to my server?

Yes Nforcer, I know about phone and ticked

It just happens that this is not my server nor did I have the login info at the time of initial post.

One things for sure, there is problems inside The Planet network.

The Planet to my ISP

Traceroute doesn't really show a whole lot.

Your better to do a png and see if your losing packets.

Routers treat traceroute packets as a low priority packet. Therefore if a router is heavily loaded, it will drop the packet.

Ping it and see if you gettng packet loss, then if you are do the trace to see where its happening at.

Then open up a ticket with support so they can look into it.

right, ok we will ping, like this. notice the missing sequence numbers, and yes thisis from my server to a router on servermatrix network
[root@ns2 root]# ping 70.85.127.34
PING 70.85.127.34 (70.85.127.34) 56(84) bytes of data.
64 bytes from 70.85.127.34: icmp_seq=0 ttl=252 time=7.06 ms
64 bytes from 70.85.127.34: icmp_seq=1 ttl=252 time=1.12 ms
64 bytes from 70.85.127.34: icmp_seq=2 ttl=252 time=1.08 ms
64 bytes from 70.85.127.34: icmp_seq=3 ttl=252 time=0.960 ms
64 bytes from 70.85.127.34: icmp_seq=4 ttl=252 time=1.14 ms
64 bytes from 70.85.127.34: icmp_seq=5 ttl=252 time=1.14 ms
64 bytes from 70.85.127.34: icmp_seq=6 ttl=252 time=0.996 ms
64 bytes from 70.85.127.34: icmp_seq=7 ttl=252 time=1.33 ms
64 bytes from 70.85.127.34: icmp_seq=8 ttl=252 time=1.16 ms
64 bytes from 70.85.127.34: icmp_seq=12 ttl=252 time=1.05 ms
64 bytes from 70.85.127.34: icmp_seq=14 ttl=252 time=1.23 ms
64 bytes from 70.85.127.34: icmp_seq=15 ttl=252 time=1.09 ms
64 bytes from 70.85.127.34: icmp_seq=16 ttl=252 time=0.921 ms
64 bytes from 70.85.127.34: icmp_seq=17 ttl=252 time=1.26 ms
64 bytes from 70.85.127.34: icmp_seq=18 ttl=252 time=1.11 ms
64 bytes from 70.85.127.34: icmp_seq=19 ttl=252 time=1.41 ms
64 bytes from 70.85.127.34: icmp_seq=20 ttl=252 time=1.25 ms
64 bytes from 70.85.127.34: icmp_seq=21 ttl=252 time=1.16 ms
64 bytes from 70.85.127.34: icmp_seq=22 ttl=252 time=1.06 ms
64 bytes from 70.85.127.34: icmp_seq=23 ttl=252 time=1.13 ms
64 bytes from 70.85.127.34: icmp_seq=24 ttl=252 time=1.16 ms

--- 70.85.127.34 ping statistics ---
25 packets transmitted, 21 received, 16% packet loss, time 24192ms
rtt min/avg/max/mdev = 0.921/1.423/7.061/1.266 ms, pipe 2


and here is another one
[root@ns2 root]# ping -s 400 70.85.127.34
PING 70.85.127.34 (70.85.127.34) 400(428) bytes of data.
408 bytes from 70.85.127.34: icmp_seq=0 ttl=252 time=1.67 ms
408 bytes from 70.85.127.34: icmp_seq=1 ttl=252 time=1.31 ms
408 bytes from 70.85.127.34: icmp_seq=2 ttl=252 time=1.72 ms
408 bytes from 70.85.127.34: icmp_seq=3 ttl=252 time=1.62 ms
408 bytes from 70.85.127.34: icmp_seq=4 ttl=252 time=1.46 ms
408 bytes from 70.85.127.34: icmp_seq=5 ttl=252 time=1.77 ms
408 bytes from 70.85.127.34: icmp_seq=6 ttl=252 time=1.65 ms
408 bytes from 70.85.127.34: icmp_seq=10 ttl=252 time=1.31 ms
408 bytes from 70.85.127.34: icmp_seq=11 ttl=252 time=1.33 ms
408 bytes from 70.85.127.34: icmp_seq=12 ttl=252 time=1.32 ms
408 bytes from 70.85.127.34: icmp_seq=13 ttl=252 time=1.58 ms
408 bytes from 70.85.127.34: icmp_seq=14 ttl=252 time=1.42 ms
408 bytes from 70.85.127.34: icmp_seq=15 ttl=252 time=1.27 ms

--- 70.85.127.34 ping statistics ---
16 packets transmitted, 13 received, 18% packet loss, time 15117ms
rtt min/avg/max/mdev = 1.276/1.499/1.776/0.173 ms, pipe 2

We are looking into the issue. If there are other datapoints such as if it is occuring to other D4 hosts or if it is isolated to a particular provider this info would be useful.

I am also experiencing serious lag hiccups in my server at: 67.19.177.250 ever since July 14th. Here is my tracert:

Traceroute to: 67.19.177.250 from my computer:

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsCarlos>tracert 67.19.177.250

Tracing route to 250.67-19-177.reverse.theplanet.com [67.19.177.250]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 5 ms 15 ms 10.14.64.1
3 15 ms 6 ms 15 ms dstswr1-Vlan2.rh.frptny.cv.net [167.206.32.161]

4 6 ms 5 ms 8 ms r1-ge0-1-2.mhe.hcvlny.cv.net [167.206.32.129]
5 7 ms 6 ms 6 ms r2-srp0-0.wan.hcvlny.cv.net [65.19.104.195]
6 8 ms 13 ms 10 ms r2-srp13-0.in.nycmnyzr.cv.net [65.19.96.136]
7 20 ms 13 ms 13 ms r1-pos3-0.in.asbnva16.cv.net [65.19.97.226]
8 * * * Request timed out.
9 25 ms 22 ms 14 ms so-4-0-0.mpr2.iad2.us.above.net [64.125.30.122]

10 18 ms 17 ms 15 ms so-0-0-0.mpr1.iad2.us.above.net [64.125.28.25]
11 33 ms 26 ms 57 ms so-4-0-0.mpr2.iad1.us.above.net [64.125.29.133]

12 14 ms 14 ms 13 ms so-1-0-0.cr2.dca2.us.above.net [64.125.28.129]
13 44 ms 65 ms 41 ms so-2-2-0.cr2.dfw2.us.above.net [64.125.29.9]
14 47 ms 55 ms 49 ms 216.200.6.237.theplanet.com [216.200.6.237]
15 44 ms 44 ms 44 ms dist-vlan31.dsr3-1.dllstx3.theplanet.com [70.85.
127.29]
16 120 ms 212 ms 75 ms dist-vlan-42.dsr2-2.dllstx4.theplanet.com [70.85
.127.91]
17 47 ms 45 ms 46 ms gig1-0-2.sm-car6-11.dllstx4.theplanet.com [67.19
.255.170]
18 47 ms 46 ms 46 ms 250.67-19-177.reverse.theplanet.com [67.19.177.2
50]

Trace complete.

C:Documents and SettingsCarlos>



Tracert to my computer@ 68.195.21.133:

Microsoft Windows [Version 5.2.3790]
© Copyright 1985-2003 Microsoft Corp.

C:Documents and SettingsAdministrator>tracert 68.195.21.133

Tracing route to ool-44c31585.dyn.optonline.net [68.195.21.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 249.67-19-177.reverse.theplanet.com [67.19.177.2
49]
2 <1 ms <1 ms <1 ms gig4-7.dsr2-2.dllstx4.theplanet.com [67.19.255.1
69]
3 <1 ms <1 ms <1 ms dist-vlan-42.dsr3-1.dllstx3.theplanet.com [70.85
.127.89]
4 1 ms 1 ms <1 ms ae1-0.ibr3.dllstx3.theplanet.com [70.85.127.35]

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-02-ge-3-1-0-504.dlfw.twtelecom.net [66.192.
253.124]
7 37 ms 37 ms 37 ms core-01-so-0-0-0-0.asbn.twtelecom.net [66.192.25
5.19]
8 37 ms 37 ms 37 ms peer-01-so-0-0-0-0.asbn.twtelecom.net [66.192.25
5.229]
9 37 ms 32 ms 32 ms r1-ge10-1-1.in.asbnva16.cv.net [65.19.100.90]
10 37 ms 38 ms 37 ms r2-pos2-2.in.nycmnyzr.cv.net [65.19.97.225]
11 38 ms 38 ms 38 ms r1-srp13-0.wan.hcvlny.cv.net [65.19.96.49]
12 38 ms 38 ms 39 ms r2-srp5-0.mhe.hcvlny.cv.net [65.19.104.210]
13 39 ms 38 ms 39 ms dstswr2-ge3-16.rh.frptny.cv.net [167.206.32.134]

14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:Documents and SettingsAdministrator>