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.

Comments
mexico
ping cdn.jsdelivr.net
>
Turkey... Turk Telecom
Paket: Giden = 4, Gelen = 4, Kaybolan = 0 (%0 kayıp),
En Az = 95ms, En Çok = 99ms, Ortalama = 97ms
From Helsinki, Finland:
New algorithm is online. It should be a lot smarter. Feel free to ping and wget http://cdn.jsdelivr.net/jquery/2.0.3/jquery.min.js
All data helps a lot!
From Helsinki, Finland:
@drazilox Looks good, thank you!
From New Zealand
root@ubuntu-server2:~# ping cdn.jsdelivr.net PING 531151672.r.worldcdn.net (103.29.84.13) 56(84) bytes of data. 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=1 ttl=54 time=392 ms 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=2 ttl=54 time=421 ms 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=3 ttl=54 time=483 ms 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=4 ttl=54 time=393 ms 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=5 ttl=54 time=212 ms ^C --- 531151672.r.worldcdn.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 212.888/380.528/483.007/90.055 msFrom Jakarta, Indonesia.
F:\>ping cdn.jsdelivr.net Pinging jsdelivr3.dak.netdna-cdn.com [198.232.126.132] with 32 bytes of data: Reply from 198.232.126.132: bytes=32 time=248ms TTL=50 Reply from 198.232.126.132: bytes=32 time=268ms TTL=50 Reply from 198.232.126.132: bytes=32 time=269ms TTL=50 Reply from 198.232.126.132: bytes=32 time=449ms TTL=50 Ping statistics for 198.232.126.132: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 248ms, Maximum = 449ms, Average = 308ms@vRozenSch00n @lukesUbuntu Can you both ping this hostname too? 2-01-2cd3-000b.cdx.cedexis.net
It has a small fix.
Here you go:
G:\>ping 2-01-2cd3-000b.cdx.cedexis.net Pinging jsdelivr3.dak.netdna-cdn.com [198.232.126.132] with 32 bytes of data: Reply from 198.232.126.132: bytes=32 time=264ms TTL=48 Reply from 198.232.126.132: bytes=32 time=266ms TTL=48 Reply from 198.232.126.132: bytes=32 time=272ms TTL=48 Reply from 198.232.126.132: bytes=32 time=386ms TTL=48 Ping statistics for 198.232.126.132: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 264ms, Maximum = 386ms, Average = 297msManila:
From UK, Virgin Media (HFC)
C:\Users\Administrator>ping cdn.jsdelivr.net Pinging 531151672.r.worldcdn.net [185.2.138.117] with 32 bytes of data: Reply from 185.2.138.117: bytes=32 time=24ms TTL=57 Reply from 185.2.138.117: bytes=32 time=16ms TTL=57 Reply from 185.2.138.117: bytes=32 time=17ms TTL=57 Reply from 185.2.138.117: bytes=32 time=19ms TTL=57 Ping statistics for 185.2.138.117: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 24ms, Average = 19ms& T-Mobile UK DC-HSDPA
ping cdn.jsdelivr.net Pinging 531151672.r.worldcdn.net [185.2.138.117] with 32 bytes of data: Reply from 185.2.138.117: bytes=32 time=55ms TTL=53 Reply from 185.2.138.117: bytes=32 time=56ms TTL=53 Reply from 185.2.138.117: bytes=32 time=49ms TTL=53 Reply from 185.2.138.117: bytes=32 time=56ms TTL=53 Ping statistics for 185.2.138.117: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 56ms, Average = 54msFrom New Zealand
It has a small fix.
root@ubuntu-server2:~# ping 2-01-2cd3-000b.cdx.cedexis.net PING 531151672.r.worldcdn.net (103.29.84.13) 56(84) bytes of data. 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=1 ttl=54 time=59.4 ms 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=2 ttl=54 time=67.8 ms 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=3 ttl=54 time=66.7 ms 64 bytes from host13.servermule.com.au (103.29.84.13): icmp_seq=4 ttl=54 time=65.7 ms ^C --- 531151672.r.worldcdn.net ping statistics --- 5 packets transmitted, 4 received, 20% packet loss, time 4004ms rtt min/avg/max/mdev = 59.493/64.951/67.843/3.248 ms@jimaek much better
68.7.169.240 - California - 198.232.126.132
198.23.249.143 - Texas - 198.232.126.132
198.27.121.201 - Montreal, Canada - 185.2.138.117
69.27.21.152 - Utah - 198.232.126.132
Thank you all guys. Btw if anyone is interested what is going on here, you can read here more about how jsDelivr works http://blog.maxcdn.com/load-balancing-multiple-cdns-jsdelivr-works/
Kiev, Ukraine home internet
64 bytes from 176.107.177.101: seq=0 ttl=61 time=1.532 ms
Kiev, Ukraine home internet2
Ответ от 198.232.126.132: число байт=32 время=54мс TTL=54
Vinnitsa, Ukraine hyperhosting
64 bytes from leap-ua.jsdelivr.net (176.107.177.101): icmp_seq=1 ttl=59 time=9.95 ms
Kharkov, Ukraine onehostpower
64 bytes from leap-ua.jsdelivr.net (176.107.177.101): icmp_req=2 ttl=59 time=8.91 ms
Kharkov, Ukraine vdsinside
64 bytes from b9028a75.lon.100tb.com (185.2.138.117): icmp_req=1 ttl=59 time=50.6 ms
@Strikerr Thanks. I think some times it selects a slower provider because there is not enough data. I am working to fix this. You can help btw https://github.com/jsdelivr/jsdelivr#performance-data-contribution
jsDelivr now has a new provider. CloudFlare joined our sponsors. If you guy have some time can you do some tests again? I am optimizing the algorithm as always.
Also some cool graphs:

From Helsinki, Finland.
From the Den Haag, The Netherlands:
From Montréal, Canada (OVH Datacenter):
XXXX@XXXX:~$ ping cdn.jsdelivr.net
PING cdn.jsdelivr.net.cdn.cloudflare.net (190.93.247.228) 56(84) bytes of data.
64 bytes from 190.93.247.228: icmp_req=1 ttl=58 time=18.0 ms
64 bytes from 190.93.247.228: icmp_req=2 ttl=58 time=17.7 ms
64 bytes from 190.93.247.228: icmp_req=3 ttl=58 time=17.9 ms
64 bytes from 190.93.247.228: icmp_req=4 ttl=58 time=17.9 ms
64 bytes from 190.93.247.228: icmp_req=5 ttl=58 time=18.1 ms
64 bytes from 190.93.247.228: icmp_req=6 ttl=58 time=18.0 ms
64 bytes from 190.93.247.228: icmp_req=7 ttl=58 time=17.8 ms
64 bytes from 190.93.247.228: icmp_req=8 ttl=58 time=17.7 ms
64 bytes from 190.93.247.228: icmp_req=9 ttl=58 time=17.8 ms
64 bytes from 190.93.247.228: icmp_req=10 ttl=58 time=17.8 ms
64 bytes from 190.93.247.228: icmp_req=11 ttl=58 time=17.9 ms
64 bytes from 190.93.247.228: icmp_req=12 ttl=58 time=17.8 ms
64 bytes from 190.93.247.228: icmp_req=13 ttl=58 time=18.0 ms
64 bytes from 190.93.247.228: icmp_req=14 ttl=58 time=17.8 ms
64 bytes from 190.93.247.228: icmp_req=15 ttl=58 time=18.1 ms