Quantcast
Channel: Basic Internet Connectivity And Modem Help topics
Viewing all articles
Browse latest Browse all 12065

Packet loss while playing games.

$
0
0

For the past week, I have noticed random lag while playing Diablo 3.  I followed the instructions listed (https://us.battle.net/support/en/article/running-a-pathping-test) and by results are below.

 

Tracing route to 12.129.209.68 over a maximum of 30 hops

  0  Stephanie-MSI [10.0.0.10]
  1  10.0.0.1
  2  172.16.12.1
  3  24.4.208.1
  4  te-0-7-0-9-sur03.hayward.ca.sfba.comcast.net [68.85.100.137]
  5  te-9-3-ur02.hayward.ca.sfba.comcast.net [68.87.194.98]
  6  te-0-2-0-0-cr01.chicago.il.ibone.comcast.net [68.86.91.121]
  7  pos-0-3-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.87.18]
  8  192.205.37.1
  9  cr1.sffca.ip.att.net [12.122.86.198]
 10  cr1.la2ca.ip.att.net [12.122.3.122]
 11  gar5.lsrca.ip.att.net [12.122.85.33]
 12  12-122-254-230.attens.net [12.122.254.230]
 13  mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
 14  paxonix-placeholder.lax1.attens.net [12.129.248.118]
 15  12.129.209.68

Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Stephanie-MSI [10.0.0.10]
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  10.0.0.1
                                0/ 100 =  0%   |
  2    1ms     0/ 100 =  0%     0/ 100 =  0%  172.16.12.1
                                0/ 100 =  0%   |
  3   58ms     0/ 100 =  0%     0/ 100 =  0%  24.4.208.1
                                1/ 100 =  1%   |
  4   45ms     2/ 100 =  2%     1/ 100 =  1%  te-0-7-0-9-sur03.hayward.ca.sfba.comcast.net [68.85.100.137]
                                0/ 100 =  0%   |
  5   39ms     3/ 100 =  3%     2/ 100 =  2%  te-9-3-ur02.hayward.ca.sfba.comcast.net [68.87.194.98]
                                0/ 100 =  0%   |
  6   53ms     2/ 100 =  2%     1/ 100 =  1%  te-0-2-0-0-cr01.chicago.il.ibone.comcast.net [68.86.91.121]
                                0/ 100 =  0%   |
  7   47ms     3/ 100 =  3%     2/ 100 =  2%  pos-0-3-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.87.18]
                                0/ 100 =  0%   |
  8  106ms     2/ 100 =  2%     1/ 100 =  1%  192.205.37.1
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%    99/ 100 = 99%  cr1.sffca.ip.att.net [12.122.86.198]
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%    99/ 100 = 99%  cr1.la2ca.ip.att.net [12.122.3.122]
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%    99/ 100 = 99%  gar5.lsrca.ip.att.net [12.122.85.33]
                                0/ 100 =  0%   |
 12  ---     100/ 100 =100%    99/ 100 = 99%  12-122-254-230.attens.net [12.122.254.230]
                                0/ 100 =  0%   |
 13  ---     100/ 100 =100%    99/ 100 = 99%  mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
                                0/ 100 =  0%   |
 14  ---     100/ 100 =100%    99/ 100 = 99%  paxonix-placeholder.lax1.attens.net [12.129.248.118]
                                0/ 100 =  0%   |
 15  100ms     1/ 100 =  1%     0/ 100 =  0%  12.129.209.68

Trace complete.

 

Any idea how fix the problem?


Viewing all articles
Browse latest Browse all 12065

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>