Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/18/2021 in all areas

  1. tdawnaz

    Hi TMN folk

    Rest in Paradise ROCO Movin on to greener pastures. Your presence will be missed. So sad to see you go my friend from across the pond! ??
    1 point
  2. CA3LE

    TestMy Latency... to anywhere.

    I opened up TestMy Latency for public testing about 2 weeks ago. Thousands of tests have been performed daily, thank you for the data and insight. It's really helped to button down the program. It wouldn't be able to test the way it does today without you just simply running those early tests and logging that information to my database. Today I was in the shower and thought, "Why not make it able to test anywhere..." --- cut myself shaving because I wanted to get to my computer so fast. So I added an ability that's hidden right now and I would love for you to test it. https://testmy.net/latency?internal=1&fa=1&addr=google.com https://testmy.net/latency?internal=1&fa=1&addr=facebook.com https://testmy.net/latency?internal=1&fa=1&addr=msn.com ... any address you want. It's going to show as "My Network" right now because it's barely built in there. If you query TML like this and it returns a result then you're testing against the host at addr=. From what I've seen it doesn't matter if the host is behind a CDN like cloudflare, it will punch right through that and get the real time to the host. For instance, a website I know is hosted in Australia, who's users have linked to TMN for decades >> forums.whirlpool.net.au I ping that using ICMP ping and I get Damons-5K-iMac:~ CA3LE$ ping forums.whirlpool.net.au PING forums.whirlpool.net.au (104.20.14.233): 56 data bytes 64 bytes from 104.20.14.233: icmp_seq=0 ttl=57 time=9.928 ms 64 bytes from 104.20.14.233: icmp_seq=1 ttl=57 time=9.410 ms 64 bytes from 104.20.14.233: icmp_seq=2 ttl=57 time=9.819 ms 64 bytes from 104.20.14.233: icmp_seq=3 ttl=57 time=9.808 ms 64 bytes from 104.20.14.233: icmp_seq=4 ttl=57 time=11.445 ms 64 bytes from 104.20.14.233: icmp_seq=5 ttl=57 time=9.191 ms 64 bytes from 104.20.14.233: icmp_seq=6 ttl=57 time=9.319 ms 64 bytes from 104.20.14.233: icmp_seq=7 ttl=57 time=9.396 ms 64 bytes from 104.20.14.233: icmp_seq=8 ttl=57 time=9.357 ms ^C --- forums.whirlpool.net.au ping statistics --- 9 packets transmitted, 9 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 9.191/9.741/11.445/0.650 ms Damons-5K-iMac:~ CA3LE$ (I can tell by the 104. address, don't even have to look it up, most likely cloudflare) That's the ping to the cloudflare proxy... not the actual forums.whirlpool.net.au server. but then I run that address with TML and get about 1 second delay. (sorry, can't share this like normal because it's not logging it to the database... again, this is a hidden function and I have to develop it further. There are blocks in the program preventing certain actions when it's outside of the scope it expects to see. Screenshots will have to do.) https://testmy.net/latency?internal=1&fa=1&https=1&addr=forums.whirlpool.net.au I do the same test to domains known to resolve in the US... Oops, I realize now that you need to add the &https=1 if the website is https. However, most will resolve both. https://testmy.net/latency?internal=1&fa=1&https=1&addr=google.com https://testmy.net/latency?internal=1&fa=1&https=1&addr=facebook.com https://testmy.net/latency?internal=1&fa=1&https=1&addr=msn.com by the way, facebook started responding slower on http also, wasn't just https. It's like it switched me to a different location. Actually, sharing does work as long as the address has less than 3 parts to it. "forums.whirlpool.net.au" won't save just because it has 4 parts to the address... I'll fix that. example embedded share https://testmy.net/latency?q=CA3LE&n=100&internal=1&fa=1&addr=testmy.net&stats=1 Help me understand what this can do, I'm figuring it out with you. Please run more tests and let me know what you find.
    1 point
×
×
  • Create New...