Ping Plotter how-to

[Skuzzy]

There seems to be an issue with Verizon.  If you are seeing the error message stating you cannot connect to the "Game Manager", and you are certain your firewall is not blocking, AND you have reset your router, then we would like to see a Ping Plot from you.

Please post the text output or image of your scan in this thread.  Thank you.

[715]

I can ping .149 but neither .153 nor .154 respond.  No problem entering arenas though (last night anyway).

Bytes   Source   Seq   Time   Units
64   71.252.137.149   1   67.5   ms
64   71.252.137.149   2   68.1   ms
64   71.252.137.149   3   69.3   ms
64   71.252.137.149   4   68.1   ms
64   71.252.137.149   5   67.6   ms
64   71.252.137.149   6   67.7   ms
64   71.252.137.149   7   68.3   ms
64   71.252.137.149   8   69.2   ms
64   71.252.137.149   9   68.6   ms
64   71.252.137.149   10   68.9   ms
Time minimum:   67.50 ms
Time average:   68.25 ms
Time maximum:   69.30 ms
Packets transmitted:   10
Packets received:   10
Successful packets:   100%

Traceroute to 71.252.137.154:
Hop   Hostname   IP   Time 1
1   ubuntu.local   192.168.1.100   0.094
1   192.168.1.1   192.168.1.1   4.387
1   192.168.1.1   192.168.1.1   1.313
2   10.183.12.1   10.183.12.1   8.236
3   172.30.12.33   172.30.12.33   23.400
4   12.249.197.9   12.249.197.9   26.406
5   cr81.sj2ca.ip.att.net   12.122.110.110   29.706
6   cr1.sffca.ip.att.net   12.122.1.117   37.359
7   gar23.sffca.ip.att.net   12.122.114.5   30.187
9   vlan90.csw4.SanJose1.Level3.n et   4.69.152.254   97.030
10   ae-82-82.ebr2.SanJose1.Level3.net   4.69.153.25   101.658
11   ae-2-2.ebr2.SanJose5.Level3.net   4.69.148.141   98.212
12   ae-1-100.ebr2.SanJose5.Level3.net   4.69.148.110   96.717
13   ae-6-6.ebr2.LosAngeles1.Level3.net   4.69.148.201   99.779
14   ae-83-83.csw3.Dallas1.Level3.net   4.69.151.157   97.508
15   ae-93-93.csw4.Dallas1.Level3.net   4.69.151.169   97.350
16   ae-2-2.ebr1.Miami1.Level3.net   4.69.140.134   96.676
17   ae-1-51.edge2.Miami1.Level3.net   4.69.138.70   97.539
18   ae-1-51.edge2.Miami1.Level3.net   4.69.138.70   98.776
19   A-SUR-NET-I.edge2.Miami1.Level3.net   4.31.223.78   103.315
20   63.245.70.26   63.245.70.26   131.259
21   63.245.70.26   63.245.70.26   125.749
22   xe-0-1-0-h1-hfc02.flowja.com   72.252.25.179   142.215

I have no idea why it goes to Dallas then out to Miami to get lost.  The traceroute to .149 is much cleaner:

Hop   Hostname   IP   Time 1
1   ubuntu.local   192.168.1.100   0.093
1   192.168.1.1   192.168.1.1   2.016
1   192.168.1.1   192.168.1.1   1.271
2   10.183.12.1   10.183.12.1   8.522
3   172.30.12.33   172.30.12.33   21.528
4   12.249.197.9   12.249.197.9   25.966
5   cr81.sj2ca.ip.att.net   12.122.110.110   28.393
6   cr1.sffca.ip.att.net   12.122.1.117   29.299
7   12.122.114.53   12.122.114.53   27.214
8   att-gw.sj.alter.net   192.205.36.62   27.610
9   B100.DLLSTX-LCR-21.verizon-gni.net   130.81.199.59   68.837
11   static-71-252-137-149.dllstx.fios.verizon.net   71.252.137.149   69.686

[Skuzzy]

This looks like a bad route injection from an ISP in Jamaica.

They look like they are trying to claim our IP address as there own.

Not good.

[Skuzzy]

New game plan.

I need anyone and everyone to post up a trace route or Ping Plot to the following addresses.

71.252.137.149
71.252.137.151
71.252.137.153

Thank you for the help.

[715]

Here's .151:

Hop   Hostname   IP   Time 1
1   ubuntu.local   192.168.1.100   0.095
1   192.168.1.1   192.168.1.1   2.122
1   192.168.1.1   192.168.1.1   1.266
2   10.183.12.1   10.183.12.1   9.564
3   172.30.12.33   172.30.12.33   24.663
4   12.249.197.9   12.249.197.9   25.833
5   cr81.sj2ca.ip.att.net   12.122.110.110   29.143
6   cr1.sffca.ip.att.net   12.122.1.117   32.041
7   12.122.114.53   12.122.114.53   30.381
8   att-gw.sj.alter.net   192.205.36.62   26.792
9   P0-8-0-0.DLLSTX-LCR-21.verizon-gni.net   130.81.199.35   69.543
11   static-71-252-137-151.dllstx.fios.verizon.net   71.252.137.151   68.387

[FLS]

C:\>tracert 71.252.137.149

Tracing route to static-71-252-137-149.dllstx.fios.verizon.net [71.252.137.149]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms   [10.0.0.1]
  2    10 ms    10 ms    10 ms  bras7-l0.mrdnct.sbcglobal.net [204.60.4.43]
  3     8 ms     9 ms     8 ms  dist2-vlan60.mrdnct.sbcglobal.net [66.159.184.22
7]
  4    12 ms    11 ms    11 ms  12.83.97.130
  5    40 ms    39 ms    39 ms  gar13.cgcil.ip.att.net [12.122.132.121]
  6    36 ms    41 ms    36 ms  0.ae10.BR3.CHI13.ALTER.NET [204.255.168.165]
  7    59 ms    59 ms    59 ms  B200.DLLSTX-LCR-21.verizon-gni.net [130.81.162.1
53]
  8     *        *        *     Request timed out.
  9    60 ms    60 ms    60 ms  static-71-252-137-149.dllstx.fios.verizon.net [7
1.252.137.149]

Trace complete.

C:\>tracert 71.252.137.151

Tracing route to static-71-252-137-151.dllstx.fios.verizon.net [71.252.137.151]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms   [10.0.0.1]
  2    10 ms    10 ms    10 ms  bras7-l0.mrdnct.sbcglobal.net [204.60.4.43]
  3     *        9 ms     8 ms  dist1-vlan60.mrdnct.sbcglobal.net [66.159.184.22
6]
  4    10 ms    11 ms    12 ms  12.83.32.254
  5    35 ms    35 ms    36 ms  gar13.cgcil.ip.att.net [12.122.132.121]
  6    32 ms    32 ms    32 ms  0.ae10.BR3.CHI13.ALTER.NET [204.255.168.165]
  7    57 ms    56 ms    55 ms  P0-0-0-0.DLLSTX-LCR-21.verizon-gni.net [130.81.1
51.243]
  8     *        *        *     Request timed out.
  9    56 ms    56 ms    55 ms  static-71-252-137-151.dllstx.fios.verizon.net [7
1.252.137.151]

Trace complete.

C:\>tracert 71.252.137.153

Tracing route to static-71-252-137-153.dllstx.fios.verizon.net [71.252.137.153]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms   [10.0.0.1]
  2    10 ms    10 ms    10 ms  bras7-l0.mrdnct.sbcglobal.net [204.60.4.43]
  3     8 ms     8 ms     8 ms  dist2-vlan60.mrdnct.sbcglobal.net [66.159.184.22
7]
  4    11 ms    11 ms    11 ms  12.83.97.130
  5    40 ms    39 ms    39 ms  gar13.cgcil.ip.att.net [12.122.132.121]
  6    37 ms    36 ms    37 ms  0.ae10.BR3.CHI13.ALTER.NET [204.255.168.165]
  7    65 ms    60 ms    59 ms  P0-8-0-0.DLLSTX-LCR-22.verizon-gni.net [130.81.1
99.37]
  8     *        *        *     Request timed out.
  9    60 ms    60 ms    60 ms  static-71-252-137-153.dllstx.fios.verizon.net [7
1.252.137.153]

Trace complete.

[715]

Now .153 and .154 work.  Very weird. 

Hop   Hostname   IP   Time 1
1   ubuntu.local   192.168.1.100   0.092
1   192.168.1.1   192.168.1.1   4.309
1   192.168.1.1   192.168.1.1   1.276
2   10.183.12.1   10.183.12.1   8.979
3   172.30.12.33   172.30.12.33   21.858
4   12.249.197.9   12.249.197.9   24.687
5   cr81.sj2ca.ip.att.net   12.122.110.110   31.419
6   cr1.sffca.ip.att.net   12.122.1.117   32.274
7   12.122.114.53   12.122.114.53   28.589
8   att-gw.sj.alter.net   192.205.36.62   28.114
9   P0-0-0-0.DLLSTX-LCR-22.verizon-gni.net   130.81.151.245   68.041
11   static-71-252-137-153.dllstx.fios.verizon.net   71.252.137.153   70.026

Hop   Hostname   IP   Time 1
1   ubuntu.local   192.168.1.100   0.089
1   192.168.1.1   192.168.1.1   1.302
1   192.168.1.1   192.168.1.1   1.254
2   10.183.12.1   10.183.12.1   8.071
3   172.30.12.33   172.30.12.33   42.024
4   12.249.197.9   12.249.197.9   34.799
5   cr81.sj2ca.ip.att.net   12.122.110.110   29.662
6   cr1.sffca.ip.att.net   12.122.1.117   29.202
7   12.122.114.53   12.122.114.53   28.614
8   att-gw.sj.alter.net   192.205.36.62   27.681
9   B100.DLLSTX-LCR-21.verizon-gni.net   130.81.199.59   69.412
11   static-71-252-137-154.dllstx.fios.verizon.net   71.252.137.154   69.536

[Drane]

From space coast in Florida

[Drane]

It appears to get worse as PingPlotter runs longer.

[Schen]

same result on all 3 with 15-17 hops

ending and stoping at    

72.252.25.179 xe-0-1-0-h1-hfc02.flowja.com

[Skuzzy]

I called the ISP in Jamaica, but they support people would not allow me to talk to one of their networking engineers.  I managed to get an email address and have sent off an email detailing the problem.

Not sure if anything will come of it.  Hopefully, they will realize what they have done and correct it quickly.

[The Fugitive]

Here are mine.....

Target Name: static-71-252-137-149.dllstx.fios.verizon.net
         IP: 71.252.137.149
  Date/Time: 7/7/2014 4:45:15 PM to 7/7/2014 4:45:44 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    30   0   0.0  10  20  15  WRT610N [192.168.1.1]
 2    30   0   0.0  19  49  29  [10.241.112.1]
 3    30   0   0.0  19  40  29  dtr02sbdgma-tge-0-0-0-3.sbdg.ma.charter.com [96.34.84.158]
 4    30   0   0.0  19  49  29  crr03oxfrma-tge-0-1-0-1.oxfr.ma.charter.com [96.34.80.162]
 5    30   0   0.0  19  59  36  bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
 6    30   0   0.0  19  70  33  xe-5-0-3.bar2.Boston1.Level3.net [4.53.56.169]
 7    30   0   0.0  29  50  40  ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
 8    30   0   0.0  29  69  42  ae-47-47.ebr1.NewYork2.Level3.net [4.69.201.46]
 9    30  23  76.7  29  50  37  ae-1-51.ear1.NewYork2.Level3.net [4.69.138.201]
10    30   0   0.0  29  90  39  [208.51.134.134]
11    30   0   0.0  29  69  40  [64.215.195.34]
12    30   0   0.0  59  90  78  P0-0-0-0.DLLSTX-LCR-22.verizon-gni.net [130.81.151.245]
13    30  30 100.0   0   0   0   [-]
14    30   0   0.0  69  99  79  static-71-252-137-149.dllstx.fios.verizon.net [71.252.137.149]

Target Name: static-71-252-137-151.dllstx.fios.verizon.net
         IP: 71.252.137.151
  Date/Time: 7/7/2014 4:46:41 PM to 7/7/2014 4:47:10 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    30   0   0.0  15  31  27  WRT610N [192.168.1.1]
 2    30   0   0.0  31  62  47  [10.241.112.1]
 3    30   0   0.0  31  62  47  dtr02sbdgma-tge-0-0-0-3.sbdg.ma.charter.com [96.34.84.158]
 4    30   0   0.0  31  77  48  crr03oxfrma-tge-0-1-0-1.oxfr.ma.charter.com [96.34.80.162]
 5    30   0   0.0  31  78  48  bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
 6    30   0   0.0  30 124  54  xe-4-2-0.bar2.Boston1.Level3.net [4.53.56.129]
 7    30   0   0.0  31  77  52  ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
 8    30   0   0.0  31  77  53  ae-48-48.ebr1.NewYork2.Level3.net [4.69.201.50]
 9    28  19  67.9  31  62  51  ae-1-51.ear1.NewYork2.Level3.net [4.69.138.201]
10    30   0   0.0  31 124  53  [208.51.134.134]
11    30   0   0.0  31  62  47  [208.49.136.38]
12    30   0   0.0  77 109  94  P0-0-0-0.DLLSTX-LCR-21.verizon-gni.net [130.81.151.243]
13    30  30 100.0   0   0   0   [-]
14    30   0   0.0  77 109  97  static-71-252-137-151.dllstx.fios.verizon.net [71.252.137.151]

Target Name: static-71-252-137-153.dllstx.fios.verizon.net
         IP: 71.252.137.153
  Date/Time: 7/7/2014 4:47:49 PM to 7/7/2014 4:48:19 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    30   0   0.0  15  31  25  WRT610N [192.168.1.1]
 2    30   0   0.0  31  62  54  [10.241.112.1]
 3    30   0   0.0  31  62  53  dtr02sbdgma-tge-0-0-0-3.sbdg.ma.charter.com [96.34.84.158]
 4    30   0   0.0  31  77  52  crr03oxfrma-tge-0-1-0-1.oxfr.ma.charter.com [96.34.80.162]
 5    30   0   0.0  31  77  51  bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
 6    30   0   0.0  31 109  53  xe-4-2-0.bar2.Boston1.Level3.net [4.53.56.129]
 7    30   0   0.0  31  62  52  ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
 8    30   0   0.0  31  77  51  ae-48-48.ebr1.NewYork2.Level3.net [4.69.201.50]
 9    26  19  73.1  31  78  55  ae-1-51.ear1.NewYork2.Level3.net [4.69.138.201]
10    30   0   0.0  31  77  53  [208.51.134.134]
11    30   0   0.0  46  77  57  [64.215.195.34]
12    30   0   0.0  77 124  97  B100.DLLSTX-LCR-21.verizon-gni.net [130.81.199.59]
13    30  30 100.0   0   0   0   [-]
14    30   0   0.0  78 109  98  static-71-252-137-153.dllstx.fios.verizon.net [71.252.137.153]

[Skuzzy]

I am assuming all of you who have the same, or similar, traces for all three IP addresses, are also working just fine.

[Drane]

Have been able to connect to AH however the lost count for LW Arena cycles frequently from 0 to 1 while watching ping details.

[Skuzzy]

Have been able to connect to AH however the lost count for LW Arena cycles frequently from 0 to 1 while watching ping details.

That could happen at any router from you to the servers.  You would need to run Ping Plotter, for a few minutes, to capture where that is happening.