nivleK1985
Senior Member
- Joined
- Feb 20, 2005
- Messages
- 1,710
- Reaction score
- 0
There's no foul play but merely issues that both MR and Singtel needs to iron out, a few users and I have feedback speed and ping issues to Singtel for weeks now but no response no nothing. I have discovered the same issues when I do remote desktop for my clients and the speed always varies from hours to hours. You have to pray for a good time to have the connection be up and working properly.
Yet calling the MR hotline is a nightmare, so much for expanding the team. Waited 30mins on a normal business hour and still no one picks up the damn phone, I just had to try my luck putting it on loudspeaker and leaving it by the side of my desk while working, sucks to be proven right.
Both taken on different timing. Even when the speed is working the ping is ridiculously off.
![]()
![]()
I wouldn't go the extent of suggesting foul play or talk about conspiracy theories, but what the MR team needs to do right now is to LOOK into the issues people are raising up and also to stop being so selective at picking out questions and issues from us consumers.
What is wrong with your hotline support exactly and what happened to the forum presence? There is practically none right now. Got issues, can't get through to your hotline, no one picks up; bringing it up on the forum yields no response, your live chat is bad. Do we have to resort to emailing you guys every single time there's issue that can be easily look into and to keep your customers in the loop?
The funny thing is when I called Singtel to check up on this, they actually did their part and tried to call MR as well but they told me, can't get through at all.
To my knowledge. The Singtel backend staff has direct contact information to our team. Thus, there's no reason for them to be calling the main hotline or "can't get through to us at all".
However, it is indeed weird that Singtel speed is extremely slow. It seems the download is being limited.
Traceroute has started…
traceroute to info.singtel.com (203.127.23.38), 64 hops max, 72 byte packets
1 my.router (192.168.1.1) 2.016 ms 0.400 ms 0.300 ms
2 172.28.0.1 (172.28.0.1) 3.134 ms 2.712 ms 3.506 ms
3 103-6-148-49.myrepublic.com.sg (103.6.148.49) 60.375 ms 4.152 ms 3.024 ms
4 myr-0001.asianetcom.net (203.192.154.153) 5.095 ms 4.639 ms 4.074 ms
5 te2-1.502.arc005.sin3.pacific.net.sg (192.169.32.33) 5.097 ms 8.545 ms 5.232 ms
6 ge1-1-1.dcr1.sin7.pacific.net.sg (192.169.32.209) 22.754 ms 33.523 ms 3.936 ms
7 gi0-1-0.dgw2.sin5.pacific.net.sg (192.169.32.78) 8.396 ms 10.874 ms 7.275 ms
8 165.21.49.126 (165.21.49.126) 38.086 ms 38.836 ms 37.700 ms
9 203.125.232.130 (203.125.232.130) 40.889 ms 40.894 ms 41.035 ms
10 203.127.23.38 (203.127.23.38) 93.216 ms 94.041 ms 93.944 ms
Traceroute result seems to point out the jump only occur after it enter 165.21.49.126
According to whois - http://www.whoisstuff.net/ip-lookup.php?domain=165.21.49.126
It belongs to Singtel backend. Regardless, we are happy to work with Singtel to see how we can resolve their issue
Last edited: