Starhub Singapore, Singtel, MyRepublic - Lots of Spikey World delay

Is there going to be an update from blizzard side? Playing with VPN is not a long term solution…

Considering every SE-Asian ISP listed here ends up going via Singapore (which is where WinMTR logs have been showing the packet loss) to the Australian servers… who’s really in the wrong here, “bucko”?

Hey all,

We made some routing adjustments recently and are looking to see how well it worked for everybody. Can you all turn off your VPNs and see how things are going without? If the spikes are still there, let’s get a WinMTR which catches it and a looking glass so we can look for more options.

1 Like

I played many hours yesterday trying to get WinMTR if lag happened. It was a smooth day for me on Singtel. The ping in-game was stable at around 147ms. So, no ping capture from me.

Edit: no vpn used.

yesterday about 3 hours, no VPN.
Smooth running on OCE server, home/world about 140~180.
Highest hit is about ~200 which occurred during EBG; IOC. Slight lag.

1 Like

Can’t do looking glass for OCE realms i believe, there isnt a Barthilas. Home latency is at 165ms.

Latest WinMTR

|

| WinMTR statistics |

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

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

| 192.168.1.254 - 0 | 1826 | 1826 | 0 | 0 | 10 | 0 |

| bb42-61-167-254.singnet.com.sg - 0 | 1826 | 1826 | 1 | 5 | 119 | 3 |

| 202.166.123.134 - 0 | 1826 | 1826 | 1 | 3 | 27 | 2 |

| 202.166.123.133 - 0 | 1826 | 1826 | 1 | 2 | 41 | 3 |

| ae8-0.tp-cr03.singnet.com.sg - 0 | 1826 | 1826 | 1 | 2 | 30 | 2 |

| ae4-0.tp-er03.singnet.com.sg - 0 | 1826 | 1826 | 1 | 3 | 66 | 2 |

| 202.166.124.190 - 0 | 1826 | 1826 | 1 | 5 | 80 | 1 |

| ip-202-147-32-126.asianetcom. net - 0 | 1826 | 1826 | 2 | 3 | 23 | 3 |

|te0-0-2-0.wr1.sin0.10026.telstraglobal. net - 0 | 1826 | 1826 | 3 | 6 | 32 | 7 |

| xe-0-1-1.gw1.sin2.pacnet. net - 0 | 1826 | 1826 | 3 | 6 | 52 | 3 |

|po11-0-0.gw5.sin1.10026.telstraglobal. net - 0 | 1826 | 1826 | 3 | 6 | 74 | 4 |

| i-92.sgpl-core02.telstraglobal. net - 0 | 1826 | 1826 | 3 | 6 | 27 | 5 |

| i-15350.pthp-core02.telstraglobal. net - 0 | 1826 | 1826 | 6 | 54 | 79 | 53 |

| i-10353.sydo-core03.telstraglobal. net - 1 | 1822 | 1821 | 52 | 163 | 190 | 165 |

| i-0-0-0-1.sydo10.bi.telstraglobal. net - 1 | 1822 | 1821 | 127 | 171 | 272 | 172 |

| unknown.telstraglobal. net - 1 | 1822 | 1821 | 124 | 171 | 196 | 172 |

| 137.221.85.35 - 1 | 1822 | 1821 | 121 | 125 | 244 | 122 |

| et-0-0-1-pe01-eqsy4.as57976. net - 1 | 1822 | 1821 | 125 | 142 | 213 | 140 |

| 137.221.66.145 - 1 | 1822 | 1821 | 143 | 165 | 201 | 165 |

| 103.4.115.248 - 1 | 1822 | 1821 | 168 | 172 | 195 | 172 |

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

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

Side note: I put a space before every “. net” cos couldnt post hyperlinks lol didnt know how to solve that.

Its finally fixed omg.

Back to 90 ms and no packet loses on Starhub.

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

Host - % Sent Recv Best Avrg Wrst Last
Linksys13694 - 0 140 140 0 0 0 0
2.16.182.58.starhub. net. sg - 0 140 140 1 2 32 2
an-ts-br05.starhub. net. sg - 0 140 140 1 1 3 2
183.90.44.229 - 0 140 140 2 2 4 2
unknown.telstraglobal. net - 0 140 140 2 4 76 3
i-93.sgpl-core02.telstraglobal. net - 0 140 140 2 3 5 3
i-15350.pthp-core02.telstraglobal. net - 0 140 140 50 52 54 54
i-10353.sydo-core03.telstraglobal. net - 0 140 140 90 91 93 92
i-0-0-0-0.sydo10.bi.telstraglobal. net - 0 140 140 90 91 132 91
unknown.telstraglobal. net - 0 140 140 90 91 119 91
et-0-0-48-br01-eqsy4.as57976. net - 0 140 140 91 95 198 92
et-0-0-0-pe02-eqsy4.as57976. net - 0 140 140 90 93 150 91
103.4.115.248 - 0 140 140 90 90 91 91
________________________________________________ ______ ______ ______ ______ ______ ______
1 Like

Ping is a constant 240+ Singtel ISP, its constant but previously it was 140+ … No instance lag or world lag yet

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

Host - % Sent Recv Best Avrg Wrst Last
Singtel-ACPlus - 0 4813 4813 0 0 16 0
bb219-74-149-254.singnet.com.sg - 0 4814 4814 1 6 156 4
202.166.123.134 - 0 4814 4814 1 2 35 2
202.166.123.133 - 0 4814 4814 1 2 55 2
ae8-0.tp-cr03.singnet.com.sg - 0 4814 4814 1 3 56 8
ae4-0.tp-er03.singnet.com.sg - 0 4814 4814 1 3 54 12
202.166.124.190 - 0 4814 4814 1 5 104 2
ip-202-147-32-126.asianetcom.ne t - 0 4814 4814 1 5 51 2
te0-3-0-3.wr2.sin0.10026.telstraglobal.ne t - 0 4814 4814 2 8 47 7
xe0-2-0.gw1.sin2.pacnet.ne t - 1 4810 4809 2 7 58 3
po11-0-0.gw5.sin1.10026.telstraglobal.ne t - 0 4814 4814 3 8 101 3
i-92.sgpl-core02.telstraglobal.ne t - 0 4814 4814 3 7 46 4
202.84.140.37 - 1 4810 4809 4 144 165 144
i-10353.sydo-core03.telstraglobal.ne t - 1 4810 4809 52 165 206 167
i-0-0-0-1.sydo10.bi.telstraglobal.ne t - 1 4810 4809 170 172 271 171
unknown.telstraglobal.ne t - 1 4810 4809 143 145 290 144
137.221.85.35 - 0 4814 4814 146 150 304 149
et-0-0-0-pe02-eqsy4.as57976.ne t - 1 4810 4809 139 143 216 140
103.4.115.248 - 1 4807 4806 143 203 241 204
________________________________________________ ______ ______ ______ ______ ______ ______

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

Think you need to contact Singtel for this case. There is clearly a routing problem. way before the connection reach Blizzard servers.

If you pay attention, the lag spike happens immediately at the node 202.84.140.37.
This is questionable because you are already connecting via Telstraglobal routing but for some reason it routes to 202.84.140.37 and then back to Telstraglobal again…

Even though we are on diff ISP, the nodes / routing partner we are connecting through are similar but your case clearly needs intervention from Singtel.

So envy. I wish I could get this back on Singtel. The last time I got 90ms was over 6 months ago.

If you want to, you can post your MTR and i can help you take a look at it.
Chances are, there is a legitimate routing problem on Singtel’s side and in that case, only Singtel can help you out.

Starhub and some other ISP like myrepublic seems to be routing correctly while Singtel users seems to have weird and questionable routing path taken based on some of the MTR posted.

The general rule is that if you already have high latency/ping before the connection reaches Blizzard servers, its not really something Blizzard can help you with.

1 Like

Same here, never remembered getting 90ms on starhub ever before though…

Finally. I see improvements today. last time my home ms=150 and world ms=170 usually. Then few days ago spiked to 8k for 2 to 3 days. Now home ms only 90ms and world ms around 110. Big improvements for me. Blizz did the re-routing helps but if it was done earlier would have been better. Below is my MTR report.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
Escapehunt 0 463 463 1 2 23 1
2.224.164.222.starhub.net.sg 1 452 449 3 8 120 4
183.90.44.117 1 457 455 3 8 121 4
183.90.44.237 0 463 463 3 7 123 4
unknown.telstraglobal.net 1 456 454 4 9 172 6
i-93.sgpl-core02.telstraglobal.net 1 459 458 4 9 130 6
i-15350.pthp-core02.telstraglobal.net 1 452 449 51 57 165 56
i-10353.sydo-core03.telstraglobal.net 1 448 444 92 95 198 96
i-0-0-0-1.sydo10.bi.telstraglobal.net 1 452 449 91 96 207 92
unknown.telstraglobal.net 1 452 449 95 100 217 96
et-0-0-48-br01-eqsy4.as57976.net 1 448 444 92 100 219 103
et-0-0-0-pe02-eqsy4.as57976.net 3 425 415 91 98 206 93
103.4.115.248 2 441 435 95 100 209 96

HI, under singtel ISP, ping constant 164ms for home, but world ms is 120 to 165ms. not sure whey there is gap there

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
Singtel-ACPlus 0 520 520 0 0 3 0
bb42-61-175-254.singnet.com.sg 0 520 520 1 2 48 2
202.166.123.134 0 521 521 1 2 27 2
202.166.123.133 0 520 520 1 1 27 1
ae8-0.tp-cr03.singnet.com.sg 0 520 520 1 2 61 1
ae4-0.tp-er03.singnet.com.sg 0 520 520 1 2 49 1
202.166.124.190 0 520 520 1 4 68 1
ip-202-147-32-126.asianetcom.net 0 521 521 1 2 8 2
te0-0-2-0.wr1.sin0.10026.telstraglobal.net 0 520 520 3 4 19 3
xe-0-1-1.gw1.sin2.pacnet.net 0 521 521 2 3 43 3
po11-0-0.gw5.sin1.10026.telstraglobal.net 0 520 520 3 4 59 3
i-92.sgpl-core02.telstraglobal.net 0 520 520 3 4 20 3
i-15350.pthp-core02.telstraglobal.net 0 520 520 50 52 63 52
i-10353.sydo-core03.telstraglobal.net 1 517 516 142 144 173 144
i-0-0-0-0.sydo10.bi.telstraglobal.net 0 520 520 136 136 176 136
unknown.telstraglobal.net 0 520 520 164 165 197 165
et-0-0-48-br01-eqsy4.as57976.net 0 520 520 122 125 192 122
et-0-0-0-pe02-eqsy4.as57976.net 0 520 520 140 142 205 140
103.4.115.248 0 520 520 164 165 177 167

ya its back to normal. still dont understand why i get 40 ms ping to your overwatch servers in singapore and a 180 ms ping to your wow servers in singapore…

seems like my ping is not as stable as yesterday.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                           192.168.1.254 -    0 | 2964 | 2964 |    1 |    3 |  640 |    4 |
|          bb219-74-47-254.singnet.com.sg -    0 | 2964 | 2964 |    2 |    7 |  620 |    6 |
|                         202.166.123.130 -    0 | 2964 | 2964 |    3 |    6 |  581 |    5 |
|                         202.166.123.129 -    1 | 2960 | 2959 |    2 |    5 |  622 |    9 |
|            ae8-0.qt-cr03.singnet.com.sg -    0 | 2964 | 2964 |    3 |    6 |  652 |    4 |
|           ae12-0.qt-er05.singnet.com.sg -    0 | 2964 | 2964 |    3 |    6 |  631 |    5 |
|                         202.166.126.114 -    1 | 2961 | 2960 |    3 |    8 |  928 |    3 |
|        ip-202-147-32-136.asianetcom.net -    0 | 2964 | 2964 |    3 |    6 |  582 |    4 |
|te0-2-0-0.wr1.sin0.10026.telstraglobal.net -    0 | 2964 | 2964 |    4 |    8 |  660 |    8 |
|            xe-0-1-1.gw1.sin2.pacnet.net -    0 | 2964 | 2964 |    5 |    8 |  623 |    5 |
|po11-0-0.gw5.sin1.10026.telstraglobal.net -    0 | 2964 | 2964 |    5 |    9 |  643 |    7 |
|      i-92.sgpl-core02.telstraglobal.net -    0 | 2964 | 2964 |    5 |    8 |  631 |    7 |
|                           202.84.140.37 -    0 | 2964 | 2964 |  144 |  148 |  587 |  148 |
|                           202.84.140.34 -    0 | 2964 | 2964 |  173 |  175 |  629 |  175 |
|   i-0-0-0-1.sydo10.bi.telstraglobal.net -    1 | 2960 | 2959 |  144 |  147 |  567 |  145 |
|               unknown.telstraglobal.net -    1 | 2960 | 2959 |  148 |  151 |  607 |  150 |
|        et-0-0-48-br01-eqsy4.as57976.net -    1 | 2960 | 2959 |  205 |  210 |  601 |  207 |
|         et-0-0-0-pe02-eqsy4.as57976.net -    1 | 2952 | 2949 |  142 |  148 | 1149 |  143 |
|                           103.4.115.248 -    1 | 2960 | 2959 |  211 |  213 |  606 |  212 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

This issue seems to have cleared up now, it would be great if we could get some sort of response from the blues clarifying what actually happened.

Considering this has happened multiple times now. Would be great to know what the problem was and what is being done to ensure that we dont all miss out on almost a week of our subscriptions again in the future.

Yes, please clear this up and help us understand.

There was an issue with the way that your connections were being routed to our servers, causing you to take an inefficient path to the servers in Australia. It looks to be resolved at this point. If you are having further issues with abnormally high latency, this is likely an individual issue. Please create your own thread in this case.