Jump to content
  • Sign Up

Help interpreting diagnostic


Recommended Posts

So I ran the GW2 diagnostic because I'm regularly, especially on Sunday, unable to stay connected for a long period of time. 20-30 minutes in, sometimes less, lag, drop, my internet connection craps out for the whole apartment. My isp is sending a tech, which undoubtedly wont change anything. Can anyone tell me what this means? I would like to be able to tell the isp something, I clipped the part that seemed bad:

 

10 38ms 4/ 50 = 8% 4/ 50 = 8% bu-ether12.chcgildt87w-bcr00.tbone.rr.com [66.109.6.25]

0/ 50 = 0% |

11 37ms 0/ 50 = 0% 0/ 50 = 0% 66.109.5.225

50/ 50 =100% |

12 --- 50/ 50 =100% 0/ 50 = 0% 52.95.219.76

 

Another run

 

10 41ms 11/ 50 = 22% 7/ 50 = 14% bu-ether12.chcgildt87w-bcr00.tbone.rr.com [66.109.6.25]

0/ 50 = 0% |

11 39ms 4/ 50 = 8% 0/ 50 = 0% 66.109.5.225

46/ 50 = 92% |

12 --- 50/ 50 =100% 0/ 50 = 0% 52.95.219.76

 

If I'm reading that right is a ton of packet loss on that server?

Link to comment
Share on other sites

Run again after playing 1 pvp match, and disconnecting...

 

Tracing route to server-52-84-13-78.ord54.r.cloudfront.net [52.84.13.78]

over a maximum of 30 hops:

0 DesktopMain [192.168.1.2]

1 192.168.1.1

2 142.254.157.129

3 * ae63.bathoh0601h.midwest.rr.com [24.164.114.17]

4 be21.sgvlohaj01r.midwest.rr.com [24.33.103.76]

5 be11.clevohek02r.midwest.rr.com [65.29.1.97]

6 be25.clevohek01r.midwest.rr.com [65.29.1.32]

7 bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]

8 bu-ether12.nwrknjmd67w-bcr00.tbone.rr.com [66.109.6.29]

9 66.109.5.138

10 bu-ether12.chcgildt87w-bcr00.tbone.rr.com [66.109.6.25]

11 66.109.5.225

12 52.95.219.76

13 * * *

Computing statistics for 150 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 DesktopMain [192.168.1.2]

0/ 50 = 0% |

1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1

0/ 50 = 0% |

2 8ms 0/ 50 = 0% 0/ 50 = 0% 142.254.157.129

0/ 50 = 0% |

3 15ms 0/ 50 = 0% 0/ 50 = 0% ae63.bathoh0601h.midwest.rr.com [24.164.114.17]

0/ 50 = 0% |

4 9ms 0/ 50 = 0% 0/ 50 = 0% be21.sgvlohaj01r.midwest.rr.com [24.33.103.76]

0/ 50 = 0% |

5 13ms 0/ 50 = 0% 0/ 50 = 0% be11.clevohek02r.midwest.rr.com [65.29.1.97]

0/ 50 = 0% |

6 11ms 1/ 50 = 2% 1/ 50 = 2% be25.clevohek01r.midwest.rr.com [65.29.1.32]

0/ 50 = 0% |

7 35ms 0/ 50 = 0% 0/ 50 = 0% bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]

0/ 50 = 0% |

8 39ms 12/ 50 = 24% 12/ 50 = 24% bu-ether12.nwrknjmd67w-bcr00.tbone.rr.com [66.109.6.29]

0/ 50 = 0% |

9 40ms 0/ 50 = 0% 0/ 50 = 0% 66.109.5.138

0/ 50 = 0% |

10 37ms 13/ 50 = 26% 13/ 50 = 26% bu-ether12.chcgildt87w-bcr00.tbone.rr.com [66.109.6.25]

0/ 50 = 0% |

11 41ms 0/ 50 = 0% 0/ 50 = 0% 66.109.5.225

50/ 50 =100% |

12 --- 50/ 50 =100% 0/ 50 = 0% 52.95.219.76

 

Trace complete.

Section completed in 199.64 seconds

Link to comment
Share on other sites

Estimated packet loss is the in-between lines ending with |. The problem with pathping is that it's not compatible with nodes that do not respond to pings and will simply stop when it encounters one. Most of Amazon's network doesn't respond to pings, which is why your trace ends like that. You need to use PingPlotter to see the full trace, though the end will always show a high packet loss since it won't respond and thus can't be measured.

 

> @"Anat.1765" said:

> my internet connection craps out for the whole apartment

 

If you actually lose your internet connection on all devices, it's a problem with the modem or ISP. If your local network goes down, it's a problem with the router.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...