Partial Packet loss at BurstNET?

Portal Home > Knowledgebase > Articles Database > Partial Packet loss at BurstNET?

Posted by hostbox, 09-12-2004, 11:31 PM
Since I got this server I always had packet loss, they told me it was "on my end"... Now, if I could ask you a favor and if you are willing to do it for me, run the following command, copy and paste the results. Thank You. on CMD "ping -n 300 66.96.217.245" My Results: Ping statistics for 66.96.217.245: Packets: Sent = 542, Received = 521, Lost = 21 (3% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 3964ms, Average = 85ms Control-C ^C C:\Documents and Settings\Navigator>ping
Posted by CPUHosting, 09-13-2004, 12:52 AM
Ping statistics for 66.96.217.245: Packets: Sent = 300, Received = 285, Lost = 15 (5% loss), Approximate round trip times in milli-seconds: Minimum = 28ms, Maximum = 4366ms, Average = 117ms
Posted by t c, 09-13-2004, 01:04 AM
Remind me never to do that on dial up again, lol. Ping statistics for 66.96.217.245: - Packets: Sent = 300, Received = 286, Lost = 14 (4% loss) Approximate round trip times in milli-seconds: - Minimum = 205ms, Maximum = 4241ms, Average = 316ms
Posted by bhaputi, 09-13-2004, 10:34 AM
Do you have a ticket open on this? If so, it will be addressed. Keep in mind the ping results from people are not useful unless they also include a traceroute.
Posted by Joshua, 09-13-2004, 03:01 PM
My ping graphs at Burst (between my Burst server and Burst's Philly router) haven't shown any issues of spikes or packetloss in the past 24 hours. (See attached graph) Attached Images ping1.png (4.3 KB, 44 views)
Posted by PreciseHost, 09-14-2004, 12:53 PM
My Results: Ping statistics for 66.96.217.245: Packets: Sent = 300, Received = 217, Lost = 83 (27% loss), Approximate round trip times in milli-seconds: Minimum = 240ms, Maximum = 991ms, Average = 364ms Tracing route to scott.servernavigator.net [66.96.217.245] over a maximum of 30 hops: 1 <10 ms 10 ms <10 ms static-64-65-164-77.customer.sea.eschelon.com [64.65.164.77] 2 10 ms 10 ms 10 ms 172.17.33.17 3 30 ms 40 ms 40 ms core0-atm1-0-450.phx.eschelon.com [209.150.192.241] 4 80 ms 71 ms 90 ms s3-0-12.hsa1.phx1.bbnplanet.net [4.24.253.113] 5 80 ms 70 ms 80 ms so-6-0-0.mp1.Phoenix1.Level3.net [4.68.113.241] 6 90 ms 90 ms 90 ms so-0-2-0.mp1.Philadelphia1.Level3.net [209.247.8.69] 7 90 ms 90 ms 90 ms ge-11-0.hsa1.Philadelphia1.Level3.net [64.159.0.146] 8 111 ms 80 ms 90 ms 4.78.144.6 9 240 ms 240 ms 251 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.45] 10 250 ms 250 ms 251 ms scott.servernavigator.net [66.96.217.245] Trace complete.
Posted by mpjetta, 09-14-2004, 01:32 PM
We just moved into a full rack at Burst last week and are seeing 500ms pings right now, things have been pretty fast until now: [nate@marykate nate]$ ping -c 10 www.burst.net PING root.burst.net (66.96.192.201) 56(84) bytes of data. 64 bytes from burst.net (66.96.192.201): icmp_seq=1 ttl=53 time=500 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=2 ttl=53 time=497 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=3 ttl=53 time=490 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=4 ttl=53 time=491 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=5 ttl=53 time=498 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=6 ttl=53 time=506 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=7 ttl=53 time=499 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=8 ttl=53 time=504 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=9 ttl=53 time=491 ms 64 bytes from burst.net (66.96.192.201): icmp_seq=10 ttl=53 time=492 ms --- root.burst.net ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9007ms rtt min/avg/max/mdev = 490.005/497.193/506.103/5.508 ms [nate@marykate nate]$ /usr/sbin/traceroute www.burst.net traceroute to root.burst.net (66.96.192.201), 30 hops max, 38 byte packets 1 192.168.0.1 (192.168.0.1) 0.706 ms 0.694 ms 0.795 ms 2 10.18.224.1 (10.18.224.1) 7.333 ms 7.341 ms 6.453 ms 3 vl200.cat1.sbo.ma.rcn.net (209.6.160.100) 8.035 ms 6.293 ms 8.136 ms 4 ge3-0.core2.sbo.ma.rcn.net (207.172.15.130) 7.873 ms 6.992 ms 8.316 ms 5 pos6-0.core2.chsl.il.rcn.net (208.59.95.10) 36.079 ms 37.451 ms 36.542 ms 6 ge5-0.border1.eqnx.il.rcn.net (207.172.19.15) 40.500 ms 36.371 ms 37.528 ms 7 ge3-0.cr01.chc01.pccwbtn.net (206.223.119.48) 35.030 ms 35.514 ms 35.961 ms 8 pos5-2.cr01.phl02.pccwbtn.net (63.218.30.45) 43.046 ms 42.912 ms 42.020 ms 9 hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net (63.218.31.6) 269.909 ms 270.723 ms 261.828 ms 10 ge-7-0-ctsi.rtr0.scra1.hostnoc.net (66.197.191.45) 494.220 ms 490.939 ms 470.170 ms 11 * * 66.197.191.82 (66.197.191.82) 495.355 ms 12 * burst.net (66.96.192.201) 487.827 ms 487.621 ms Looks like things are slowing from Philly to Scranton although I am not exactly sure.
Posted by fiks, 09-14-2004, 03:54 PM
what is TTL??
Posted by pztup, 09-15-2004, 02:58 AM
DSL from San Jose UU.NET Ping statistics for 66.96.217.245: Packets: Sent = 15, Received = 15, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 102ms, Maximum = 121ms, Average = 105ms Tracing route to scott.servernavigator.net [66.96.217.245] over a maximum of 30 hops: 1 5 ms 5 ms 4 ms sjc.onnet.us.uu.net [] 2 24 ms 24 ms 22 ms 207.251.160.187 3 25 ms 23 ms 27 ms 207.251.172.230 4 23 ms 23 ms 35 ms 0.so-1-0-0.HR1.PAO1.ALTER.NET [152.63.48.121] 5 24 ms 26 ms 26 ms 524.ATM3-0.XR1.PAO1.ALTER.NET [152.63.54.202] 6 25 ms 40 ms 24 ms 0.so-0-0-0.XL1.PAO1.ALTER.NET [152.63.54.73] 7 26 ms 23 ms 27 ms 0.so-7-0-0.XL1.SCL2.ALTER.NET [152.63.54.134] 8 28 ms 31 ms 26 ms 0.so-6-1-0.BR1.SCL2.ALTER.NET [152.63.48.13] 9 26 ms 24 ms 26 ms 204.255.173.42 10 26 ms 26 ms 26 ms so-1-2-0.bbr1.SanJose1.Level3.net [209.244.3.137 ] 11 99 ms 98 ms 101 ms so-0-1-0.mp1.Philadelphia1.Level3.net [64.159.0. 141] 12 100 ms 98 ms 98 ms ge-11-0.hsa1.Philadelphia1.Level3.net [64.159.0. 146] 13 100 ms 98 ms 99 ms 4.78.144.6 14 103 ms 105 ms 103 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.4 5] 15 105 ms 104 ms 106 ms scott.servernavigator.net [66.96.217.245] Trace complete. VPS From Defender Equinix in Ashburn, VA --- 66.96.217.245 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5041ms rtt min/avg/max/mdev = 9.956/10.285/10.643/0.241 ms, pipe 2 traceroute 66.96.217.245 traceroute to 66.96.217.245 (66.96.217.245), 30 hops max, 38 byte packets 1 unknown223.0.157.204.defenderhosting.com (204.157.0.223) 0.143 ms 0.134 ms 0.066 ms 2 blue1.ash.dvlabs.com (69.31.4.129) 0.655 ms 0.646 ms 0.656 ms 3 207.99.112.173 (207.99.112.173) 0.705 ms 0.673 ms 0.600 ms 4 ge6-14.colo02.ash01.pccwbtn.net (206.223.115.48) 2.636 ms 1.003 ms 0.756 ms 5 pos5-2.cr01.phl02.pccwbtn.net (63.218.30.45) 5.292 ms 5.257 ms 5.077 ms 6 hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net (63.218.31.6) 5.306 ms 5.378 ms 5.438 ms 7 ge-7-0-ctsi.rtr0.scra1.hostnoc.net (66.197.191.45) 12.480 ms 10.014 ms 9.780 ms 8 scott.servernavigator.net (66.96.217.245) 10.176 ms 10.224 ms 10.356 ms Seems the problem has been fixed.