Packet Loss ISP or me?

Toggle sidebar Toggle sidebar
C

Corroborate

Reputable
Mar 17, 2014
35
0
4,540
Hi, guys I need help i did a traceroute and i got these results but i need someone to explain them to me.

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Fangblades>tracert google
Unable to resolve target system name google.

C:\Users\Fangblades>tracert 63.240.161.189

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 8 ms 8 ms cpe-76-168-240-1.socal.res.rr.com [76.168.240.1]

3 8 ms 9 ms 8 ms 76.167.30.169
4 14 ms 14 ms 14 ms agg22.lsaicaev02r.socal.rr.com [72.129.18.88]
5 14 ms 14 ms 14 ms 72.129.17.2
6 15 ms 15 ms 14 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
7 13 ms 14 ms 13 ms ae2.pr1.lax10.tbone.rr.com [107.14.19.54]
8 14 ms 13 ms 13 ms 216.156.65.225.ptr.us.xo.net [216.156.65.225]
9 13 ms 13 ms 15 ms 207.88.15.94.ptr.us.xo.net [207.88.15.94]
10 19 ms 18 ms 14 ms 205.158.79.242.ptr.us.xo.net [205.158.79.242]
11 65 ms 66 ms 66 ms cr1.la2ca.ip.att.net [12.122.128.102]
12 66 ms 62 ms 63 ms cr1.slkut.ip.att.net [12.122.30.29]
13 63 ms 66 ms 66 ms cr2.dvmco.ip.att.net [12.122.30.26]
14 72 ms 64 ms 65 ms cr1.cgcil.ip.att.net [12.122.31.86]
15 63 ms 67 ms 62 ms gar18.cgcil.ip.att.net [12.122.99.21]
16 224 ms 202 ms 203 ms 12.122.251.14
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 ^C
C:\Users\Fangblades>tracert 208.94.27.1

Tracing route to dal-r11-s6501.dal.triongames.com [208.94.27.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 7 ms cpe-76-168-240-1.socal.res.rr.com [76.168.240.1]

3 8 ms 8 ms 8 ms 76.167.30.169
4 12 ms 14 ms 14 ms agg22.lsaicaev02r.socal.rr.com [72.129.18.88]
5 12 ms 14 ms 14 ms 72.129.17.2
6 14 ms 14 ms 18 ms ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214]
7 14 ms 14 ms 14 ms bu-ether14.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.4]
8 13 ms 12 ms 13 ms 107.14.17.250
9 13 ms 12 ms 59 ms xe-0-3-2-0-pe01.onewilshire.ca.ibone.comcast.net
[173.167.59.45]
10 13 ms 14 ms 14 ms te-2-0-0-0-cr01.losangeles.ca.ibone.comcast.net
[68.86.82.33]
11 48 ms 50 ms 46 ms he-0-14-0-0-cr01.dallas.tx.ibone.comcast.net [68
.86.85.142]
12 47 ms 47 ms 48 ms be-14-pe02.1950stemmons.tx.ibone.comcast.net [68
.86.83.110]
13 47 ms 47 ms 47 ms dal-r11-s6501.dal.triongames.com [208.94.27.1]

Trace complete.

C:\Users\Fangblades>tracert 208.94.27.1

Tracing route to dal-r11-s6501.dal.triongames.com [208.94.27.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 12 ms cpe-76-168-240-1.socal.res.rr.com [76.168.240.1]

3 8 ms 10 ms 8 ms 76.167.30.169
4 12 ms 14 ms 14 ms agg22.lsaicaev02r.socal.rr.com [72.129.18.88]
5 13 ms 14 ms 14 ms 72.129.17.2
6 15 ms 15 ms 14 ms ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214]
7 16 ms 14 ms 14 ms bu-ether14.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.4]
8 * * 13 ms 107.14.17.250
9 24 ms 13 ms 13 ms xe-0-3-2-0-pe01.onewilshire.ca.ibone.comcast.net
[173.167.59.45]
10 17 ms 13 ms 16 ms te-2-0-0-0-cr01.losangeles.ca.ibone.comcast.net
[68.86.82.33]
11 49 ms 50 ms 51 ms he-0-14-0-0-cr01.dallas.tx.ibone.comcast.net [68
.86.85.142]
12 51 ms 48 ms 47 ms be-14-pe02.1950stemmons.tx.ibone.comcast.net [68
.86.83.110]
13 47 ms 47 ms 47 ms dal-r11-s6501.dal.triongames.com [208.94.27.1]

Trace complete.

C:\Users\Fangblades>tracert 95.172.65.76

Tracing route to 95.172.65.76 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 12 ms cpe-76-168-240-1.socal.res.rr.com [76.168.240.1]

3 8 ms 8 ms 8 ms 76.167.30.169
4 13 ms 15 ms 14 ms agg22.lsaicaev02r.socal.rr.com [72.129.18.88]
5 13 ms 14 ms 14 ms 72.129.17.2
6 17 ms 14 ms 14 ms 107.14.19.30
7 13 ms 13 ms 19 ms ae2.pr1.lax10.tbone.rr.com [107.14.19.54]
8 14 ms 14 ms 14 ms las-bb1-link.telia.net [62.115.36.57]
9 25 ms 14 ms 13 ms las-bb1-link.telia.net [62.115.140.8]
10 75 ms 75 ms 76 ms ash-bb3-link.telia.net [80.91.251.253]
11 177 ms 177 ms 175 ms ffm-bb1-link.telia.net [62.115.139.40]
12 176 ms 176 ms 173 ms ffm-b11-link.telia.net [213.155.134.85]
13 181 ms 182 ms 181 ms internap-ic-305857-ffm-b11.c.telia.net [62.115.4
1.206]
14 180 ms 180 ms 179 ms border1.po2-8g-bbnet2.fra002.pnap.net [95.172.67
.65]
15 182 ms 181 ms 181 ms 95.172.65.76

Trace complete.

C:\Users\Fangblades>ping 216.52.241.254

Pinging 216.52.241.254 with 32 bytes of data:
Reply from 216.52.241.254: bytes=32 time=127ms TTL=245
Reply from 216.52.241.254: bytes=32 time=22ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245

Ping statistics for 216.52.241.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 127ms, Average = 43ms

C:\Users\Fangblades>ping 216.52.241.254 -t

Pinging 216.52.241.254 with 32 bytes of data:
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=14ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=73ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=27ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=18ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=14ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=14ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=17ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=16ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=181ms TTL=245
Request timed out.
Reply from 216.52.241.254: bytes=32 time=15ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=13ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245
Reply from 216.52.241.254: bytes=32 time=12ms TTL=245

Ping statistics for 216.52.241.254:
Packets: Sent = 45, Received = 44, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 181ms, Average = 18ms
Control-C
^C
C:\Users\Fangblades>
 
Solution
P


25% is quite high and will definitely cause problems with gaming. You should ask them to send a tech out to take a look at the line
Sort by date Sort by votes
P

Pinhedd

Champion
Aug 7, 2007
10,342
20
56,965
Dropping packets is the internet's way of telling a sender to slow down a bit. A small amount of packet loss is perfectly normal, it's a flow control technique. High levels of packet loss may indicate either congestion or a high level of bit errors on the transmission medium.

Request timeouts on tracert do not automatically mean that the packets are being lost. Tracert uses carefully shaped ICMP packets (just like ping) to elicit a response. Many devices will not respond to ICMP requests by default to prevent discovery and/or flooding.
 
Upvote 0 Downvote
P

Pinhedd

Champion
Aug 7, 2007
10,342
20
56,965


There are many, many different things that could cause delays in gameplay. You're going to have to be a lot more specific and give us a lot more information.
 
Upvote 0 Downvote
C

Corroborate

Reputable
Mar 17, 2014
35
0
4,540
Kk what information do i need to know also i did call my ISP and said i had a 25% packet loss. I keep getting a random amount of packet loss its quite bothersome but what other information do i need to give?
 
Upvote 0 Downvote
P

Pinhedd

Champion
Aug 7, 2007
10,342
20
56,965


25% is quite high and will definitely cause problems with gaming. You should ask them to send a tech out to take a look at the line
 
Upvote 0 Downvote
Solution
W

wsmierciak

Reputable
Aug 7, 2014
1
0
4,510
You can try one other option before the tech gets there.

if you have a cable/dsl modem and a SEPERATE Router go to Step 1. If you do not have a SEPERATE Router, go to Step 3.
Step 1.
You will do this test FIRST with your Router connected between your PC and your Cable/DSL modem. Once you've finished move to Step 2.

Step 2.
For a full test to esnure it's not your aftermarket router, Power off your Cable/DSL modem, remove the router and plug the Modem directly into your computer (no router in between) and follow the same test again. See if the packet loss is the same with your router and without your router.
If you only have a Cable/DSL Modem and Router all in one piece...then you don't need to unplug anything. just follow this test below once.

Step 3.
On your computer do a tracert to www.google.com from a DOS window.
You'll see a window full of IP Addresses that equates to every single hop your internet traffic takes to go from your router to google.com.

Start at the top and ping each IP address with a " -T " (no quotes) on each ip for 30-60 seconds.
After your time for each has passed, press Control+C and view the results. During the ping you'll see each line moving up the window. If you see any lines that do not show a reply, those could be packet loss. But ALSO make note of the time=#ms. That # shouldn't be too high depending on where you are pinging. if you see anything over 100ms you'll start to have latency issues depending on what you're doing (streaming/gaming/vonage phone/skype)

Follow that step through each IP Address you have from the top down. Make note of each IP and the Packet Loss % in the results after you press Control+C. The hop that has the worst packet loss is one of the points that your ISP will need to know about, unless your packet loss starts on your internal network (192.168.x.x).

You can go through each of these lines over a 10-15 minute timeframe plus note taking.
Do this at different times of the day over a few days and see if you get some of the trends. (people getting off at 5, home and surfing/streaming after 6 is common, making DSL feel slower than normal).

Hope this helps and maybe helps you save some money if your packet loss is at your router.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom