New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Do a ping and help improve load balancing algorithm
I am currently trying to improve the load balancing algorithm for jsDelivr CDN.
For this I could really use some data from all of you.
Ping cdn.jsdelivr.net and post results like this:
Your IP - Your IPs Country or US State - Result IP
Feel free to ping from multiple servers or your home, the more the better.
Thank you
P.S If anyone wants to help with important data he can integrate this javascript
Comments
From the Netherlands
Pinging jsdelivr3.dak.netdna-cdn.com [108.161.188.124] with 32 bytes of data: Reply from 108.161.188.124: bytes=32 time=13ms TTL=56 Reply from 108.161.188.124: bytes=32 time=13ms TTL=56 Reply from 108.161.188.124: bytes=32 time=16ms TTL=56 Reply from 108.161.188.124: bytes=32 time=18ms TTL=56 Ping statistics for 108.161.188.124: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 18ms, Average = 15msSouth Bend, IN
France
Lombard, IL
Norfolk, England.
UK
Pauls-MacBook-Pro:~ prae$ ping cdn.jsdelivr.net
PING 531151672.r.worldcdn.net (109.123.117.122): 56 data bytes
64 bytes from 109.123.117.122: icmp_seq=0 ttl=53 time=24.161 ms
64 bytes from 109.123.117.122: icmp_seq=1 ttl=53 time=22.515 ms
64 bytes from 109.123.117.122: icmp_seq=2 ttl=53 time=26.567 ms
64 bytes from 109.123.117.122: icmp_seq=3 ttl=53 time=26.078 ms
64 bytes from 109.123.117.122: icmp_seq=4 ttl=53 time=23.690 ms
64 bytes from 109.123.117.122: icmp_seq=5 ttl=53 time=25.437 ms
^C
--- 531151672.r.worldcdn.net ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.515/24.741/26.567/1.414 ms
Pauls-MacBook-Pro:~ prae$
Atlanta, GA, USA
root@site [/]# ping cdn.jsdelivr.net
PING jsdelivr3.dak.netdna-cdn.com (108.161.188.124) 56(84) bytes of data.
64 bytes from 108.161.188.124: icmp_seq=1 ttl=60 time=0.364 ms
64 bytes from 108.161.188.124: icmp_seq=2 ttl=60 time=0.208 ms
64 bytes from 108.161.188.124: icmp_seq=3 ttl=60 time=0.213 ms
64 bytes from 108.161.188.124: icmp_seq=4 ttl=60 time=0.211 ms
64 bytes from 108.161.188.124: icmp_seq=5 ttl=60 time=0.220 ms
64 bytes from 108.161.188.124: icmp_seq=6 ttl=60 time=0.217 ms
64 bytes from 108.161.188.124: icmp_seq=7 ttl=60 time=0.217 ms
64 bytes from 108.161.188.124: icmp_seq=8 ttl=60 time=0.274 ms
64 bytes from 108.161.188.124: icmp_seq=9 ttl=60 time=0.227 ms
64 bytes from 108.161.188.124: icmp_seq=10 ttl=60 time=0.227 ms
^C
--- jsdelivr3.dak.netdna-cdn.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9340ms
rtt min/avg/max/mdev = 0.208/0.237/0.364/0.049 ms
root@site [/]#
Pinging 531151672.r.worldcdn.net [42.1.61.124] with 32 bytes of data: Reply from 42.1.61.124: bytes=32 time=130ms TTL=51 Reply from 42.1.61.124: bytes=32 time=110ms TTL=51 Reply from 42.1.61.124: bytes=32 time=131ms TTL=51 Reply from 42.1.61.124: bytes=32 time=112ms TTL=51 Reply from 42.1.61.124: bytes=32 time=138ms TTL=51 Reply from 42.1.61.124: bytes=32 time=128ms TTL=51 Ping statistics for 42.1.61.124: Packets: Sent = 6, Received = 6, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 110ms, Maximum = 138ms, Average = 124msIP: 180.215.x.x
India
From just-ping.com:
Give us a list of PoPs (preferrably with a map) so we can decide if we are indeed hitting the closest PoP or not.
Here: http://www.jsdelivr.com/network.php
I host a PoP for @jimaek but it looks like I'm hitting NetDNA Chicago from within the same facility that the PoP is hosted in South Bend, IN.
Thanks, found the list of PoPs but no IP addresses to ping...
Hey, I am not sure if its wise to give the exact list of the IPs of all custom POPs.
@zfedora The lack of data does that. NetDNA has more benchmarks from this script than your new server.
I am not sure either, but i get IP 108.161.188.124, which appears to be in Amsterdam, the Netherlands. Yet I am in Bulgaria and looking at the map, pure geographicly the PoPs in Greece, Romania, Hungary, Croatia, The Czech Republic, Germany and some other should be closer to me. Don't know about the ping.
Just tested some of the IPs that just-ping.com reveals - it seems that this IP
87.229.127.230 in Hungary is the lowest ping for me.
@rds100 Believe me geographically closest is not always the fastest. If you want I can send you a list of EU IPs to test out and if something is faster then I will make the change the globally.
Brisbane, AU:
From the UK, on my phone (with a poor signal (and retyped because Terminal won't let me copy and paste))
yeah, i typed that out.
95.154.245.253, United Kingdom, 162.216.224.144.
Seems like there's some AnyCast too.
This is a bug. Noted and will look into it. Thanks
Please try again pinging cdn.jsdelivr.net
It's actually worse now - goes to Romania, Voxility. And Voxility and peering... meh.
Reply from 67.214.167.238: bytes=32 time=71ms TTL=53. Pretty bad for canada.
37.157.198.193 - the Czech Republic - 108.161.188.124 (apparently in the Netherlands):
rtt min/avg/max/mdev = 37.435/37.512/37.648/0.251 ms
There is a POP in Prague (CZ) which has to be better since the ping to Prague DCs looks like this:
rtt min/avg/max/mdev = 3.291/3.335/3.398/0.069 ms
And my request to 108.161.188.124 is routed through a Prague peering anyway.
From Frankfurt, Germany @ Global Switch:
@MiB @agoldenberg I sent you both messages.
If anyone else wants to help you can still submit pings.
Thanks
From New Mexico:
Pinging jsdelivr3.dak.netdna-cdn.com [108.161.188.124] with 32 bytes of data:
Reply from 108.161.188.124: bytes=32 time=31ms TTL=54
Reply from 108.161.188.124: bytes=32 time=36ms TTL=54
Reply from 108.161.188.124: bytes=32 time=32ms TTL=54
Reply from 108.161.188.124: bytes=32 time=33ms TTL=54
Tennessee:
Pinging jsdelivr3.dak.netdna-cdn.com [108.161.188.124] with 32 bytes of data: Approximate round trip times in milli-seconds: Minimum = 26ms, Maximum = 29ms, Average = 27msNew York:
PING 531151672.r.worldcdn.net (209.190.64.15) 56(84) bytes of data. --- 531151672.r.worldcdn.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 22.582/22.621/22.653/0.191 msPhoenix:
PING azza-ja.jsdelivr.net (162.216.152.175) 56(84) bytes of data. --- azza-ja.jsdelivr.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 64.435/64.587/64.798/0.199 msDataShack (Kansas City, MO)
From Auckland, New Zealand
Pinging 531151672.r.worldcdn.net [103.29.84.13] with 32 bytes of data:Reply from 103.29.84.13: bytes=32 time=86ms TTL=51Reply from 103.29.84.13: bytes=32 time=79ms TTL=51Reply from 103.29.84.13: bytes=32 time=80ms TTL=51Reply from 103.29.84.13: bytes=32 time=82ms TTL=51Ping statistics for 103.29.84.13:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 79ms, Maximum = 86ms, Average = 81msFrom Atlanta, GA:
PING jsdelivr3.dak.netdna-cdn.com (108.161.188.124) 56(84) bytes of data. 64 bytes from 108.161.188.124: icmp_seq=1 ttl=61 time=0.303 ms 64 bytes from 108.161.188.124: icmp_seq=2 ttl=61 time=0.321 ms 64 bytes from 108.161.188.124: icmp_seq=3 ttl=61 time=0.378 ms 64 bytes from 108.161.188.124: icmp_seq=4 ttl=61 time=0.391 ms 64 bytes from 108.161.188.124: icmp_seq=5 ttl=61 time=0.372 ms ^C --- jsdelivr3.dak.netdna-cdn.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4147ms rtt min/avg/max/mdev = 0.303/0.353/0.391/0.034 msFrom Jacksonville, FL:
PING 531151672.r.worldcdn.net (67.209.158.3) 56(84) bytes of data. 64 bytes from jtssqpq.ncserv.com (67.209.158.3): icmp_seq=1 ttl=54 time=73.9 ms 64 bytes from jtssqpq.ncserv.com (67.209.158.3): icmp_seq=2 ttl=54 time=70.6 ms 64 bytes from jtssqpq.ncserv.com (67.209.158.3): icmp_seq=3 ttl=54 time=71.8 ms 64 bytes from jtssqpq.ncserv.com (67.209.158.3): icmp_seq=4 ttl=54 time=76.2 ms 64 bytes from jtssqpq.ncserv.com (67.209.158.3): icmp_seq=5 ttl=54 time=76.3 ms ^C --- 531151672.r.worldcdn.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4140ms rtt min/avg/max/mdev = 70.620/73.805/76.333/2.304 msFrom Buffalo, NY:
PING 531151672.r.worldcdn.net (65.98.109.99) 56(84) bytes of data. 64 bytes from 65.98.109.99: icmp_seq=1 ttl=53 time=15.8 ms 64 bytes from 65.98.109.99: icmp_seq=2 ttl=53 time=15.6 ms 64 bytes from 65.98.109.99: icmp_seq=3 ttl=53 time=15.7 ms 64 bytes from 65.98.109.99: icmp_seq=4 ttl=53 time=15.6 ms 64 bytes from 65.98.109.99: icmp_seq=5 ttl=53 time=15.7 ms ^C --- 531151672.r.worldcdn.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4064ms rtt min/avg/max/mdev = 15.667/15.729/15.808/0.055 ms