it is routing issue, not sure is TM or starhub issue. it now route from MY to HK and back to SG.

Target Name: sgp-1.valve.net
IP: 103.28.54.1
Date/Time: 5/9/2015 3:22:46 AM

1 1 ms [192.168.1.1]
2 9 ms [x]
3 6 ms [x]
4 15 ms [x]
5 48 ms 63-216-142-53.static.pccwglobal.net [63.216.142.53]
6 49 ms TenGE6-4.br01.hkg15.pccwbtn.net [63.218.210.198]
7 48 ms TenGE6-4.br01.hkg15.pccwbtn.net [63.218.210.198]
8 53 ms starhub.te3-7.500.br01.hkg15.pccwbtn.net [63.216.142.170]
9 91 ms w118012009.w118012.starhub.net.sg [203.118.12.9]
10 89 ms [203.118.2.29]
11 87 ms an-ats-loc11.starhub.net.sg [203.118.15.242]
12 92 ms [203.116.8.22]
13 90 ms sgp-1.valve.net [103.28.54.1]

Ping statistics for sgp-1.valve.net
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 90ms, Maximum = 90ms, Average = 90ms

since yesterday friday december 22 2017 around 6:30pm, there is a disconnection, reason unknown, observed by connection uptime, since fibre rarely disconnect, i am not there when it happen, but when i check it around at the same night, the unifi 1st hop 10.233.97.36 ping from previously lowest around 2ms rise to right now lowest around 6ms. and the ping result isnt as stable as before.

dota 2 server sgp-1.valve.net 103.28.54.16 ping also rise around 3ms, now 11ms, the trace route hop in between remain the same.

when i play dota 2, i get random hang around 0.5sec each time, happen from time to time, around few minute once.

https://forum.lowyat.net/index.php?act=ST&f...post&p=87457645

UPDATE:

after further testing, it seem that now ONLY IPv6 be able to get the 2ms lowest 1st hop ping, while IPv4 now stuck at 6ms lowest 1st hop ping. TM unifi seem to now prioritize IPv6 Traffic.

you can test it yourself with PingPlotter version 5

https://www.pingplotter.com/download

UPDATE 2:

the unifi ipv6 1st hop ip is 2001:e68:5441:14e2:429b:cdff:febc:6900
the lowest ping reply i can get is 1ms, with PingPlotter 5.5.7.3827

personally i would say it's a bad move, since some services are still running on IPv4, especially gaming, it would take a long time to upgrade the gaming software to IPv6.

UPDATE 3:

testing from streamyx show that IPv6 and IPv4 still getting the almost same ping result. and that streamyx was connected/just upgraded to the lastest new BRAS ibse<number21>.<area code>, some other was imse<number21>.<area code>, previously BSR<AREA CODE><number51>, erx<area code><number0x>.

unifi lastest BRAS was imse<number01>.<area code>, previously BSR<AREA CODE><number01or51>, erx<area code><number21>.

UPDATE 4:

the random hang has nothing to do with unifi, it has everything to do with D-Link DIR-850L supplied by Unifi, The QoS Engine Feature just suck, even assigned Highest priority would cause random hang, the solution is just dun use it at all.



This post has been edited by Alpha_Tay: Dec 28 2017, 03:02 AM

TM and singapore valve steam dota 2 server peering issue?‏ unifi fibre and streamyx ping from 10ms+- to 100ms+-

it just happen today to unifi fibre and streamyx. tested both. the ping is still normal at early morning today 10ms+- with unifi fibre, and now it is 100ms+- with unifi fibre.

server is valve steam dota 2 hosted at singapore

trace route result with unifi fibre, using PingPlotter latest version 5.5.7.3827

UPDATE: forgot to mention already email to TM and e-club malaysia about it

Target Name: sgp-1.valve.net
IP: 103.28.54.16
Date/Time: 1/11/2018 5:18:10 PM - 1/11/2018 5:28:10 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 121 0 3.54 30.61 6.83 10.233.97.36 [10.233.97.36]
2 121 0 8.46 97.73 13.61 10.55.96.105 [10.55.96.105]
3 121 0 82.38 107.26 96.70 103.10.124.246 [103.10.124.246]
4 121 0 108.68 525.48 162.56 192.168.152.9 [192.168.152.9]
5 121 0 83.69 110.77 98.77 sgp-1.valve.net [103.28.54.16]


Target Name: sgp-2.valve.net
IP: 103.10.124.1
Date/Time: 1/11/2018 5:18:42 PM - 1/11/2018 5:28:42 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 4 0 5.98 18.75 12.39 10.233.97.36 [10.233.97.36]
2 4 0 9.07 11.78 10.88 10.55.96.105 [10.55.96.105]
3 4 0 90.80 100.25 93.25 103.10.124.246 [103.10.124.246]
4 4 0 104.04 110.41 108.37 sgp-2.valve.net [103.10.124.1]


Target Name: 45.121.184.1
IP: 45.121.184.1
Date/Time: 1/11/2018 5:19:12 PM - 1/11/2018 5:29:12 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 4 0 4.05 6.04 4.56 10.233.97.36 [10.233.97.36]
2 4 0 10.97 12.37 11.68 10.55.96.105 [10.55.96.105]
3 3 0 103.31 107.10 104.57 103-10-124-246.valve.net [103.10.124.246]
4 3 0 113.68 122.09 116.48 45.121.184.1 [45.121.184.1]


Target Name: 45.121.185.1
IP: 45.121.185.1
Date/Time: 1/11/2018 5:19:27 PM - 1/11/2018 5:29:27 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 3 0 5.96 6.08 6.04 10.233.97.36 [10.233.97.36]
2 3 0 10.87 10.92 10.90 10.55.96.105 [10.55.96.105]
3 3 0 95.77 97.42 96.87 103-10-124-246.valve.net [103.10.124.246]
4 3 0 115.79 239.66 198.37 192.168.152.5 [192.168.152.5]
5 3 0 108.32 109.25 108.63 45.121.185.1 [45.121.185.1]


Target Name: 45.121.186.1
IP: 45.121.186.1
Date/Time: 1/11/2018 5:19:44 PM - 1/11/2018 5:29:44 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 3 0 6.00 6.99 6.35 10.233.97.36 [10.233.97.36]
2 3 0 93.74 94.54 94.25 10.55.208.173 [10.55.208.173]
3 3 0 93.88 95.23 94.50 218.100.6.132 [218.100.6.132]
4 2 100 0 0 0 [-]
5 3 0 104.82 122.13 113.91 45.121.186.1 [45.121.186.1]


Target Name: 45.121.187.1
IP: 45.121.187.1
Date/Time: 1/11/2018 5:19:58 PM - 1/11/2018 5:29:58 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 2 0 6.09 6.17 6.13 10.233.97.36 [10.233.97.36]
2 2 0 93.19 96.85 95.02 10.55.208.173 [10.55.208.173]
3 2 0 92.17 94.56 93.37 218.100.6.132 [218.100.6.132]
4 1 100 0 0 0 [-]
5 2 0 96.62 96.70 96.66 45.121.187.1 [45.121.187.1]

This post has been edited by Alpha_Tay: Jan 11 2018, 05:43 PM

seem like fixed.

Telekom Malaysia and Singapore valve steam dota 2 server peering issue?‏ unifi fibre and streamyx adsl ping from 10ms+- to 60ms+-

it just happen today to unifi fibre and streamyx adsl. tested both.

server is valve steam dota 2 hosted at singapore

trace route result with unifi fibre, using PingPlotter Freeware 1.30

already email to isp TM and e-club malaysia about it

Target Name: sgp-1.valve.net
IP: 103.28.54.16
Date/Time: 2/2/2018 10:14:06 PM

1 6 ms 6 ms 6 ms 7 ms 18 ms 6 ms [10.233.97.36]
2 6 ms 11 ms 10 ms 11 ms 10 ms N/A [10.55.96.105]
3 51 ms 53 ms 49 ms 39 ms 33 ms N/A 103-10-124-246.valve.net [103.10.124.246]
4 104 ms 84 ms 81 ms 53 ms 55 ms N/A [192.168.152.13]
5 68 ms 70 ms 69 ms 61 ms 57 ms N/A [103.28.54.16]

Ping statistics for sgp-1.valve.net
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 57ms, Maximum = 70ms, Average = 65ms


Target Name: sgp-2.valve.net
IP: 103.10.124.1
Date/Time: 2/2/2018 10:14:59 PM

1 4 ms 6 ms 4 ms 9 ms 5 ms 6 ms [10.233.97.36]
2 8 ms 11 ms 13 ms 10 ms 10 ms 9 ms [10.55.96.105]
3 61 ms 48 ms 41 ms 33 ms 36 ms 37 ms 103-10-124-246.valve.net [103.10.124.246]
4 72 ms 66 ms 60 ms 65 ms 49 ms 55 ms sgp-2.valve.net [103.10.124.1]

Ping statistics for sgp-2.valve.net
Packets: Sent = 6, Received = 6, Lost = 0 (0.0%)
Round Trip Times: Minimum = 49ms, Maximum = 72ms, Average = 61ms


Target Name: N/A
IP: 45.121.184.1
Date/Time: 2/2/2018 10:15:19 PM

1 6 ms 6 ms 7 ms [10.233.97.36]
2 8 ms 11 ms 10 ms [10.55.96.105]
3 51 ms 54 ms 56 ms 103-10-124-246.valve.net [103.10.124.246]
4 73 ms 99 ms 95 ms [45.121.184.1]

Ping statistics for 45.121.184.1
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 73ms, Maximum = 99ms, Average = 89ms


Target Name: N/A
IP: 45.121.185.1
Date/Time: 2/2/2018 10:15:28 PM

1 6 ms 6 ms 6 ms [10.233.97.36]
2 8 ms 11 ms 10 ms [10.55.96.105]
3 49 ms 47 ms 45 ms 103-10-124-246.valve.net [103.10.124.246]
4 74 ms 75 ms 60 ms [192.168.152.13]
5 53 ms 45 ms 45 ms [45.121.185.1]

Ping statistics for 45.121.185.1
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 45ms, Maximum = 53ms, Average = 47ms

the ping issue has been fixed, around 20min after post and email it, pretty fast.