HubCity Posted January 7, 2013 CID Share Posted January 7, 2013 When i logged on today to check my speed, there was no selection for Central, Western, Eastern locations, only test size selections. The test location was useful in determining bottlenecks of my ISP with traceroutes to different parts of the country. What is the TMN location now, Houston, TX...?? thanks Quote Link to comment Share on other sites More sharing options...
HubCity Posted January 7, 2013 Author CID Share Posted January 7, 2013 Nevermind, I found it listed in very small text across the top of the page. Before it was displayed when I selected the download test. Quote Link to comment Share on other sites More sharing options...
CA3LE Posted January 7, 2013 CID Share Posted January 7, 2013 Sorry, I should have put something there... Selection is now only at the top of the Speed Test pages. When you test with the default location now you are routed through one of 23 datacenters world wide. If you ping or run a traceroute to TestMy.net you'll now see that no matter where you are... you should have low latency. You can still select the server for troubleshooting but most will find that the distributed networking option will provide highly accurate results. See my traceroutes below. The home server has a 57 ms ping to me in Phoenix, after distribution it drops to 21 ms because it's being served closer. This is all done automatically. I believe the Internet will be served this way more and more in the future so I'm adopting the framework for TestMy.net. I have 4 other CDNs online, including one delivered by Google that was invitation only. But I haven't released them publicly yet. ... increasingly this is the way that your content is being delivered to you. So that's the way I'm going to deliver my tests. iMac:~ ca3le$ traceroute testmy.net traceroute: Warning: testmy.net has multiple addresses; using 199.27.135.63 traceroute to testmy.net (199.27.135.63), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 3.285 ms 1.199 ms 1.146 ms 2 10.34.96.1 (10.34.96.1) 9.878 ms 8.277 ms 8.293 ms 3 172.21.0.126 (172.21.0.126) 10.200 ms 10.224 ms 11.873 ms 4 70.169.73.196 (70.169.73.196) 15.315 ms 12.056 ms 12.052 ms 5 70.169.75.157 (70.169.75.157) 9.432 ms 10.342 ms 10.152 ms 6 * * * 7 ae12.ar1.lax1.us.nlayer.net (69.31.127.229) 23.045 ms 27.111 ms 24.574 ms 8 as13335.xe-11-0-6.ar1.lax1.us.nlayer.net (69.31.125.106) 23.272 ms as13335.xe-9-0-7.ar1.lax1.us.nlayer.net (69.31.127.62) 22.664 ms as13335.xe-11-0-6.ar1.lax1.us.nlayer.net (69.31.125.106) 23.026 ms 9 cf-199-27-135-63.cloudflare.com (199.27.135.63) 21.506 ms 21.862 ms 22.241 ms iMac:~ ca3le$ traceroute central.testmy.net traceroute to central.testmy.net (174.120.187.140), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 2.112 ms 1.106 ms 1.024 ms 2 10.34.96.1 (10.34.96.1) 8.113 ms 7.969 ms 10.140 ms 3 172.21.0.126 (172.21.0.126) 10.197 ms 9.504 ms 9.710 ms 4 70.169.73.196 (70.169.73.196) 11.726 ms 11.722 ms 12.072 ms 5 70.169.75.157 (70.169.75.157) 33.757 ms 9.050 ms 10.187 ms 6 paltbprj01-ae0.0.rd.pt.cox.net (68.1.0.234) 47.703 ms 48.351 ms 55.982 ms 7 xe-1-0-0.bbr01.eq01.pal01.networklayer.com (50.97.16.17) 43.862 ms 44.402 ms 37.630 ms 8 ae3.bbr02.eq01.sjc02.networklayer.com (173.192.18.242) 39.236 ms 40.419 ms 47.251 ms 9 ae0.bbr02.cs01.lax01.networklayer.com (173.192.18.151) 52.768 ms 57.575 ms 53.123 ms 10 ae7.bbr01.cs01.lax01.networklayer.com (173.192.18.166) 58.174 ms 63.559 ms 50.922 ms 11 ae19.bbr01.eq01.dal03.networklayer.com (173.192.18.140) 60.216 ms 129.928 ms 51.046 ms 12 po31.dsr02.dllstx3.networklayer.com (173.192.18.227) 59.449 ms 61.902 ms po31.dsr01.dllstx3.networklayer.com (173.192.18.225) 52.768 ms 13 po32.dsr02.dllstx2.networklayer.com (70.87.255.70) 56.194 ms po31.dsr01.dllstx2.networklayer.com (70.87.255.66) 59.251 ms po32.dsr02.dllstx2.networklayer.com (70.87.255.70) 56.928 ms 14 po12.car15.dllstx6.networklayer.com (70.87.255.14) 58.598 ms 57.428 ms 58.715 ms 15 8c.bb.78ae.static.theplanet.com (174.120.187.140) 56.678 ms 58.255 ms 57.197 ms iMac:~ ca3le$ traceroute west.testmy.net traceroute to west.testmy.net (50.23.138.74), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 1.386 ms 1.095 ms 1.150 ms 2 10.34.96.1 (10.34.96.1) 9.237 ms 9.570 ms 9.442 ms 3 172.21.0.126 (172.21.0.126) 8.795 ms 9.818 ms 9.685 ms 4 70.169.73.196 (70.169.73.196) 17.495 ms 11.736 ms 12.146 ms 5 70.169.75.157 (70.169.75.157) 11.365 ms 12.027 ms 10.100 ms 6 paltbprj01-ae0.0.rd.pt.cox.net (68.1.0.234) 57.552 ms 47.324 ms 93.671 ms 7 xe-1-0-0.bbr01.eq01.pal01.networklayer.com (50.97.16.17) 45.680 ms 44.219 ms 45.715 ms 8 ae3.bbr01.eq01.sjc02.networklayer.com (173.192.18.240) 49.499 ms 49.354 ms 69.591 ms 9 ae0.bbr02.wb01.sea02.networklayer.com (173.192.18.146) 63.117 ms 57.352 ms 57.199 ms 10 ae1.dar01.sr01.sea01.networklayer.com (173.192.18.143) 66.962 ms 78.051 ms 66.784 ms 11 po2.fcr01.sr01.sea01.networklayer.com (67.228.118.138) 88.075 ms po1.fcr01.sr01.sea01.networklayer.com (67.228.118.134) 57.257 ms 61.873 ms 12 50.23.138.74-static.reverse.softlayer.com (50.23.138.74) 66.034 ms 60.512 ms 66.062 ms iMac:~ ca3le$ traceroute dc.testmy.net traceroute to dc.testmy.net (184.173.139.122), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 2.423 ms 1.067 ms 1.056 ms 2 10.34.96.1 (10.34.96.1) 9.101 ms 12.708 ms 9.046 ms 3 172.21.0.126 (172.21.0.126) 11.280 ms 12.058 ms 11.748 ms 4 70.169.73.196 (70.169.73.196) 20.821 ms 11.668 ms 12.027 ms 5 mcdldsrj01-ae2.0.rd.ph.cox.net (70.169.76.225) 9.685 ms 12.191 ms 11.974 ms 6 paltbprj01-ae0.0.rd.pt.cox.net (68.1.0.234) 48.186 ms 49.254 ms 41.721 ms 7 xe-1-0-0.bbr01.eq01.pal01.networklayer.com (50.97.16.17) 38.047 ms 62.949 ms 45.078 ms 8 ae3.bbr01.eq01.sjc02.networklayer.com (173.192.18.240) 44.867 ms 51.978 ms 43.854 ms 9 ae0.bbr02.cs01.den01.networklayer.com (173.192.18.149) 61.068 ms 54.588 ms 65.459 ms 10 ae0.bbr02.eq01.chi01.networklayer.com (173.192.18.130) 76.394 ms 79.597 ms 97.482 ms 11 ae0.bbr02.eq01.wdc02.networklayer.com (173.192.18.154) 96.364 ms 88.361 ms 84.438 ms 12 ae1.dar01.sr01.wdc01.networklayer.com (173.192.18.193) 88.499 ms 87.108 ms 93.199 ms 13 po1.fcr03.sr02.wdc01.networklayer.com (208.43.118.157) 94.361 ms po2.fcr03.sr02.wdc01.networklayer.com (208.43.118.159) 117.443 ms 94.017 ms 14 184.173.139.122-static.reverse.softlayer.com (184.173.139.122) 103.051 ms 104.588 ms 102.039 ms iMac:~ ca3le$ traceroute eu.testmy.net traceroute to eu.testmy.net (5.10.86.18), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 1.192 ms 1.044 ms 1.071 ms 2 10.34.96.1 (10.34.96.1) 9.799 ms 11.571 ms 8.235 ms 3 172.21.0.126 (172.21.0.126) 28.215 ms 10.273 ms 11.246 ms 4 70.169.73.196 (70.169.73.196) 14.609 ms 11.947 ms 23.483 ms 5 mcdldsrj01-ae2.0.rd.ph.cox.net (70.169.76.225) 12.433 ms 21.764 ms 14.776 ms 6 paltbprj01-ae0.0.rd.pt.cox.net (68.1.0.234) 50.114 ms 50.589 ms 43.712 ms 7 xe-1-0-0.bbr01.eq01.pal01.networklayer.com (50.97.16.17) 38.012 ms 39.866 ms 46.007 ms 8 ae3.bbr01.eq01.sjc02.networklayer.com (173.192.18.240) 51.497 ms 49.641 ms 50.066 ms 9 ae0.bbr02.cs01.den01.networklayer.com (173.192.18.149) 60.443 ms 64.058 ms 75.982 ms 10 ae0.bbr02.eq01.chi01.networklayer.com (173.192.18.130) 69.506 ms 76.366 ms 75.386 ms 11 ae7.bbr01.eq01.chi01.networklayer.com (173.192.18.170) 71.782 ms 79.647 ms 76.326 ms 12 ae0.bbr02.tl01.nyc01.networklayer.com (173.192.18.133) 98.510 ms 120.431 ms 97.128 ms 13 ae0.bbr01.tg01.lon01.networklayer.com (50.97.18.205) 165.680 ms 165.720 ms 160.004 ms 14 ae7.bbr02.tg01.lon01.networklayer.com (50.97.18.207) 167.460 ms 174.570 ms 168.164 ms 15 ae0.bbr02.eq01.ams02.networklayer.com (50.97.18.211) 170.093 ms 172.611 ms 162.984 ms 16 ae6.dar01.sr01.ams01.networklayer.com (50.97.18.249) 172.739 ms ae6.dar02.sr01.ams01.networklayer.com (50.97.18.251) 169.059 ms 169.389 ms 17 po1.fcr01.sr01.ams01.networklayer.com (159.253.158.131) 164.693 ms 173.551 ms 169.762 ms 18 5.10.86.18-static.reverse.softlayer.com (5.10.86.18) 184.674 ms 171.326 ms 163.366 ms You'll see on the homepage... What makes TestMy.net Different? Routing Distribution Along side its own network of servers TestMy.net uses CloudFlare global network to provide this service as close to you as possible while still being outside of your Internet providers network. If you suspect a connection issue try testing from another location, this can help diagnose whether an issue is due to routing or if it has to do with your home network and/or computer itself. Select a test location at the top of any of the speed test pages. I've added some text where those server selection buttons used to be so that people aren't confused. Thanks for pointing that out. Quote Link to comment Share on other sites More sharing options...
Pgoodwin1 Posted January 8, 2013 CID Share Posted January 8, 2013 CA3LE....do you recommend that we put the test server location on "Automatic" now to get the most realistic results? This evening (and a few evenings ago) I was getting significantly higher download speeds using the Washington DC server. I'm in Cincinnati, OH. I used to leave it on the Central (Dallas) server - it was called my default. This evening, when I chose the Central server, the page wouldn't open (got a server not found error). don't know if that was just a temporary outage or not. It was working on Central earlier today. I'll try clearing my browser History and try again. Just a note...Clearing the iPad Safari history didn't bring the Central server back. Quote Link to comment Share on other sites More sharing options...
CA3LE Posted January 8, 2013 CID Share Posted January 8, 2013 I'm using the automatic myself. It just helped me tune my wifi. Just today I got a wifi range extender and used TestMy.net on the auto route to fine tune the best location for it. Worked like a charm. The DNS may need to update for you. Ping central.testmy.net... once you can ping that you can test from that server. I should have waited for DNS to fully propagate before turning that on... but oh well. You can also try "dscacheutil -flushcache" from terminal on Mac to flush your DNS cache. (On Windows type "ipconfig /flushdns" in the command prompt). Quote Link to comment Share on other sites More sharing options...
Pgoodwin1 Posted January 8, 2013 CID Share Posted January 8, 2013 Thanks. Quote Link to comment Share on other sites More sharing options...
Pgoodwin1 Posted January 10, 2013 CID Share Posted January 10, 2013 CA3LE. There's something odd/different about the Dallas server from a couple of weeks ago. I mentioned above that my iPad Safari couldn't find the server when I selected Central. when I select East Coast, and use the Test Now button on the testmy nome page, it runs fine. I actually am getting speeds using the East Coast server that are consistently about 50% to 90% higher than I've typically gotten on the Central server over the past year. As for the Central server, after rebooting my cable modem, and my Router, and after flushing Cookies and Data on the iPad, I was able to connect to the Central server. I ran a few combined tests, and the speeds were about 25% lower than what I used to see on that server. Then I went back to the East Coast server and got the higher speeds I was seeing earlier. Then I selected the Central server again. And Safari again said the server couldn't be found. I flushed the cookies and data again but that didn't fix it. I've never had this happen in the past. Any thoughts? above I called the Home page test button the "Test Now" button. It's actually called the "Test My Speed" Button. I use that, then use the Re-Test button in the current test results page for another test. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.