High latency/disconnections - Canadian East Coast

Support Technical Support
81

fix your game blizz…

82

I’m also with Bell Canada (East) and having the same lag issue. One moment it’s stable as it’s always been at around 30ms~ and the next it jumps all the way up to 200/300ms~ rendering the game virtually unplayable.

I’ve already contacted Blizzard about this and was assured that they were currently looking into this and investigating the issue.

Hopefully something is done real soon 'cos … I can’t see myself playing much longer when half the time I’m restricted to just roam about due to lag.

83

Doing a bit more troubleshooting on my end, not sure how much of this is helpful.

When the latency is high, here’s my path to Blizzard:

PS C:\> TRACERT.EXE 24.105.62.129

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms     2 ms  172.19.20.1
  2     2 ms     1 ms     2 ms  10.11.5.121
  3     *        *        *     Request timed out.
  4     2 ms     2 ms     2 ms  10.178.206.73
  5     8 ms     6 ms     6 ms  tcore3-toronto12_2-4-0-0.net.bell.ca [64.230.104.162]
  6    11 ms     6 ms     6 ms  tcore4-toronto01_0-1-0-1.net.bell.ca [64.230.50.236]
  7     2 ms     3 ms     2 ms  bx2-toronto01_et7-1-0.net.bell.ca [64.230.109.143]
  8    16 ms    15 ms    15 ms  ae55.bar2.Toronto1.Level3.net [4.28.138.45]
  9     *        *       17 ms  4.69.216.226
 10    21 ms    22 ms    22 ms  blizzard-en.ear1.newyork5.level3.net [4.35.72.34]
 11   270 ms   258 ms   258 ms  ae1-br01-eqny8.as57976.net [137.221.71.33]
 12   269 ms   252 ms   248 ms  et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
 13   263 ms   255 ms   265 ms  be2-pe02-eqch2.as57976.net [137.221.69.73]
 14   259 ms   260 ms   267 ms  chi-eqch2-ia-bons-04.as57976.net [137.221.66.15]
 15   256 ms   263 ms   266 ms  24.105.62.129

Trace complete.
PS C:\>

There’s a noticeable lag spike right where Level3 hands off to Blizzard, but return paths can be fun (note that this is a notoriously unreliable way to measure the return path):

$ ping -R 24.105.62.129
PING 24.105.62.129 (24.105.62.129) 56(124) bytes of data.
64 bytes from 24.105.62.129: icmp_seq=1 ttl=242 time=282 ms
NOP
RR:     142.114.117.29
        30.30.30.30
        10.178.206.72
        64.230.195.181
        4.28.138.46
        4.69.170.2
        4.35.72.33
        137.221.66.8
        137.221.66.9

Probably better off to look at the Looking Glass stuff, as that gives me better return path:

traceroute to 142.114.117.29 (142.114.117.29), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.276 ms  0.254 ms  0.250 ms
 2  37.244.22.130 (37.244.22.130)  1.521 ms  1.546 ms  1.568 ms
 3  24.105.30.166 (24.105.30.166)  4.975 ms  4.998 ms  5.375 ms
 4  137.221.66.4 (137.221.66.4)  1.534 ms  2.956 ms  2.960 ms
 5  137.221.68.68 (137.221.68.68)  1.668 ms  1.673 ms  1.671 ms
 6  137.221.68.32 (137.221.68.32)  1.277 ms  1.468 ms  1.065 ms
 7  213.248.78.166 (213.248.78.166)  1.371 ms  1.386 ms  1.227 ms
 8  dls-b21-link.telia.net (62.115.123.136)  31.807 ms  31.819 ms  32.074 ms
 9  213.155.130.179 (213.155.130.179)  42.210 ms  42.221 ms  42.220 ms
10  213.155.130.176 (213.155.130.176)  52.907 ms  52.942 ms  52.628 ms
11  213.248.79.222 (213.248.79.222)  73.639 ms  74.617 ms  74.615 ms
12  * * *
13  * * *
14  * * *
15  * * *

So for some reason, the return path to me is going through Telia, which is causing the grief. If we wait for latency to settle down a bit, we can see that we’re not longer going through Telia, but through AT&T:

MTR:
Start: Mon Nov 19 15:55:24 2018 Blizzard  1.|-- Blizzard           0.0%    10    0.3   0.3   0.2   0.4   0.0
  2.|-- 37.244.23.130           0.0%    10    0.6   0.6   0.5   0.9   0.0
  3.|-- 24.105.62.146           0.0%    10    1.2   1.6   1.0   5.6   1.2
  4.|-- 137.221.66.8            0.0%    10    2.0   2.0   1.9   2.1   0.0
  5.|-- 137.221.69.66           0.0%    10  216.1  56.9   1.8 220.2  92.3
  6.|-- 137.221.69.32           0.0%    10    1.5   1.4   1.3   1.9   0.0
  7.|-- 12.246.90.153           0.0%    10    2.2   2.0   1.9   2.3   0.0
  8.|-- cr1.cgcil.ip.att.net    0.0%    10    9.9   6.4   3.1   9.9   2.4
  9.|-- gar18.cgcil.ip.att.net  0.0%    10   70.0  24.8   1.2  99.6  34.1
 10.|-- 12.249.212.10           0.0%    10   28.0  26.8  26.5  28.0   0.3
 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.|-- ???                    100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- 142.114.116.1           0.0%    10   27.9  27.3  27.1  27.9   0.0
 16.|-- 142.114.117.29          0.0%    10   27.9  28.1  27.7  29.2   0.3

An important thing to note: I ran the high-latency return-path check with the traceroute option, and the low-latency return-path check with the MTR option. For some reason, when running the low-latency return-path check with traceroute, it follows the same path and shows the same latency issues as the high-latency return-path check – which doesn’t make any sense, as I’m not seeing any latency issues.

I’m still waiting for latency to go back up so I can do a high-latency return-path check with MTR.

FWIW, whenever I try to open an issue with my ISP on this (Bell), I’m told that since my connection to the Internet is fine and it’s just a problem with WoW, the issue is with Blizzard and I need to open a ticket with them. AFAICT, this seems to be a route path issue from Blizzard to Bell, so while they’re not wrong, they’re also definitely not right, either.

EDIT: Just ran an MTR during the high-latency, and it’s going the route of AT&T:

Start: Mon Nov 19 17:15:52 2018 Blizzard  1.|-- Blizzard           0.0%    10    0.3   0.4   0.3   0.5   0.0
  2.|-- 37.244.23.2            0.0%    10    0.8 179.5   0.5 602.6 251.3
  3.|-- 24.105.62.146          0.0%    10    0.9   1.1   0.9   2.0   0.0
  4.|-- 137.221.66.8           0.0%    10    2.2   2.1   1.9   2.2   0.0
  5.|-- 137.221.69.70          0.0%    10    2.0   2.0   1.9   2.1   0.0
  6.|-- 137.221.69.34          0.0%    10    1.3   3.3   1.2  13.4   4.1
  7.|-- 12.246.90.153          0.0%    10    2.1   2.1   2.0   2.4   0.0
  8.|-- 12.122.99.98           0.0%    10    8.4   6.0   3.3   9.2   2.1
  9.|-- gar6.ipsin.ip.att.net  0.0%    10   10.4  24.9   1.8  69.7  29.0
 10.|-- 12.249.212.10          0.0%    10  287.2 291.0 286.0 299.3   4.4
 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.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- 142.114.116.1          0.0%    10  298.2 289.4 276.4 301.1   9.1
 16.|-- 142.114.117.29         0.0%    10  299.4 291.2 279.8 303.2   8.6

So… MTR is going via AT&T, traceroute is going via Telia, and both are showing latency spikes in different locations. /shrug

84

Just to let you know that a Bell rep contacted Blizzard’s CSR on my behalf and obtained some information from them in regards to peering. The same Bell rep forwarded this to Bell’s NOC which he has opened an internal ticket with.

Hopefully we’ll be able to play soon.

3 Likes
85

Another day of lag spikes I see…starting to become very annoying, can’t do M+ with these spikes, so no weekly cache and no key for next week…very frustrating seeing your guild-mates progress without you!

86

Hey all,

We made some modifications on our end and have a few more tweaks to make as soon as we can. Can I get a pulse check for Bell Canada users? Are we seeing improvements? Who is still having issues? Where/when are you seeing issues? If those who are still having problems can post WinMTRs that would be excellent.

If you have problems posting your WinMTR due to trust level issues, just use a ` mark before and after the test. (Same key as the tilde.)

It'll look like this

87

Still Lagging.
`|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 75 75 0 0 1 0
10.11.5.193 - 0 75 75 4 6 21 5
No response from host - 100 15 0 0 0 0 0
tcore2-kitchener06_ae5.net.bell.ca - 0 75 75 7 8 13 8
dis18-kitchener06_10-0-0.net.bell.ca - 0 75 75 4 4 17 4
tcore3-kitchener06_0-9-0-0.net.bell.ca - 0 75 75 7 8 24 10
tcore3-toronto63_bundle-ether30.net.bell.ca - 0 75 75 8 12 16 10
tcore3-toronto01_0-1-0-1.net.bell.ca - 0 75 75 8 11 16 12
bx2-toronto01_et5-1-0.net.bell.ca - 0 75 75 7 8 16 7
ae55.bar2.Toronto1.Level3.net - 0 75 75 20 20 24 20
4.69.216.226 - 15 47 40 22 27 49 25
BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 75 75 26 28 42 27
ae1-br01-eqny8.as57976.net - 0 75 75 267 297 335 328
et-0-0-2-br02-eqch2.as57976.net` - 0 75 75 267 297 339 328
be2-pe02-eqch2.as57976.net - 0 75 75 270 297 337 330
chi-eqch2-ia-bons-04.as57976.net - 0 75 75 269 297 336 329
24.105.62.129 - 0 75 75 271 298 338 331
________________________________________________ ______ ______ ______ ______ ______ ______

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

88

Didn’t make any difference - ran this at 7.08pm:

`|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| mynetwork - 0 | 64 | 64 | 0 | 0 | 3 | 0 |

| 10.11.1.17 - 0 | 64 | 64 | 3 | 7 | 23 | 9 |

| 10.178.206.86 - 0 | 64 | 64 | 4 | 4 | 15 | 4 |

| 10.178.206.87 - 0 | 64 | 64 | 4 | 5 | 19 | 4 |

| tcore4x-hamilton14_0-4-0-0.net.bell.ca - 0 | 64 | 64 | 6 | 10 | 20 | 13 |

|tcore4-toronto47_bundle-ether23.net.bell.ca - 0 | 64 | 64 | 6 | 9 | 17 | 10 |

|tcore4-toronto01_100gige0-14-0-0.net.bell.ca - 0 | 64 | 64 | 6 | 10 | 16 | 11 |

| bx2-toronto01_et7-1-0.net.bell.ca - 0 | 64 | 64 | 5 | 6 | 25 | 6 |

| ae55.bar2.Toronto1.Level3.net - 0 | 64 | 64 | 18 | 18 | 24 | 18 |

| 4.69.216.226 - 18 | 40 | 33 | 20 | 27 | 36 | 21 |

| BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 | 64 | 64 | 24 | 27 | 39 | 25 |

| ae1-br01-eqny8.as57976.net - 4 | 56 | 54 | 312 | 356 | 425 | 376 |

| et-0-0-2-br02-eqch2.as57976.net - 12 | 42 | 37 | 312 | 469 | 3399 | 3399 |

| be2-pe02-eqch2.as57976.net - 2 | 60 | 59 | 311 | 350 | 375 | 373 |

| 24.105.62.129 - 4 | 56 | 54 | 312 | 351 | 373 | 373 |

|________________________________________________|______|______|______|______|______|______|

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

89

No change.

Location: Ottawa, ISP: Bell Canada

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 211 211 0 0 7 0
10.11.3.25 - 0 211 211 12 16 33 27
No response from host - 100 42 0 0 0 0 0
tcore3x-ottawa23_bundle-ether14.net.bell.ca - 2 199 196 12 17 29 19
dis32-ottawa23_ae0.net.bell.ca - 1 203 201 12 14 38 12
tcore4x-ottawa23_bundle-ether7.net.bell.ca - 2 199 196 14 19 31 16
tcore4-montreal02_1-9-0-0.net.bell.ca - 1 207 206 15 19 32 22
bx7-montreal02_ae5.net.bell.ca - 2 199 196 14 15 27 15
lag-107.bear2.Montreal2.Level3. net - 18 123 101 15 16 25 17
4.69.216.226 - 23 111 86 24 36 46 35
BLIZZARD-EN.ear1.NewYork5.Level3. net - 1 203 201 29 33 56 30
ae1-br01-eqny8.as57976. net - 18 122 101 370 376 422 372
et-0-0-2-br02-eqch2.as57976. net - 23 106 82 0 471 4404 389
be2-pe02-eqch2.as57976. net - 19 122 100 0 373 388 371
24.105.62.129 - 18 123 102 372 376 394 375
________________________________________________ ______ ______ ______ ______ ______ ______

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

This next test done at 7:20pm EST,

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 112 112 0 0 4 3
10.11.3.25 - 0 112 112 12 15 29 16
No response from host - 100 23 0 0 0 0 0
tcore3x-ottawa23_bundle-ether14.net.bell.ca - 0 112 112 13 16 21 14
dis32-ottawa23_ae0.net.bell.ca - 0 112 112 12 13 34 13
tcore4x-ottawa23_bundle-ether7.net.bell.ca - 0 112 112 15 18 24 21
tcore4-montreal02_1-9-0-0.net.bell.ca - 0 112 112 15 18 24 17
bx7-montreal02_ae5.net.bell.ca - 0 112 112 14 14 28 15
lag-107.bear2.Montreal2.Level3. net - 21 63 50 15 15 19 17
4.69.216.226 - 19 65 53 0 37 46 44
BLIZZARD-EN.ear1.NewYork5.Level3. net - 0 112 112 29 31 43 33
ae1-br01-eqny8.as57976. net - 10 85 77 344 377 440 397
et-0-0-2-br02-eqch2.as57976. net - 14 73 63 343 374 421 370
be2-pe02-eqch2.as57976. net - 10 81 73 344 375 418 372
24.105.62.129 - 6 93 88 0 377 416 374
________________________________________________ ______ ______ ______ ______ ______ ______

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

90

It’s gotten much worse now, I was sitting around 200ms when I am normally at 40, now I am stuck at a solid 4694ms and it never changes.
`
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 83 83 0 0 5 0
10.11.0.153 - 0 83 83 15 19 40 18
10.178.206.30 - 0 83 83 14 15 42 14
10.178.206.31 - 0 83 83 14 15 37 15
tcore4x-london14_0/4/0/2.net.bell.ca` - 0 83 83 18 22 41 19
tcore4-toronto47_hundredgige2-8-0-1.net.bell.ca` - 0 83 83 18 22 39 21
tcore4-toronto01_100gige0-14-0-0.net.bell.ca` - 0 83 83 19 23 41 23
bx2-toronto01_et7-1-0.net.bell.ca` - 0 83 83 17 19 44 18
ae55.bar2.Toronto1.Level3.net` - 2 79 78 30 32 42 31
4.69.216.226 - 20 47 38 42 51 72 49
BLIZZARD-EN.ear1.NewYork5.Level3.net` - 0 83 83 37 39 52 37
ae1-br01-eqny8.as57976.net` - 24 43 33 356 380 426 410
et-0-0-2-br02-eqch2.as57976.net` - 24 43 33 0 409 1341 411
be2-pe02-eqch2.as57976.net` - 16 51 43 353 379 414 413
24.105.62.129 - 16 52 44 354 382 425 410
________________________________________________ ______ ______ ______ ______ ______ ______
91

I’ve been spiking 300-400 all week but after this change now getting 1000ms this is amazing.

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 244 244 0 0 24 0
10.11.7.105 - 0 243 243 1 12 1460 1
10.178.206.72 - 0 244 244 0 1 23 1
10.178.206.73 - 0 244 244 1 2 33 2
tcore3-toronto12_2-4-0-0.net.bell.ca - 0 244 244 14 18 41 16
tcore3-chicagocp_hundredgige0-4-0-0.net.bell.ca - 0 244 244 14 16 38 16
bx6-chicagodt_0-6-0-0.net.bell.ca - 0 244 244 13 15 34 14
12.249.212.9 - 12 165 146 319 352 428 320
cr1.cgcil.ip.att.net - 5 201 191 322 352 389 325
gar2.clboh.ip.att.net - 14 158 137 319 356 458 323
12.122.251.50 - 91 52 5 330 371 479 364

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

92
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
10.0.1.1 0 179 179 0 0 5 0
mynetwork 0 179 179 2 4 19 4
10.11.1.17 0 179 179 16 22 51 17
10.178.206.86 0 179 179 16 18 30 17
10.178.206.87 1 175 174 15 18 35 35
tcore3x-hamilton14_0-4-0-0.net.bell.ca 0 179 179 18 24 51 25
tcore3-toronto12_bundle-ether19.net.bell.ca 0 179 179 18 22 51 21
tcore4-toronto01_0-1-0-1.net.bell.ca 0 179 179 18 24 52 21
bx2-toronto01_et7-1-0.net.bell.ca 0 179 179 17 20 51 20
ae55.bar2.Toronto1.Level3.net 1 175 174 27 31 50 30
4.69.216.226 20 104 84 34 47 66 46
BLIZZARD-EN.ear1.NewYork5.Level3.net 0 179 179 36 41 70 39
ae1-br01-eqny8.as57976.net 0 179 179 326 361 460 360
et-0-0-2-br02-eqch2.as57976.net 0 179 179 324 359 485 357
be2-pe01-eqch2.as57976.net 0 179 179 324 358 380 359
chi-eqch2-ia-bons-02.as57976.net 0 179 179 326 358 382 361
24.105.62.129 0 179 179 326 359 387 361
93

Same sh… again … day 4th of this mess… today i get 1500-2000 ms… can’t raid, and difficult to do anything…

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
mynetwork 0 244 244 0 0 2 0
10.11.18.225 0 244 244 1 4 15 11
10.178.206.132 0 244 244 3 3 6 3
10.178.206.133 0 244 244 3 4 24 4
tcore4-montreal02_2-12-0-0.net.bell.ca 0 244 244 4 8 13 9
bx7-montreal02_ae5.net.bell.ca 0 244 244 3 4 18 4
lag-107.bear2.Montreal2.Level3.net 19 140 114 0 5 7 5
4.69.216.226 19 140 114 17 29 39 24
BLIZZARD-EN.ear1.NewYork5.Level3.net 0 244 244 17 19 44 18
ae1-br01-eqny8.as57976.net 6 200 189 318 361 431 353
et-0-0-2-br02-eqch2.as57976.net 10 171 154 317 425 4312 353
be2-pe01-eqch2.as57976.net 8 188 174 316 357 397 351
24.105.62.129 6 200 189 318 361 400 353
94

Thanks for the tests everyone,

The WinMTRs confirm that the issue’s still happening. We forwarded this back to the network engineers to see if there’s anything else they can do. Feel free to keep the tests coming, the more information we have the better.

1 Like
95

MS looks normal at around 25, but still feels a bit off, can see some packet loss in the WinMTR. Spikes usually come in a while after logging on, I’ll be keeping an eye on it.

Bell, Montreal.

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

Host - % Sent Recv Best Avrg Wrst Last
SAGEMCOM - 0 258 258 0 0 26 0
10.11.16.249 - 0 258 258 1 5 36 1
10.178.206.132 - 0 258 258 1 2 30 1
10.178.206.133 - 0 258 258 1 2 34 3
tcore3-montreal02_2-12-0-0.net.bell.ca - 0 258 258 1 6 38 4
bx7-montreal02_ae4.net.bell.ca - 0 258 258 1 2 30 2
lag-107.bear2.Montreal2.Level3. net - 16 162 137 1 3 39 2
4.69.216.226 - 22 139 109 23 33 42 37
BLIZZARD-EN.ear1.NewYork5.Level3. net - 0 258 258 16 19 51 28
ae1-br01-eqny8.as57976. net - 0 258 258 24 28 95 25
et-0-0-2-br02-eqch2.as57976. net - 0 258 258 24 35 593 45
be2-pe01-eqch2.as57976. net - 0 258 258 25 26 59 27
24.105.62.129 - 0 258 258 25 27 60 26
________________________________________________ ______ ______ ______ ______ ______ ______

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

96

Bell. Ontario, Canada.
Why is it when i track the IP’s after it reaches Blizzard, it says it’s from Netherlands?

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
mynetwork 0 626 626 0 0 12 0
10.11.3.73 1 602 596 5 12 40 6
10.178.206.30 1 607 602 5 9 28 7
10.178.206.31 1 610 606 6 9 27 6
tcore3x-london14_0/4/0/2.net.bell.ca 1 610 606 9 16 41 14
tcore3-toronto47_hundredgige2-8-0-1.net.bell.ca 1 618 616 10 17 38 15
tcore3-toronto01_0-1-0-0.net.bell.ca 1 602 596 9 17 37 18
bx2-toronto01_et5-1-0.net.bell.ca 1 622 621 9 13 39 11
ae55.bar2.Toronto1.Level3.net 1 603 597 19 25 65 20
4.69.216.226 20 351 282 36 46 65 38
BLIZZARD-EN.ear1.NewYork5.Level3.net 1 606 601 28 34 66 35
ae1-br01-eqny8.as57976.net 2 595 587 32 39 130 52
et-0-0-2-br02-eqch2.as57976.net 3 565 551 34 69 4692 35
be2-pe01-eqch2.as57976.net 1 614 611 32 37 60 33
24.105.62.129 1 622 621 33 38 63 38

And when it starts to lag:

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
mynetwork 0 338 338 0 0 6 0
10.11.3.73 1 330 328 5 12 42 13
10.178.206.30 0 338 338 5 9 29 9
10.178.206.31 0 338 338 6 9 29 6
tcore3x-london14_0/4/0/2.net.bell.ca 1 334 333 10 16 37 17
tcore3-toronto47_hundredgige2-8-0-1.net.bell.ca 1 330 328 10 17 39 25
tcore3-toronto01_0-1-0-0.net.bell.ca 1 330 328 10 17 36 31
bx2-toronto01_et5-1-0.net.bell.ca 0 338 338 9 13 42 11
ae55.bar2.Toronto1.Level3.net 1 326 323 20 26 49 20
4.69.216.226 23 178 138 0 47 66 45
BLIZZARD-EN.ear1.NewYork5.Level3.net 1 326 323 28 34 71 29
ae1-br01-eqny8.as57976.net 1 330 328 43 185 355 355
et-0-0-2-br02-eqch2.as57976.net 4 286 275 44 266 3740 322
be2-pe01-eqch2.as57976.net 2 322 318 46 185 330 322
24.105.62.129 2 318 313 44 179 331 323
97

Yep, definitely the same laggy behavior as before. Been logged on for about 45 minutes and I am back at 250~ ms and climbimg, probably ends around the usual 500~.

98

its lagging for 10-20 min… and go down to 200-300 ms for 30-40 min, and again etc…

99

Bell, Ontario

Was at a solid 40ms for around 1hr, then at 8:40~ it started to go up to over 300+, still climbing

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.2.1 0 265 265 0 0 15 0
10.11.1.105 0 265 265 15 19 40 16
No response from host 100 53 0 0 0 0 0
10.178.206.87 0 265 265 15 16 36 16
tcore4x-hamilton14_0-4-0-0.net.bell.ca 0 265 265 17 22 30 24
tcore4-toronto47_bundle-ether23.net.bell.ca 0 265 265 17 21 26 25
tcore4-toronto01_100gige0-14-0-0.net.bell.ca 0 265 265 18 22 36 21
bx2-toronto01_et7-1-0.net.bell.ca 0 265 265 17 18 43 18
ae55.bar2.toronto1.level3.net 0 265 265 28 29 41 29
4.69.216.226 25 137 104 46 53 58 52
blizzard-en.ear1.newyork5.level3.net 0 265 265 36 42 1013 37
ae1-br01-eqny8.as57976.net 2 249 245 323 364 484 377
et-0-0-2-br02-eqch2.as57976.net 5 223 213 0 377 3002 353
be2-pe02-eqch2.as57976.net 4 231 222 321 360 393 384
chi-eqch2-ia-bons-04.as57976.net 3 237 230 326 364 394 352
24.105.62.129 3 245 240 324 363 392 373
100

I will also add that after around 25~ mins of super high ms, it started to go back down. Takes around 10 mins of slowly going down to go back to normal. Here is another MTR after it mostly settled back down.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.2.1 0 152 152 0 0 5 0
10.11.1.105 0 152 152 15 22 49 16
No response from host 100 30 0 0 0 0 0
10.178.206.87 1 148 147 15 19 45 16
tcore4x-hamilton14_0-4-0-0.net.bell.ca 2 144 142 18 24 48 22
tcore4-toronto47_bundle-ether23.net.bell.ca 2 144 142 18 24 49 23
tcore4-toronto01_100gige0-14-0-0.net.bell.ca 0 152 152 18 25 46 20
bx2-toronto01_et7-1-0.net.bell.ca 1 148 147 17 20 61 18
ae55.bar2.toronto1.level3.net 0 151 151 28 33 65 30
4.69.216.226 19 88 72 0 57 81 57
blizzard-en.ear1.newyork5.level3.net 3 136 132 47 58 81 64
ae1-br01-eqny8.as57976.net 0 151 151 69 83 126 80
et-0-0-2-br02-eqch2.as57976.net 1 148 147 40 57 181 181
be2-pe02-eqch2.as57976.net 3 140 137 69 78 105 78
chi-eqch2-ia-bons-04.as57976.net 4 132 127 72 81 106 79
24.105.62.129 4 132 127 71 80 105 80