Marketing, a nepresvedcivy.ISP1:
google rtt min/avg/max/mdev = 9.542/10.231/11.349/0.462 ms
cloudflare rtt min/avg/max/mdev = 9.191/10.211/21.314/1.860 ms
AWS Frankfurt (elastic IP): rtt min/avg/max/mdev = 17.248/18.092/21.696/0.623 msISP2:
google rtt min/avg/max/mdev = 4.532/5.015/8.685/0.440 ms
cloudflare rtt min/avg/max/std-dev = 4.206/4.304/4.526/0.062 ms
AWS Frankfurt: rtt min/avg/max/mdev = 12.791/13.180/14.381/0.321 msISP3:
google rtt min/avg/max/std-dev = 3.865/3.970/4.279/0.076 ms
cloudflare rtt min/avg/max/std-dev = 4.206/4.304/4.526/0.062 ms
AWS Frankfurt: rtt min/avg/max/std-dev = 11.916/12.047/13.973/0.204 msGoogle vs ClouFlare:
ISP1 stejne, google lepsi jitter
ISP2 lepsi cloudflare (0.7 msec), i jitter
ISP3 lepsi google (0.4msec), cloudflare lepsi jitterPodstatne je neco jineho:Google public DNS znaj a tudiz pouzivaj masy po leta, je tedy extremne zatezovany i provereny. Narust provozu u nej tedy nehrozi, bezne jej pouzivam pro SLA monitor na Cisco a v obdobne roli na firewallech, pokud potrebuju overit dostupnost internetu via jednotlive ISP.CloudFlare by se asi rad dostal, kde je Google, ale to ukaze az cas (a narust provozu). Vedet, kam zakaznici pristupuji, je marketingove neocenitelne, a tudiz se asi budou snazit umerne profitu (pokud obchodne porazi Google, ktery roky vydelava na reklamach, pro jejichz analyzu je znalost DNS provozu sakra vyhodou).Technicky test na odezvu ICMP nic nerika o kvalite a odezve DNS, navic QoS nekterych ISP icmp na vybrane IP proste pousti prvni, i kvuli podobnym testum
Ten Amazon do rajchu je spis vtip, ve virtualizaci radi a casto udp a icmp dropuji a nastavuji rate-limity, navic jde o T2.micro instanci.