CA3LE

Reading the speed between their server and your computer is not really testing the internet speed. 
 
Doesn't matter how you connect.  You're not testing the Internet if you don't actually go out to the Internet.  Testing against your ISP's servers isn't going out to the Internet.  That's why TestMy.net is here.
 
Your ISP has control over the quality of peering and bandwidth in and out of their network.  
 
If your ISP is in the UK, then it should be a very quick hop over to my UK servers.  As long as your ISP is delivering that won't affect the final result.  There would be little to no difference if all the connections between are running with capacity available.  Any good ISP in that scenario would have at least multiple 10 GbE peers, meaning that the route between the ISP and TestMy.net should never be the weakest link... unless it's over capacity.
 
It's a red flag if an ISP tells you that only testing against their server's is accurate.  And like I said, it doesn't make sense in the first place.  Your ISP's servers are not the Internet, that's your host's network... before the Internet.  It's a part of the Internet but if that's your host, their network is your network.  A step above your local area network but we're not really out to the wider Internet.
 
TestMy.net is actually testing your connection out to the Internet.

11 October 2024
39º N 31º W

Hello 
Steven WJ Richards.
I hope you are well
 
My internet communications 10 to 15 years ago was unique in two ways.

The first one was done with ISP two satelite dIshes link with 210 meters on 80 meters self supported towers for ADSL distribution.

The second was earth to satelite geostationary orbit, at 35,786 km (22,236 mi) in altitude above Earth's equator to earth for ADSL distribution.I never mesured the latency but was high. The internet speed was 4Mbps and we paid for 12 Mbps.

Your internet is from 4G ?

What is your internet speed? 

What is the latency at TMN London Server (auto mode) ?

4G is better than ADSL.

Do you have sheep or goats in your paradise? and your antenna is safe from the animals ? 

I am also testing with TMN and this was my last results and observation:

Today, the Amazon Latency test at TMN and Ookla Speedtest is similar for London. We don't know if Amazon have servers in the countries with Shopps/Stores-Business ? 
 
All the tests below was done by wireless with ISP router and DNS. (5m from the router in a strait line)
  With warm Wi-Fi 5 on Intel modem AC 20-160Mhz on the PC and the router with 160 MHz bandwidth channel, 1733 Mhz all the results should be a little bit better.
We factory reset the router 4 times a year. 
  We use TMN server in London for speed test because it is closer to my router   
   
 
LINX LON1 - 195.66.224.91 - LINX LON2 - 195.66.236.91
 

 
I hope you answer my questions. 

Kind regards.
 

Hello Frank, thank you for your comprehensive and informative reply, it is much appreciated.  My internet connects to a radio transmitter tower across the Towy Valley about 2 miles away via a dish on my house. I am pleased to inform you that, since my last post, my internet provider has replaced the dish with an upgraded one. Here are my new speeds!!! 

Reading the speed between their server and your computer is not really testing the internet speed. 
 
Doesn't matter how you connect.  You're not testing the Internet if you don't actually go out to the Internet.  Testing against your ISP's servers isn't going out to the Internet.  That's why TestMy.net is here.
 
Your ISP has control over the quality of peering and bandwidth in and out of their network.  
 
If your ISP is in the UK, then it should be a very quick hop over to my UK servers.  As long as your ISP is delivering that won't affect the final result.  There would be little to no difference if all the connections between are running with capacity available.  Any good ISP in that scenario would have at least multiple 10 GbE peers, meaning that the route between the ISP and TestMy.net should never be the weakest link... unless it's over capacity.
 
It's a red flag if an ISP tells you that only testing against their server's is accurate.  And like I said, it doesn't make sense in the first place.  Your ISP's servers are not the Internet, that's your host's network... before the Internet.  It's a part of the Internet but if that's your host, their network is your network.  A step above your local area network but we're not really out to the wider Internet.
 
TestMy.net is actually testing your connection out to the Internet.

Hi Steven, welcome!
 
When you test at TestMy.net you're testing the connection from your home, through your providers network, out to the internet and then to my servers.
 
You only need to consider your own location when choosing one of my locations to test from.  Usually TMN will do a good job of choosing for you.
 
Based on your IP address, TMN would pick UK servers to test from.  You can also visit the Mirror page and quickly test your latency across all of the locations.  UK will again most likely perform the best (lowest).
 
After you're settled on a test server location then head over to the Auto Speed Test to schedule automatic testing.
 
Once you've gathered some results (data) visit My Results and My Average to get a better understanding of the results.
 
Hope this helps, please let me know if you have any other questions.

I see 1 results from today that was 140 Mbps... but very odd about the other ones.  I've never personally seen that happen to that degree before.
 
I'd really like to see how you run on the beta and what kind of charts it draws for your connection.
 
Click "My Settings" then toggle the beta ON.
 
Run a few combined tests.  Then visit Tune ☆ and toggle multithread ON.  Run a few more combined tests and hit me back so I can take a look.

Awesome  

Sorry for the inconvenience. 
 
I made a change to the code that should prevent that from happening again.  Please let me know if you have any other questions.
 
Happy Testing!
 

I love the music of Alannah Myles - Black Velvet

Using DNS in Singapore doesn't really help for your latency to the server.
 
Latency is like the time it takes for you to send a message to your friend and for them to respond. In the world of the internet, when you click on something or ask your computer to do something online, it sends a request to another computer far away. Latency is how long it takes for that request to reach the other computer and for you to get an answer back. If it takes a long time, everything online feels slow, like when you're waiting for someone to respond to a text.
 
When you ask your computer to load a website, it sends a message to another computer far away called a server. That server holds the information for the website you want. The message travels through wires, cables, or even space (if it’s using satellites!), and when the server gets it, it sends the website information back to your computer the same way. The time it takes for the message to go to the server and back to your computer is what we call latency. The quicker it travels, the faster things load!
 
You can't improve this unless you're able to take a shorter path to the server.  The physical distance creates unavoidable latency... the speed of light is the limiting factor.
 
What the Latency Test is showing you is that servers in Singapore will perform best for you.  Amazon is hosted on a CDN (content delivery network) so when you request using that test it pulls from a server closer to you automatically.
 
To improve latency over long distances, here’s how it works:
Use servers closer to you: Imagine a game of telephone. The closer the person, the quicker the message gets to you. Using servers that are closer (like a local one instead of one far away) speeds things up.
Optimize the route: Think of taking the quickest path home. By using smarter routes (like special internet paths called "content delivery networks"), the message travels faster, just like choosing a shortcut.
Use faster connections: Just like a fast car on a highway, using better internet connections helps the message travel quicker, even over long distances!

My beta gives anyone the ability to run TMN on any computer they'd like.  Run it locally on a Docker images I've prepared for you or install it on any web sever, with or without SSL.  It only takes 2 files, a total of 1800 bytes of code on your end.  What speed will you see between two wired 1 GbE?   Exactly what you'd expect to see, watch for yourself.
 
tmn-on-my-server.mp4
The Mac and Windows machines are fairly distant, non-direct routes.  The connection traverses 2 switches, then the router, then another switch also adding in about 100 ft of cable before it arrives.  Not lab conditions, I wanted all of those real world variables. 
 
If you inspect I think you'll agree, TMN's results are pretty exact. 
 
tl&dr

 
So average 916 Mbps | 904 Mbps.  Adding 6% network overhead you get to 971 Mbps | 958 Mbps.  Which is right in line with what we see coming across the interface in reality.  
 
I did the same LAN testing when developing the current version (v18) you're using now, always do.  But now I'm giving the ability to do it yourself, super quick.  ... I've also done that before but not like this.  This is very different.  Cut and paste a few commands into Terminal or PowerShell and you're running local tests on all your devices in a few seconds.  You can also audit all of the code and understand the entire container in just a few seconds.
 
Pretty excited to share that with you all.  Curious how people will use it.

The beta is now available to all members.  You'll find a toggle switch in My Settings.
 
Hope you find this helpful.

Instructions to Enable the Beta are in the Private area.
 
The beta is private but members with access are allowed to share instructions.
 
Please use this public forum for all threads related to Beta 23. 
 
If you encounter any issues or bugs please copy the URL in your browser and include it with your post.  This helps reproduce the issue.  Screen recordings are also very helpful.
 
Start new topic  
Happy Testing!

I use the my Internet Service Provider (ISP) DNS closer to my location on the router and sometimes on the computer DNS cloudflare: 1.1.1.1   1.0.0.1 on the computer.
https://www.cloudflare.com/learning/dns/what-is-1.1.1.1/
 
Some users prefer google 8.8.8.8  8.8.4.4 or Quad9 Security 9.9.9.9 

I like DNS Jumper V2.3 to find wich DNS is faster every hour and wich days of the week.

I hope this was useful. 

Just a query. Is the residential gateway/ modem provided by Spectrum?
If so is PC connected directly to that provided modem or passed through either a switch or isp extender device or perhaps a wall jack rj45 ethernet port using inside wire in the walls. 
Also if straight to router is there a port out of usually 4 or 5 grouped ports that are not of the same color or may even labeled as "1Gbps" some go higher when dealing with fastest speeds. Att and Comcast have equipment that use this
 
Internet speed on PC is largely hardware specific. gpu, cpu, memory, Network interface 
 
 
As a former tech for the Death Star I would bet its the top suggestions. Lasty the PC...but it is more common than you think of coming up shy.
 
820 on here is good on testmy I wouldn't fret

Turns out.... Its the ISP supplied WiFi 6e router ethernet interfaces..... thats a bummer... For anyone in the future this is the Spectrum branded SAX2V1S model. After connecting directly to the modem (should have been an obvious first step), I am easily able to get to and maintain the 1gbps internet speeds, see graph below. I will have to see about adding a hub or something in between. Thanks @spenceteeth
 

Using DNS in Singapore doesn't really help for your latency to the server.
 
Latency is like the time it takes for you to send a message to your friend and for them to respond. In the world of the internet, when you click on something or ask your computer to do something online, it sends a request to another computer far away. Latency is how long it takes for that request to reach the other computer and for you to get an answer back. If it takes a long time, everything online feels slow, like when you're waiting for someone to respond to a text.
 
When you ask your computer to load a website, it sends a message to another computer far away called a server. That server holds the information for the website you want. The message travels through wires, cables, or even space (if it’s using satellites!), and when the server gets it, it sends the website information back to your computer the same way. The time it takes for the message to go to the server and back to your computer is what we call latency. The quicker it travels, the faster things load!
 
You can't improve this unless you're able to take a shorter path to the server.  The physical distance creates unavoidable latency... the speed of light is the limiting factor.
 
What the Latency Test is showing you is that servers in Singapore will perform best for you.  Amazon is hosted on a CDN (content delivery network) so when you request using that test it pulls from a server closer to you automatically.
 
To improve latency over long distances, here’s how it works:
Use servers closer to you: Imagine a game of telephone. The closer the person, the quicker the message gets to you. Using servers that are closer (like a local one instead of one far away) speeds things up.
Optimize the route: Think of taking the quickest path home. By using smarter routes (like special internet paths called "content delivery networks"), the message travels faster, just like choosing a shortcut.
Use faster connections: Just like a fast car on a highway, using better internet connections helps the message travel quicker, even over long distances!

Using DNS in Singapore doesn't really help for your latency to the server.
 
Latency is like the time it takes for you to send a message to your friend and for them to respond. In the world of the internet, when you click on something or ask your computer to do something online, it sends a request to another computer far away. Latency is how long it takes for that request to reach the other computer and for you to get an answer back. If it takes a long time, everything online feels slow, like when you're waiting for someone to respond to a text.
 
When you ask your computer to load a website, it sends a message to another computer far away called a server. That server holds the information for the website you want. The message travels through wires, cables, or even space (if it’s using satellites!), and when the server gets it, it sends the website information back to your computer the same way. The time it takes for the message to go to the server and back to your computer is what we call latency. The quicker it travels, the faster things load!
 
You can't improve this unless you're able to take a shorter path to the server.  The physical distance creates unavoidable latency... the speed of light is the limiting factor.
 
What the Latency Test is showing you is that servers in Singapore will perform best for you.  Amazon is hosted on a CDN (content delivery network) so when you request using that test it pulls from a server closer to you automatically.
 
To improve latency over long distances, here’s how it works:
Use servers closer to you: Imagine a game of telephone. The closer the person, the quicker the message gets to you. Using servers that are closer (like a local one instead of one far away) speeds things up.
Optimize the route: Think of taking the quickest path home. By using smarter routes (like special internet paths called "content delivery networks"), the message travels faster, just like choosing a shortcut.
Use faster connections: Just like a fast car on a highway, using better internet connections helps the message travel quicker, even over long distances!

Don't know how I missed this topic.
 
I read it when it came in but I never responded, sorry dude.
 
I was thinking about the same thing as I was developing the beta... how it would be interesting to combine them together.
 
So along the way I developed it with that in mind for the future.  There are a couple of different ways I've imagined it can be done.  I think I'll just have to experiment in the real-world.
 
It's definitely coming.  Whether people understand it, use it, want it or care about it... that's another story.  But I think it would be a cool, unique tool... sounds like an interesting new benchmark.  One that will be hard to score well on unless you're connection is awesome. 
 
I think the most interesting part to me is that it's unknown.  I can kind of simulate what would happen but when it's actually a single process, I think it will yield interesting results.  A test whose results can only be compared to itself.
 
I'll let you know when it's ready to try.

Sorry for the inconvenience. 
 
I made a change to the code that should prevent that from happening again.  Please let me know if you have any other questions.
 
Happy Testing!
 

Thank you! it seems to be working great now!

This beta started as a request for a multithread upload test.  Funny and ironic that the hardest part to implement in this version was the Linear (single thread) Upload.
 
The "Linear" option has been removed and you'll now see a "Multithread" toggle under Tune ☆.  Multithread and Linear now work with both test types.
 
Hope you find this useful.

See those are super interesting 😊
 
At some point it would probably also be nice to use stacked bars as the histogram bars so you can e.g. also group by age.

ahhh, "My Average" is taking the last 25 results into consideration.  That's a direct copy of how it's currently done.
 
This also filters your results by identifier and host.  So when you're on Spectrum you'll get an average of only those results, when you're on Verizon you'll get an average of your Verizon results.  Same is true if you visit on a desktop, android or iOS.  You'll only compare similar results.
 
But that's only for "My Average" -- the ISP and location are taking into account all results and come from a continuous 15 minute average that runs for all databases.  Those numbers constantly fluctuate with the current average user's performance.

Yes and no... for right now.
 
For download it's enabled by default for upload it only works with multithread... until I push my next update. 
 
You may have already read this topic on it.  I got it fully working just last night.
 
 
As soon as the linear upload test is available in the beta, it will be the default option.  When you toggle the multithread option it will affect both upload and download tests.