w1mm13 schreef op dinsdag 10 mei 2022 @ 14:35:
[...]
Wat denk je hier van .....
PING pantheon-systems.map.fastly.net (151.101.38.133): 56 data bytes
64 bytes from 151.101.38.133: icmp_seq=0 ttl=61 time=0.948 ms
64 bytes from 151.101.38.133: icmp_seq=1 ttl=61 time=0.934 ms
64 bytes from 151.101.38.133: icmp_seq=2 ttl=61 time=0.878 ms
64 bytes from 151.101.38.133: icmp_seq=3 ttl=61 time=0.852 ms
64 bytes from 151.101.38.133: icmp_seq=4 ttl=61 time=0.874 ms
64 bytes from 151.101.38.133: icmp_seq=5 ttl=61 time=0.780 ms
64 bytes from 151.101.38.133: icmp_seq=6 ttl=61 time=0.856 ms
64 bytes from 151.101.38.133: icmp_seq=7 ttl=61 time=0.944 ms
64 bytes from 151.101.38.133: icmp_seq=8 ttl=61 time=0.867 ms
64 bytes from 151.101.38.133: icmp_seq=9 ttl=61 time=1.012 ms
--- pantheon-systems.map.fastly.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.780/0.895/1.012/0.062 ms
Dat red ik toch echt niet, dit is vanaf mijn server welke direct op de router zit aangesloten met een cat6 kabeltje van 0.25M, korter pad dan dat kan ik niet hebben.
PING 151.101.38.133 (151.101.38.133) 56(84) bytes of data.
64 bytes from 151.101.38.133: icmp_seq=1 ttl=60 time=7.11 ms
64 bytes from 151.101.38.133: icmp_seq=2 ttl=60 time=6.18 ms
64 bytes from 151.101.38.133: icmp_seq=3 ttl=60 time=7.47 ms
64 bytes from 151.101.38.133: icmp_seq=4 ttl=60 time=6.64 ms
64 bytes from 151.101.38.133: icmp_seq=5 ttl=60 time=7.84 ms
64 bytes from 151.101.38.133: icmp_seq=6 ttl=60 time=6.99 ms
64 bytes from 151.101.38.133: icmp_seq=7 ttl=60 time=8.32 ms
64 bytes from 151.101.38.133: icmp_seq=8 ttl=60 time=6.63 ms
64 bytes from 151.101.38.133: icmp_seq=9 ttl=60 time=6.06 ms
^C
--- 151.101.38.133 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8014ms
rtt min/avg/max/mdev = 6.056/7.026/8.316/0.705 ms