Yup. Noticed sudden slowdown to US Servers. Currently running some tests to confirm where the issue is coming from. I can only suspect its Singtel is experiencing network congestion.

Very simple way to check if you are on public IP or not.

Login to your router. Take note of WAN IP address:


Then go and google : What is my IP


If both of these IPs match, congrats you are on Public IP.



This post has been edited by faizyunus: Apr 6 2023, 03:00 AM

Oh that is strange. My monitoring system still able to ping my network just fine.

Just out of curiosity, you mentioned ping your house public IP. Not sure if your router has this setting enabled or not?



Usually I will never leave this setting enabled. I only enable when troubleshooting network issue.

Alternatively you can go with ZeroTier for remote access needs. For my network I use both OpenVPN and ZeroTier. Never exposed my devices directly to the internet for security reasons.

Hopefully TIME manages to resolve your issue.

This post has been edited by faizyunus: Apr 6 2023, 01:26 PM

I see. That explains a lot. ISP provided routers have remote management which allow TIME to remotely configure the settings on the router.

Dynamic DNS is safe. Each router brand have their own set of Dynamic DNS providers that you can choose from so its hit or miss. Most would just run the client on their server/PC

I'm also experiencing slowdown accessing services hosted on UpCloud Servers in the US since last week. Fired up a server over there and ran a traceroute back to the TIME network and found the issue is likely caused by routing via Singtel because last time I checked it should route via NTT.

Already talked to both TIME CS and UpCloud Support with all the traceroute evidence. Both say no issue with routing and refuse to check any further.

Routing from TIME to UpCloud is routing via NTT so it looks ok.

However routing from UpCloud to TIME is routing via Singtel similar to previous occurrence back in January

Speeds I'm getting from UpCloud Chicago Servers:


This post has been edited by faizyunus: Jun 14 2023, 12:35 PM

Funny thing is I was having issue with TIME international routing back in June and January. Showed them evidence from my cloud provider that TIME is intentionally slowing down traffic and they refuse to do anything and kept blaming my cloud provider. Only when it was escalated to higher ups, only then they apologized and say cannot do anything about it. Switched to Allo after doing a bit of digging in regards to their upstream provider and slowness issue was immediately resolved.

This post has been edited by faizyunus: Oct 5 2023, 11:02 PM

No. I did not manage to escalate to any upstream provider as they will never respond to our emails. Only managed to escalate to the head of TIME CS where they finally admitted its their fault.

In regards to why I switched to Allo from TIME, I did a comparison between my cloud provider upstream provider and Allo's upstream provider and found one matching upstream provider, Cogent.

Ran a few traceroute and Speedtest.net CLI with help of my cloud provider, compared the results and found Allo & TM did not have the slowness issue. The most important thing for me is routing from US to Allo does not go through Singtel unlike TIME.

Below are some of the tests I ran from my end to cloud provider to Malaysia ISP. Since we are testing from Cloud Provider to Malaysia ISP, need to pay attention to their upload speed as this reflects our download speed.


Server: TIME MY - Kuala Lumpur (id: 50737)
ISP: UpCloud USA
Idle Latency: 222.12 ms (jitter: 278.90ms, low: 221.33ms, high: 778.09ms)
Download: 965.19 Mbps (data used: 1.5 GB)
456.87 ms (jitter: 87.18ms, low: 221.86ms, high: 1274.89ms)
Upload: 1.35 Mbps (data used: 2.4 MB)
379.59 ms (jitter: 82.17ms, low: 210.84ms, high: 1814.92ms)
Packet Loss: 6.3%
Result URL: https://www.speedtest.net/result/c/bd40b786...00-a1b0499d5a0d

root@faiztestserver-upcloud-us-chi1:~# speedtest -s 38751

Speedtest by Ookla

Server: Allo Technology - Cyberjaya (id: 38751)
ISP: UpCloud USA
Idle Latency: 224.45 ms (jitter: 0.08ms, low: 224.30ms, high: 224.53ms)
Download: 956.42 Mbps (data used: 1.4 GB)
346.29 ms (jitter: 78.47ms, low: 216.40ms, high: 482.85ms)
Upload: 408.33 Mbps (data used: 554.4 MB)
315.84 ms (jitter: 76.41ms, low: 210.94ms, high: 421.30ms)
Packet Loss: 0.0%
Result URL: https://www.speedtest.net/result/c/45205216...e9-2e5f1c0dea3d


Server: Telekom Malaysia Berhad - Kuala Lumpur (id: 19302)
ISP: UpCloud USA
Idle Latency: 225.20 ms (jitter: 1.23ms, low: 224.31ms, high: 227.02ms)
Download: 967.58 Mbps (data used: 1.4 GB)
379.37 ms (jitter: 80.42ms, low: 224.83ms, high: 538.81ms)
Upload: 374.70 Mbps (data used: 438.6 MB)
332.67 ms (jitter: 77.59ms, low: 222.09ms, high: 444.03ms)
Packet Loss: 0.0%
Result URL: https://www.speedtest.net/result/c/3038b947...cc-747f4d70029d

This post has been edited by faizyunus: Oct 6 2023, 12:09 AM

No issue connecting to all 3 of their Speedtest.net Servers

Yup. Same thing happening with Allo since they also use NTT as Upstream provider





Luckily cloud provider was able to change routing to their other upstream, Cogent within 24 hours of reporting the issue.

Not at all. Many ISPs use similar upstream providers with exception of big ISP like TM. Depending on which routing they choose to advertise, your experience may vary when accessing your favourite sites/game server etc.

What I'm showing is speedtest and traceroute from my cloud provider to my current ISP, Allo City Broadband which was having slowness issue because of NTT routing similar to what TIME uses.

I was just lucky that my cloud provider was able to change the routing to Allo's other upstream provider, Cogent which resolved the issue.

Since these routing issues happen every now and then, I have created a script that I can give to any cloud provider to run on their servers which will auto run Traceroute and speedtest-cli to Allo City Broadband Speedtest.net servers. This speeds up troubleshooting on their end.

You will need to do your homework before committing to any ISP. Generally, any ISP is ok for general use. The only other factor, is your budget.

Feel free to ask around and we will be glad to share our experience

This post has been edited by faizyunus: Feb 1 2024, 08:19 PM

Totally agree. I left TIME last year after experiencing similar issue for months and their canned response from both their CS and technical team. Never looked back after that.

This post has been edited by faizyunus: May 11 2024, 01:17 PM

Currently using Allo City Broadband (AS45410) since I have a lot of choice here in Cyberjaya. I wish other areas have more choice of fibre ISPs as well. MCMC should mandate this and also provide incentive to do so.

Their upstream providers are NTT and Cogent so no more dealing with TIME's upstream provider, Singtel.

https://bgpview.io/asn/45410#upstreams-v4

Their public IP users doesn't use PPPOE but uses IPOE meaning less overhead.

Here is my ping to Twitter using Allo City Broadband:



This post has been edited by faizyunus: May 11 2024, 03:49 PM

Implemented similar thing as well. If Allo have routing issue, I can reroute affected traffic to my parent's UniFi via OpenVPN/WireGuard and same goes if my parent's UniFi having routing issue, I can easily reroute their affected traffic to my Allo.

This proved useful when I was using TIME previously.

This post has been edited by faizyunus: May 11 2024, 09:07 PM

One way to find out is go to https://myip.expert/ to get the ASN number then use that ASN number at https://bgpview.io to see its upstream providers.

This post has been edited by faizyunus: May 3 2025, 10:22 AM

Wow. Only one upstream provider. That means if got routing issue, then there is nothing much your ISP can do.