Xerʘ

Notably Dangerous Demo-Knight
Contributor
Summary:
Server Lag MTR Info for US VSH
Details:
I've been having lag issues over the last couple weeks to a month on the US VSH server. Was getting 75 ish ping before and now I get 95-100 and I've had no change on my end or at least none to my knowledge. Hope this sheds some light on what's going on.

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

| 91.216.250.14 - 0 | 84 | 84 | 92 | 95 | 116 | 99 |
|________________________________________________|______|_​
 

Xerʘ

Notably Dangerous Demo-Knight
Contributor
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| hitronhub.home - 78 | 9 | 2 | 1 | 2 | 4 | 1 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| rc2we-be128-1.ed.shawcable.net - 0 | 35 | 35 | 17 | 22 | 34 | 22 |
| rc3no-be6.cg.shawcable.net - 0 | 35 | 35 | 21 | 26 | 41 | 21 |
| rc3so-be23.cg.shawcable.net - 0 | 35 | 35 | 21 | 26 | 46 | 25 |
| rc1wt-be82.wa.shawcable.net - 0 | 35 | 35 | 42 | 47 | 70 | 46 |
| ae22.cr4-sea2.ip4.gtt.net - 0 | 35 | 35 | 42 | 50 | 75 | 48 |
| ae18.cr5-sea2.ip4.gtt.net - 0 | 35 | 35 | 42 | 52 | 119 | 43 |
| choopa-gw.ip4.gtt.net - 22 | 19 | 15 | 42 | 49 | 60 | 60 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| 91.216.250.14 - 0 | 35 | 35 | 95 | 97 | 108 | 97 |
|________________________________________________|______|______|______|______|______|______|
 

Bottiger

Administrator
I believe this is a Shaw problem. For whatever reason, your ping to Seattle should be 24 and not 50.

Here is a trace from someone with your same ISP and region.

traceroute to 91.216.250.14 (91.216.250.14) 64 hops max, 76 byte packets
1 192.168.0.1 (192.168.0.1) [AS???] 7.878 ms 3.204 ms 3.201 ms
2 24.67.96.1 (24.67.96.1) [AS6327] 16.73 ms 11.866 ms 28.661 ms
3 rd3cs-be115-1.ok.shawcable.net (64.59.170.25) [AS6327] 12.301 ms 18.259 ms 25.636 ms
4 rc1st-be5.vc.shawcable.net (66.163.67.217) [AS6327] 16.053 ms 17.245 ms 24.445 ms
5 rc2wt-be50-1.wa.shawcable.net (66.163.70.106) [AS6327] 20.244 ms 23.349 ms 22.258 ms
6 rc1wt-be18-1.wa.shawcable.net (66.163.64.81) [AS6327] 22.022 ms 22.188 ms 26.123 ms
7 ae22.cr4-sea2.ip4.gtt.net (209.120.141.209) [AS3257] 20.252 ms 22.597 ms 20.342 ms
8 ae18.cr5-sea2.ip4.gtt.net (89.149.130.34) [AS3257] 21.946 ms 24.179 ms 20.807 ms
9 choopa-gw.ip4.gtt.net (173.205.61.30) [AS3257] 21.334 ms
*
choopa-gw.ip4.gtt.net (173.205.61.30) [AS3257] 24.23 ms
10 * * *
11 * * *
12 * * *
13 91.216.250.14 (91.216.250.14) [AS208810] 72.851 ms 83.95 ms 71.745 ms

Source address is: 24.67.116.54

The reason why you may get a "normal" ping to other servers in Texas is maybe because they get routed to Chicago. Normally Shaw goes through Chicago instead of Washington, but we had to remove that link because it got congested and people were getting 200 ping. But they probably fixed it by now and so I am removing the block.

traceroute to 91.216.250.14 (91.216.250.14) 64 hops max, 76 byte packets
1 192.168.0.1 (192.168.0.1) [AS???] 7.286 ms 2.644 ms 2.7720000000000002 ms
2 24.67.96.1 (24.67.96.1) [AS6327] 14.282 ms 11.568 ms 14.468 ms
3 rd3cs-be115-1.ok.shawcable.net (64.59.170.25) [AS6327] 19.329 ms 15.667 ms 13.713 ms
4 rc1st-be5.vc.shawcable.net (66.163.67.217) [AS6327] 80.718 ms 30.547 ms 18.539 ms
5 rc3no-be11-1.cg.shawcable.net (66.163.72.69) [AS6327] 23.664 ms 25.571 ms 27.227 ms
6 rc3so-be23.cg.shawcable.net (66.163.71.118) [AS6327] 23.323 ms 25.942 ms 24.588 ms
7 rc4ec-be13.il.shawcable.net (66.163.65.18) [AS6327] 55.366 ms 52.635 ms 57.733 ms
8 20473.chi.equinix.com (208.115.137.46) [AS???] 85.558 ms 78.572 ms 138.426 ms
9 * * *
10 * * *
11 91.216.250.14 (91.216.250.14) [AS208810] 77.171 ms 77.388 ms 75.9 ms

Source address is: 24.67.116.54
 

Xerʘ

Notably Dangerous Demo-Knight
Contributor
Alrighty thanks. If the unblocking doesn't do anything is this something I would have to contact my provider to fix or is there a way for me to manually do it, or in the worse case just SOL?
 

Xerʘ

Notably Dangerous Demo-Knight
Contributor
I have a VPN which I was using (which barely helped) and I was getting the message I was going to get banned for continued use so I just stopped. I checked to see if its any better and I'm now getting 78-81 ping which is leaps and bounds better so I think I'm fine. Thanks.
 

Bottiger

Administrator
You should ask them to fix it anyway. Going through Chicago gives 6 more ping than through Washington.

If you do, you should tell them the IP 149.28.9.2. They won't see an issue to Saxton US as it goes through Chicago now.

The VPN would not have worked if it was getting routed through Seattle.