High Latency when routed through Cogent Communications

Support Technical Support
48 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.1.0.1 -   14 | 1469 | 1264 |    0 |    0 |   12 |    0 |
|                             10.181.50.1 -    0 | 2286 | 2286 |    3 |   11 |   51 |   14 |
|                             172.30.70.1 -    0 | 2286 | 2286 |   12 |   20 |   82 |   25 |
|            68-66-73-22.client.mchsi.com -    0 | 2286 | 2286 |   33 |   40 |   82 |   48 |
|              po13.chgil001cr1.mchsi.com -    0 | 2286 | 2286 |   32 |   40 |   85 |   48 |
|              po10.chgil001er1.mchsi.com -    0 | 2286 | 2286 |   32 |   41 |   98 |   42 |
|                          137.221.66.164 -    0 | 2286 | 2286 |   33 |   45 |  361 |   48 |
|              ae1-br01-eqch2.as57976.net -    0 | 2265 | 2265 |   32 |   75 | 3959 |   38 |
|              be1-pe02-eqch2.as57976.net -    0 | 2286 | 2286 |   33 |   41 |  106 |   42 |
|        chi-eqch2-ia-bons-04.as57976.net -    0 | 2286 | 2286 |   33 |   39 |  104 |   39 |
|                           24.105.62.129 -    0 | 2286 | 2286 |   31 |   39 |  109 |   38 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

and 

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.1.0.1 -   17 | 1232 | 1026 |    0 |    0 |   10 |    0 |
|                             10.181.50.1 -    0 | 2052 | 2052 |    2 |   10 |   25 |    7 |
|                             172.30.68.1 -    0 | 2052 | 2052 |   14 |   23 |   60 |   23 |
|            68-66-73-22.client.mch si.com -    0 | 2052 | 2052 |   34 |   43 |   63 |   46 |
|              po13.chgil001cr1.mchsi.com -    0 | 2052 | 2052 |   35 |   43 |   90 |   45 |
|              po10.chgil001er1.mchsi.com -    0 | 2052 | 2052 |   35 |   43 |   73 |   39 |
|                          137.221.66.164 -    0 | 2052 | 2052 |   35 |   47 |  278 |   40 |
|              ae1-br01-eqch2.as57976.net -    0 | 2031 | 2031 |   73 |  119 | 3959 |   79 |
|                          137.221.65.132 -    1 | 2008 | 2002 |   67 |  105 | 4398 |   73 |
|       et-0-0-31-pe02-swlv10.as57976.net -    0 | 2052 | 2052 |   72 |   83 |  222 |   77 |
|                           137.221.105.2 -    0 | 2052 | 2052 |   71 |   77 |   99 |   75 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
49

I think i did this right, heres my test. please help.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.100.1 - 0 278 278 0 1 38 3
10.5.168.1 - 0 278 278 7 50 205 24
10.2.109.1 - 0 278 278 7 52 317 30
10.2.125.1 - 1 274 273 9 76 779 21
10.9.249.1 - 1 274 273 13 75 779 21
10.2.155.1 - 0 278 278 9 76 763 32
10.2.154.1 - 0 278 278 10 74 779 26
10.11.92.1 - 0 278 278 9 75 779 26
10.11.201.1 - 0 278 278 11 81 809 33
10.10.45.1 - 0 278 278 11 79 749 38
192.168.1.125 - 11 198 178 9 185 1103 76
192.168.1.125 - 17 167 140 13 216 1100 76
198-204-208-1.static.chico.ca.digitalpath net - 13 182 160 635 976 2562 1205
50-227-217-129-static.hfc.comcastbusiness net - 1 273 272 14 230 1205 360
ae-11-rur01.chico.ca.ccal.comcast net - 0 276 276 14 234 1561 361
ae-5-ar01.sacramento.ca.ccal.comcast net - 1 273 272 21 228 1206 396
be-33667-cr01.9greatoaks.ca.ibone.comcast net - 0 276 276 23 239 1561 183
be-12578-pe04.9greatoaks.ca.ibone.comcast net - 0 276 276 18 237 1561 414
as852.seattle.wa.ibone.comcast net - 1 273 272 22 242 1332 209
108.170.243.1 - 0 276 276 22 242 1561 426
108.170.236.63 - 0 276 276 19 239 1561 414
sfo03s07-in-f110.1e100 net - 0 276 276 24 241 1561 414
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

50

Si this is happening since what? 2 weeks now? And there is no blue answer? Si, we calle the ISP and they can’t do anything, Blizzard can’t do anything, and we can’t contact the middle men cause we don’t have a contract with them… We are done.

51

Going to bump this considering its been over 2 weeks now with no fix, and finally people are realizing its not a problem with anyone’s ISP. It’s clearly a very widespread problem now, whether it be caused by the awful routing from NTT, or Cogent.

54

Update: 7/18/19 I just got off the phone with digital path. They said they have been working with cogen trying to figure it out but its out of both of their hands. That it is on blizzards end so yet again I been lead on a loop. Blizzard please fix this you guys make it nearly impossible to play last 2-3 weeks now. We paid for out time yet we are being denied service. I myself am not a big fan of using lemon as eye drops kinda like how i dont like playing 280 ms where everything is painful.

55

I get a better ping to Europe than Central US… when I live in Central US.

Amazing.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
router.asus.c - 0 106 106 1 1 4 1
No response from host - 100 21 0 0 0 0 0
64-126-3-37.static.everestkc.n - 0 106 106 8 12 59 10
ibr34-te-0-2-0.mci.surewest.c - 0 106 106 8 12 60 12
be4163.ccr21.mci01.atlas.cogentco.c - 0 106 106 36 40 80 38
be2831.ccr41.ord01.atlas.cogentco.c - 0 106 106 24 28 68 28
be2717.ccr21.cle04.atlas.cogentco.c - 0 106 106 31 35 72 33
be2878.ccr21.alb02.atlas.cogentco.c- 0 106 106 45 49 82 47
be3599.ccr31.bos01.atlas.cogentco.c - 0 106 106 45 49 82 49
be2099.ccr41.lon13.atlas.cogentco.c - 0 106 106 110 115 272 113
be3487.ccr51.lhr01.atlas.cogentco.c - 0 106 106 109 115 268 112
be3671.agr21.lhr01.atlas.cogentco.c - 0 106 106 110 115 272 112
gi0-0-1-15.nr11.b020862-1.lhr01.atlas.cogentco.c - 0 106 106 110 120 269 113
ae1-br01-eqld5.as57976.n - 0 106 106 113 122 270 116
et-0-0-2-br02-eqam1.as57976.n - 0 106 106 118 128 270 148
et-0-0-67-pe01-eqam1.as57976.n - 0 106 106 117 128 275 125
137.221.66.43 - 0 106 106 122 127 278 124
185.60.112.157 - 0 106 106 118 124 270 119
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

no PL, and 120 ping. Should I just play on Europe going forward?

56

Another update. I noticed that the NTT routing issue was fixed for some people by rerouting them through Cogent nodes. Is there a reason that a lot of us on the West Coast are still seeing the same bad routing from Cogent to Blizzard servers?

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 50 50 0 0 1 0
192.168.100.1 0 50 50 1 1 5 2
chico-ticore.digitalpath.net 0 50 50 28 33 45 30
198-204-208-1.static.chico.ca.digitalpath.net 13 32 28 775 1070 1183 1120
te0-0-2-1.nr12.b015947-1.smf01.atlas.cogentco.com 0 50 50 34 39 56 38
te0-2-1-3.rcr21.smf01.atlas.cogentco.com 0 50 50 35 39 54 45
be3107.ccr22.sfo01.atlas.cogentco.com 0 50 50 34 41 55 40
be3670.ccr41.sjc03.atlas.cogentco.com 0 50 50 39 43 57 50
38.88.224.5 0 50 50 38 45 87 42
ae1-br01-eqsv5.as57976.net 0 50 50 263 271 367 269
et-0-0-3-br01-eqch2.as57976.net 0 50 50 83 93 196 151
be1-pe02-eqch2.as57976.net 3 46 45 272 275 285 273
chi-eqch2-ia-bons-04.as57976.net 0 50 50 270 275 287 275
24.105.62.129 0 50 50 259 263 283 261
57

I am still having the same issues. my MTR looks the same as my last post still. i jsut have less packet loss cause they reset my tower. it was acting up. but still have 240-800 ms ping in game

58

I posted this in another thread before seeing this one. Copy/Paste from the other thread I did.

This doesn’t show what happened to me earlier before this BG I just did. In a previous BG, you had me routed to a IP in the Netherlands…no idea how or why but on this current BG I just did. I had little to no lag.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.254 1 1166 1165 0 0 1 0
My IP 0 1169 1169 0 3 22 4
99.173.76.206 0 1169 1169 1 25 792 1
cr1.rlgnc.ip.att. net 0 1169 1169 10 14 19 13
cr1.attga.ip.att. net 0 1169 1169 10 13 19 14
gar18.attga.ip.att. net 0 1169 1169 10 10 12 10
12.247.68.74 0 1169 1169 10 14 84 11
ae1-br01-eqat2.as57976. net 0 1169 1169 29 31 127 125
et-0-0-4-br02-eqch2.as57976. net 0 1169 1169 29 32 325 29
be2-pe01-eqch2.as57976. net 0 1169 1169 29 29 32 29
chi-eqch2-ia-bons-02.as57976. net 0 1169 1169 30 31 43 31
24.105.62.129 0 1169 1169 30 30 34 30

The BIG Blip you see was me logging into WoW and my character loading. Game always freezes, after that I ran it for a good long time and for a major portion of the BG before I got DC’d from random lag during the BG.

Adding Blizzard’s Through the Looking Glass so they can see the problem is indeed on their end. Seeing bad lag at a blizzard owned server: 137.221.65.68.

TRACEROUTE:
traceroute to 107.140.242.220 (107.140.242.220), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.850 ms 0.837 ms 0.824 ms
2 24.105.18.3 (24.105.18.3) 0.977 ms 1.509 ms 1.537 ms
3 137.221.105.16 (137.221.105.16) 0.932 ms 0.965 ms 1.508 ms
4 137.221.66.22 (137.221.66.22) 1.521 ms 1.697 ms 1.710 ms
5 137.221.83.68 (137.221.83.68) 30.731 ms 30.944 ms 30.982 ms
6 137.221.65.68 (137.221.65.68) 57.088 ms 275.095 ms 275.093 ms
7 137.221.68.32 (137.221.68.32) 7.695 ms 7.683 ms 7.265 ms
8 12.245.64.9 (12.245.64.9) 7.211 ms 7.204 ms 7.205 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 99.173.76.207 (99.173.76.207) 55.702 ms 55.578 ms 55.676 ms
15 * * *

21/07/2019 12:41:02 UTC

TRACEROUTE:
traceroute to 107.140.242.220 (107.140.242.220), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.361 ms 0.377 ms 0.381 ms
2 24.105.18.3 (24.105.18.3) 1.762 ms 1.792 ms 1.810 ms
3 137.221.105.16 (137.221.105.16) 1.770 ms 1.788 ms 1.805 ms
4 137.221.66.22 (137.221.66.22) 1.820 ms 1.826 ms 1.831 ms
5 137.221.83.68 (137.221.83.68) 58.799 ms 58.807 ms 58.815 ms
6 137.221.65.68 (137.221.65.68) 472.214 ms 469.851 ms 469.824 ms
7 137.221.68.32 (137.221.68.32) 6.048 ms 6.068 ms 6.075 ms
8 12.245.64.9 (12.245.64.9) 5.907 ms 6.064 ms 5.868 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 99.173.76.207 (99.173.76.207) 55.576 ms 55.574 ms 55.452 ms
15 * * *

21/07/2019 12:41:02 UTC

TRACEROUTE:
traceroute to 107.140.242.220 (107.140.242.220), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.372 ms 0.378 ms 0.387 ms
2 24.105.18.3 (24.105.18.3) 4.771 ms 4.794 ms 4.827 ms
3 137.221.105.16 (137.221.105.16) 4.757 ms 4.773 ms 4.806 ms
4 137.221.66.22 (137.221.66.22) 4.811 ms 4.801 ms 4.805 ms
5 137.221.83.68 (137.221.83.68) 18.920 ms 18.926 ms 18.933 ms
6 137.221.65.68 (137.221.65.68) 265.059 ms 260.117 ms 260.095 ms
7 137.221.68.32 (137.221.68.32) 9.408 ms 7.808 ms 8.180 ms
8 12.245.64.9 (12.245.64.9) 7.731 ms 8.173 ms 7.971 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 99.173.76.207 (99.173.76.207) 55.589 ms 55.609 ms 55.664 ms
15 * * *

21/07/2019 12:41:02 UTC

TRACEROUTE:
traceroute to 107.140.242.220 (107.140.242.220), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.279 ms 0.276 ms 0.280 ms
2 24.105.18.3 (24.105.18.3) 1.029 ms 1.040 ms 1.055 ms
3 137.221.105.16 (137.221.105.16) 0.990 ms 1.017 ms 1.029 ms
4 137.221.66.22 (137.221.66.22) 1.043 ms 1.046 ms 1.049 ms
5 137.221.83.68 (137.221.83.68) 5.937 ms 5.957 ms 5.961 ms
6 137.221.65.68 (137.221.65.68) 6.594 ms 6.070 ms 6.060 ms
7 137.221.68.32 (137.221.68.32) 6.212 ms 6.213 ms 6.152 ms
8 12.245.64.9 (12.245.64.9) 5.845 ms 5.855 ms 5.855 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 99.173.76.207 (99.173.76.207) 57.490 ms 56.991 ms 63.683 ms
15 * * *

21/07/2019 12:41:07 UTC

MTR:
Start: Sun Jul 21 12:41:02 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 1.7 0.3 13.8 4.2
2.|-- 24.105.18.3 0.0% 10 0.7 1.8 0.5 11.2 3.2
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 1.1 2.7 0.8 17.3 5.1
5.|-- 137.221.83.68 0.0% 10 5.9 6.6 5.8 13.1 2.2
6.|-- 137.221.65.68 0.0% 10 5.8 40.0 5.7 203.4 64.4
7.|-- 137.221.68.32 0.0% 10 54.2 11.0 5.8 54.2 15.2
8.|-- 12.245.64.9 0.0% 10 5.8 6.5 5.7 12.5 2.1
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 99.173.76.207 0.0% 10 55.7 55.7 55.6 55.9 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/07/2019 12:41:02 UTC

MTR:
Start: Sun Jul 21 12:41:03 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.6 0.0
2.|-- 24.105.18.3 0.0% 10 2.0 1.9 0.6 5.2 1.2
3.|-- 137.221.105.16 0.0% 10 0.9 0.7 0.5 1.2 0.0
4.|-- 137.221.66.22 0.0% 10 1.3 6.3 1.0 33.8 11.2
5.|-- 137.221.83.68 0.0% 10 6.0 5.9 5.7 6.1 0.0
6.|-- 137.221.65.68 0.0% 10 6.8 96.2 5.8 473.1 154.2
7.|-- 137.221.68.32 0.0% 10 6.2 6.6 5.9 9.0 0.7
8.|-- 12.245.64.9 0.0% 10 6.0 6.0 5.6 6.3 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 99.173.76.207 0.0% 10 55.9 55.7 55.4 56.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/07/2019 12:41:02 UTC

MTR:
Start: Sun Jul 21 12:41:03 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.3 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 2.0 1.3 0.5 3.0 0.7
3.|-- 137.221.105.16 0.0% 10 0.9 0.7 0.5 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 1.3 6.8 1.0 38.6 12.6
5.|-- 137.221.83.68 0.0% 10 6.1 5.9 5.8 6.3 0.0
6.|-- 137.221.65.68 0.0% 10 6.8 94.9 5.6 473.1 155.4
7.|-- 137.221.68.32 0.0% 10 6.2 6.1 5.9 6.8 0.0
8.|-- 12.245.64.9 0.0% 10 5.9 5.9 5.7 6.3 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 99.173.76.207 0.0% 10 56.0 55.7 55.4 56.1 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/07/2019 12:41:02 UTC

MTR:
Start: Sun Jul 21 12:41:07 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 2.0 0.8 0.5 2.0 0.3
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 1.2 8.0 0.9 61.3 18.9
5.|-- 137.221.83.68 0.0% 10 6.0 8.9 5.7 35.0 9.2
6.|-- 137.221.65.68 0.0% 10 143.0 80.3 5.7 406.2 125.0
7.|-- 137.221.68.32 0.0% 10 7.3 6.2 5.9 7.3 0.3
8.|-- 12.245.64.9 0.0% 10 6.0 6.0 5.8 6.2 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- gar8.rlgnc.ip.att. net 80.0% 10 55.0 54.9 54.7 55.0 0.0
14.|-- 99.173.76.207 0.0% 10 55.7 55.8 55.6 56.5 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/07/2019 12:41:07 UTC

59

I am over here losing my mind over this. For weeks Blizzard games have been borderline unplayable. Fine ping everywhere else, massive lag spikes in Diablo/Overwatch. I am about to just completely give up playing.

pastebin/Fx9Py9WS for my looking glass paste. Level3 is the problem.

My ping is actually lower in the EU server lol… 400 ping in USA, 130 in EU. Sad.

60

Ya I’ve kind of lost hope in them every fixing the routing to the server. There is no reason I should have a lower latency to OCE servers playing from california than I do to a server in my own state.

61

Also having high latency through Cogent although I saw another post regarding Cox Communications (my ISP) which seemed more accurate to my issue. I made my own post in case its a different issue.

Cox High Latency

62

any news on if they’re going to be fixing this issue???

1 Like
63

Hi Kolthis

I haven’t seen anything that could be attributed to a specific ISP in the past week or more. I would start your own troubleshooting thread. Detail what is occurring - what you see on the in game latency meters. Then run a WinMTR test. Paste the results on your new thread.

The instructions are on this Blizzard Support page:

Once you have the tool open enter the IP number for the server group you play on in the WinMTR box then hit start.

24.105.62.129

(include periods)

Leave it run for 5 minutes or so. Doesn’t matter if you are playing or not. Then use the button that copies Text to your clipboard. Paste that on your thread here.

*You may need to alter or remove any URL addresses to paste on forum. You could also place the test results in a code block:

Open chat box - paste test then right click - “select all”. Should highlight everything. Then press the preformatted text button along top of chat box. Looks like this </>.

64

Hello is this the same issue as everyone else, I having big lag spikes every 30seconds to a minute.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
hitronhub.home 100 119 1 5 5 5 5
99.240.154.1 1 591 590 9 18 110 12
8078-dgw02.ym.rmgt.net.rogers.com 0 594 594 8 17 72 12
3000-dgw01.ym.rmgt.net.rogers.com 1 591 590 8 17 80 13
3033-cgw01.ym.rmgt.net.rogers.com 1 591 590 8 17 72 12
209.148.235.93 2 551 540 21 26 89 31
eqix-ix-ch1.blizzard.com 0 594 594 20 33 354 80
ae1-br01-eqch2.as57976.net 1 544 539 20 158 4378 207
be1-pe02-eqch2.as57976.net 0 594 594 18 28 82 27
chi-eqch2-ia-bons-04.as57976.net 0 594 594 20 27 92 24
24.105.62.129 0 594 594 17 28 83 22
65

But this thread is about being routed through Cogent, which you are not.

Please start your own thread.

66

The Cogent issue is still alive and going strong for over a month now. So annoying.

67

Hey all,

While we understand that this problem is frustrating, we do not control that part of the internet. While in some cases we can make slight modifications to our advertised routing to help with things such as this, it depends on what peers are available and whether or not we get enough information to open such an escalation.

Your best bet still remains contacting your ISP to inform them of the problem if you are routing through this area, as it is not in our network.

Keep in mind that many players can use VPN clients to work around ISP issues like this. This typically lets you use a different backbone provider, giving you overall lower latency. You’d need to look up what a VPN is online and how to set one up to test this, as we do not support them directly.

68

im not going to start a new thread when the issue still is with being routed through cogent, i just want this to stop its been months!! i just want to play without lagg!!
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.100.1 - 0 399 399 0 1 5 0
10.5.168.1 - 0 399 399 5 47 275 11
10.2.109.1 - 1 388 385 5 48 273 27
10.2.125.1 - 0 399 399 8 51 272 21
10.9.249.1 - 0 399 399 8 50 273 16
10.2.155.1 - 0 399 399 8 53 272 17
10.2.154.1 - 0 399 399 9 55 275 32
10.11.92.1 - 0 399 399 9 50 271 12
10.11.201.1 - 1 395 394 10 58 252 64
10.10.45.1 - 0 399 399 9 54 275 20
192.168.1.125 - 15 252 215 9 53 199 17
192.168.1.125 - 15 256 220 9 51 187 15
198-204-208-1.static.chico.ca.digitalpathnet - 37 137 87 1435 1782 2170 1891
te0-0-2-1.nr12.b015947-1.smf01.atlas.cogentcocom - 0 399 399 14 61 286 25
te0-0-0-2.rcr21.smf01.atlas.cogentcocom - 0 399 399 16 60 288 25
be3107.ccr22.sfo01.atlas.cogentcocom - 0 399 399 17 62 288 35
be3670.ccr41.sjc03.atlas.cogentcocom - 1 388 385 20 64 239 55
38.88.224.5 - 0 399 399 21 63 286 31
ae1-br01-eqsv5.as57976net - 1 391 389 250 296 513 300
et-0-0-3-br01-eqch2.as57976net - 0 399 399 65 114 301 73
be1-pe01-eqch2.as57976net - 0 399 399 253 292 523 265
24.105.62.129 - 1 395 394 239 285 508 272
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

69

“I haven’t seen anything that could be attributed to a specific ISP in the past week or more. I would start your own troubleshooting thread.”

^this has got to be the funniest thing I’ve ever read. Read my post Cogent is affecting so many of us. Nastylite and I are just two of the very few people that were willing to make a post.