I set up an automated speedtest measurement and recording system, it runs every 15 minutes for 24/7 and has been running for the past 16 days so that works out to be over 1,500 tests.

This is what I see:


I'm subscribed to 500mbps package but I seem to be artificially limited to 300mbps most of the time. The spikes that you see when I get 500mbps are always because I either restarted my router or when TM resets my connection after I make a complaint. However, the graph shows that my speeds get reduced back down to 300mbps shortly after that - sometimes it could last 2 days, sometimes only a few hours.

I've made complaints to TM several times and every time they "reset my port", the speed goes back to normal and they declare that they solved my problem so there's no avenue for me to escalate further.

Is this the work of TM or is it caused by something else?

If TM tells me there is a widespread slowdown due to MCO or whatever I can still accept, but the data here suggests that it is a very specific situation where my bandwidth is capped after a while, and the remedy (reset port / restart router) is made to look like it has resolved the problem only for the cap to return when the case is closed.

99.5% local servers. Sometimes the automated server picks a server in Indonesia but only happened a few times.

I'm sure I've disabled QoS on my end. I just want to rule out all possibilities that it is caused by anything on my end.

If you suddenly get good speeds after you restart your router, then it may be an indication that you're facing the same thing.

This post has been edited by [-]: Jul 14 2021, 06:21 PM

I don't quite believe this is caused by congestion though. Have a look at the graph, the variance is very small. It is either 500+/-mbps or 300+/-mbps with almost nothing in between. It has also never dropped below 300mbps either. It looks like an artificial cap.

I have logs that show the speedtests were performed using local servers and I can set a static server if I wanted to, but I feel there should be some randomness in choosing the servers.

If the connection cannot even maintain a consistent speed across a few local servers, then it is simply not reliable.

Please correct me if I have the wrong understanding, but the "short bursts" that you're seeing in the graph are not really short. That graph shows data over 16 days so the spikes that look like bursts are in fact over a period of few hours up to few days. That is to say, I can sustain consistent 500mbps speeds over a few hours/days, then it will suddenly drop.

I did not automate the speedtest to run purely on TM server, but I did manual verification when reporting to TM:

Referring to my graph? I'm not sending any files. That graph represents the results of speedtest in mbps.