Leaderboard

Alright, it's only on one server right now and you have to manually call upon it with a URL. I'll make sure this becomes an option everyone can easily use. https://co.testmy.net/SmarTest/down - https://co.testmy.net/SmarTest/up (or add https to any of the common test URLs e.g. https://co.testmy.net/SmarTest/combinedAuto - https://co.testmy.net/dl-1MB and https://co.testmy.net/ul-1MB) I'll let you know when I duplicate this across the network. Thanks for the suggestion.

Well maybe all the Notifying Google of the "Aw Snap" BS worked as I finally was able to run a combined test and did not get that annoying message just a few seconds ago.

One issue I'm noticing now and again particularly with mobile broadband providers is that some treat http and https traffic differently. A good example I posted a while back is where the 3 Ireland mobile provider was providing considerably quicker throughput with https traffic than http traffic. Before my recent trip to California, I bought a 3UK 1GB prepay SIM so I could use data on my phone during my trip as it does not have roaming charges in the USA. While this worked for most of my trip, I noticed some websites were incredibly slow to load. When I was back in Ireland, I did some further tests with that SIM with the remaining data credit and sure enough it was a similar issue here also and found that any website using https including Three's own website took a very long time to load. When I tried YouTube (which uses https), it would play a grainy picture for a few seconds, then buffer for a while and repeat. Yet when I ran a speed test, I kept getting 6Mbps to 10Mbps with TestMy, which is carried out over http. Other streaming services were practically unusable and even a 128kbps streaming radio station could not play without endlessly rebuffering. So while it's pretty clear Three UK throttles pretty much everything besides plain http traffic when roaming on a 3 like home network, I would be curious to actually run a speed test on a https connection just to see what limited bandwidth they are throttling down to. I could not find any other site that performs such tests, yet it seems to be a pretty common search going by Google's autocomplete: So I assume there must be some interest in such a test.

You shouldn't get the warnings anymore, as long as you've accepted the cert on both testmy.net and the server you've selected. You can now visit https://testmy.net and it will work with all servers. Let me know if you have any problems. Later I'll make a way to differentiate the tests taken with ssl (https) in the database.

This post requires a +1 like times ten interwebz button

DEAR SIRS Can we change the time from local time to UTC time? Thanks.

Have you used the testmy.net multithreaded tests? With this tool, you can set specific server locations to further pin point the slow connection. Interesting idea ISP's have on their placement of said flash speed tests, as they are a direct link from you, simply to them. Which does not at all show any representation of what speeds the end user has the ability to achieve, in real world applications. Who knows what type of configuration filters are set, after the speed testing node at the ISP. Many, for certain. You'll see peering issues come out when attempting to stream, or the specific QOS settings they might give to timeframes, or vendors across the network. Furthermore , the ISP is specifically looking for issues within it's own network, and completely ignore who they are peered with, which is some of the most vital connections on the net itself.

I'll work on this for you.

One likely issue that's going on is high latency or jitter in the connection. For example, as the packets are being streamed to and from the ISP, some could be arriving much later or earlier than other packets. While most streaming services such as YouTube can handle this as they buffer the connection, with video calls, any packets that arrive out of sequence are effectively dropped as the video needs to be shown in real time, in turn resulting in the picture stuttering. To test how stable your connection is while it's idle, bring up a command prompt and running: ping -t 8.8.8.8 The ping results should be fairly consistent and stay below 100ms like the following. Make sure there is nothing in the background using the connection, i.e. nothing downloading or uploading. The '-n 100' in my screenshot just means to ping 100 times instead of continuously for '-t'. I would suggest monitoring this for a minute or two in case there is an intermittent hiccup. If the ping results fluctuate about the place, then it's quite possibly high contention on your ISP or something within your home network using the connection, such as a phone (e.g. I've come across game apps that continuously use the connection in the background). To stop the ping test and see the results, press Ctrl + C. The next time you start a video call, run this ping test again with the video call active. If the ping times start jumping about the place, then it's a latency/jitter issue with the connection. While it could be possible the router may be causing this, it's more likely caused by contention within the ISP. The following is an example with my fixed wireless connection. Basically the area highlighted in red would have resulted in broken up video/voice had I been on a call: