• Let op: Dit is het archief van het Provider Forum. De berichten die je hier ziet zijn gedateerd en er kan niet meer op worden gereageerd.

Packet loss, meer problemen?

  • Onderwerp starter Onderwerp starter Dhis
  • Startdatum Startdatum
D

Dhis

Ik ben sinds kort overgestapt naar 30mbit Fiber power. Wat mij gelijk opviel waren de iets hogere pings. Ik zat zojuist even te pingen en plots zag ik wat time-outs. Zag er verdwaald uit, totdat ik wat langer bleef pingen. Het blijft terugkomen. Router er tussenuit gehaald en opnieuw rechtstreeks gemeten: zelfde probleem. Het lijkt net gatenkaas. Meer mensen met soortgelijke problemen?

PING Chelloo.nl (80.94.70.24): 56 data bytes
64 bytes from 80.94.70.24: icmp_seq=0 ttl=59 time=9.589 ms
64 bytes from 80.94.70.24: icmp_seq=1 ttl=59 time=8.647 ms
64 bytes from 80.94.70.24: icmp_seq=2 ttl=59 time=18.976 ms
64 bytes from 80.94.70.24: icmp_seq=3 ttl=59 time=9.090 ms
Request timeout for icmp_seq 4
64 bytes from 80.94.70.24: icmp_seq=5 ttl=59 time=12.875 ms
64 bytes from 80.94.70.24: icmp_seq=6 ttl=59 time=10.247 ms
64 bytes from 80.94.70.24: icmp_seq=7 ttl=59 time=8.474 ms
64 bytes from 80.94.70.24: icmp_seq=8 ttl=59 time=10.154 ms
64 bytes from 80.94.70.24: icmp_seq=9 ttl=59 time=10.542 ms
64 bytes from 80.94.70.24: icmp_seq=10 ttl=59 time=10.516 ms
64 bytes from 80.94.70.24: icmp_seq=11 ttl=59 time=10.062 ms
64 bytes from 80.94.70.24: icmp_seq=12 ttl=59 time=20.676 ms
64 bytes from 80.94.70.24: icmp_seq=13 ttl=59 time=17.855 ms
64 bytes from 80.94.70.24: icmp_seq=14 ttl=59 time=8.386 ms
64 bytes from 80.94.70.24: icmp_seq=15 ttl=59 time=10.252 ms
64 bytes from 80.94.70.24: icmp_seq=16 ttl=59 time=10.270 ms
Request timeout for icmp_seq 17
64 bytes from 80.94.70.24: icmp_seq=18 ttl=59 time=8.168 ms
64 bytes from 80.94.70.24: icmp_seq=19 ttl=59 time=5.349 ms
64 bytes from 80.94.70.24: icmp_seq=20 ttl=59 time=8.992 ms
64 bytes from 80.94.70.24: icmp_seq=21 ttl=59 time=5.932 ms
Request timeout for icmp_seq 22
64 bytes from 80.94.70.24: icmp_seq=23 ttl=59 time=5.870 ms
64 bytes from 80.94.70.24: icmp_seq=24 ttl=59 time=8.874 ms
64 bytes from 80.94.70.24: icmp_seq=25 ttl=59 time=8.810 ms
64 bytes from 80.94.70.24: icmp_seq=26 ttl=59 time=10.556 ms
Request timeout for icmp_seq 27
64 bytes from 80.94.70.24: icmp_seq=28 ttl=59 time=6.543 ms
64 bytes from 80.94.70.24: icmp_seq=29 ttl=59 time=6.084 ms
64 bytes from 80.94.70.24: icmp_seq=30 ttl=59 time=6.479 ms
64 bytes from 80.94.70.24: icmp_seq=31 ttl=59 time=6.053 ms
Request timeout for icmp_seq 32
64 bytes from 80.94.70.24: icmp_seq=33 ttl=59 time=9.715 ms
64 bytes from 80.94.70.24: icmp_seq=34 ttl=59 time=5.786 ms
64 bytes from 80.94.70.24: icmp_seq=35 ttl=59 time=11.314 ms
64 bytes from 80.94.70.24: icmp_seq=36 ttl=59 time=11.306 ms
Request timeout for icmp_seq 37
64 bytes from 80.94.70.24: icmp_seq=38 ttl=59 time=14.761 ms
64 bytes from 80.94.70.24: icmp_seq=39 ttl=59 time=11.286 ms
64 bytes from 80.94.70.24: icmp_seq=40 ttl=59 time=8.436 ms
64 bytes from 80.94.70.24: icmp_seq=41 ttl=59 time=8.406 ms
64 bytes from 80.94.70.24: icmp_seq=42 ttl=59 time=6.634 ms
64 bytes from 80.94.70.24: icmp_seq=43 ttl=59 time=6.610 ms
64 bytes from 80.94.70.24: icmp_seq=44 ttl=59 time=6.572 ms
Request timeout for icmp_seq 45
64 bytes from 80.94.70.24: icmp_seq=46 ttl=59 time=12.105 ms
64 bytes from 80.94.70.24: icmp_seq=47 ttl=59 time=6.101 ms
64 bytes from 80.94.70.24: icmp_seq=48 ttl=59 time=5.536 ms
64 bytes from 80.94.70.24: icmp_seq=49 ttl=59 time=6.650 ms
Request timeout for icmp_seq 50
64 bytes from 80.94.70.24: icmp_seq=51 ttl=59 time=5.599 ms
64 bytes from 80.94.70.24: icmp_seq=52 ttl=59 time=11.556 ms
64 bytes from 80.94.70.24: icmp_seq=53 ttl=59 time=9.350 ms
64 bytes from 80.94.70.24: icmp_seq=54 ttl=59 time=11.503 ms
Request timeout for icmp_seq 55
64 bytes from 80.94.70.24: icmp_seq=56 ttl=59 time=11.490 ms
64 bytes from 80.94.70.24: icmp_seq=57 ttl=59 time=6.280 ms
64 bytes from 80.94.70.24: icmp_seq=58 ttl=59 time=6.320 ms
64 bytes from 80.94.70.24: icmp_seq=59 ttl=59 time=14.907 ms
Request timeout for icmp_seq 60
64 bytes from 80.94.70.24: icmp_seq=61 ttl=59 time=11.027 ms
64 bytes from 80.94.70.24: icmp_seq=62 ttl=59 time=18.767 ms
64 bytes from 80.94.70.24: icmp_seq=63 ttl=59 time=10.541 ms
64 bytes from 80.94.70.24: icmp_seq=64 ttl=59 time=9.771 ms
64 bytes from 80.94.70.24: icmp_seq=65 ttl=59 time=9.333 ms
64 bytes from 80.94.70.24: icmp_seq=66 ttl=59 time=11.484 ms
64 bytes from 80.94.70.24: icmp_seq=67 ttl=59 time=5.931 ms
Request timeout for icmp_seq 68
64 bytes from 80.94.70.24: icmp_seq=69 ttl=59 time=9.412 ms
64 bytes from 80.94.70.24: icmp_seq=70 ttl=59 time=5.949 ms
64 bytes from 80.94.70.24: icmp_seq=71 ttl=59 time=11.140 ms
64 bytes from 80.94.70.24: icmp_seq=72 ttl=59 time=14.455 ms
Request timeout for icmp_seq 73
64 bytes from 80.94.70.24: icmp_seq=74 ttl=59 time=10.596 ms
64 bytes from 80.94.70.24: icmp_seq=75 ttl=59 time=6.329 ms
64 bytes from 80.94.70.24: icmp_seq=76 ttl=59 time=6.254 ms
64 bytes from 80.94.70.24: icmp_seq=77 ttl=59 time=10.493 ms
^C
--- Chelloo.nl ping statistics ---
78 packets transmitted, 66 packets received, 15.4% packet loss
round-trip min/avg/max/stddev = 5.349/9.606/20.676/3.390 ms
Klik om te vergroten...
 
64 bytes from Chelloo.nl (80.94.70.24): icmp_seq=98 ttl=59 time=10.9 ms
64 bytes from Chelloo.nl (80.94.70.24): icmp_seq=99 ttl=59 time=11.6 ms
64 bytes from Chelloo.nl (80.94.70.24): icmp_seq=101 ttl=59 time=14.3 ms
^C
--- Chelloo.nl ping statistics ---
101 packets transmitted, 88 received, 12% packet loss, time 100299ms
rtt min/avg/max/mdev = 9.955/11.512/14.882/0.984 ms
ko@metaxa:~$
Klik om te vergroten...

12% hier.....

Ko
 
Ik heb zo het gevoel dat de Chelloo.nl server niet staat te wachten op al die ICMP-requests. :D

Vanaf een niet-UPC-verbinding:
sylv@saturnus:~$ ping 80.94.70.24
PING 80.94.70.24 (80.94.70.24) 56(84) bytes of data.
64 bytes from 80.94.70.24: icmp_seq=2 ttl=56 time=4.50 ms
64 bytes from 80.94.70.24: icmp_seq=3 ttl=56 time=4.26 ms
64 bytes from 80.94.70.24: icmp_seq=4 ttl=56 time=4.27 ms
64 bytes from 80.94.70.24: icmp_seq=7 ttl=56 time=4.42 ms
64 bytes from 80.94.70.24: icmp_seq=8 ttl=56 time=4.27 ms
64 bytes from 80.94.70.24: icmp_seq=10 ttl=56 time=4.19 ms
64 bytes from 80.94.70.24: icmp_seq=16 ttl=56 time=4.50 ms
^C
--- 80.94.70.24 ping statistics ---
37 packets transmitted, 7 received, 81% packet loss, time 36041ms
rtt min/avg/max/mdev = 4.193/4.350/4.507/0.136 ms
sylv@saturnus:~$
sylv@saturnus:~$ ping 80.94.70.24
PING 80.94.70.24 (80.94.70.24) 56(84) bytes of data.
^C
--- 80.94.70.24 ping statistics ---
34 packets transmitted, 0 received, 100% packet loss, time 33014ms

sylv@saturnus:~$
Klik om te vergroten...
Eerst 81% packet loss, daarna 100%!!! Toch is de server up & running.
 
Laten we maar subiet mee stoppen met deze thread, voordat die server wel omduikelt..
Ik heb ook geen probleem; konstateer alleen dat er een significante packet loss is.

Ko
 
het ligt aan de site. Chelloo.nl zorgt bij mij ook voor 10% packet loss. maar een andere site niet: 0% packet loss.
 
Deze hoge packet-loss percentages dragen bij aan de (m.i.) hoge variabiliteit in mini-speedtests op Chelloo.nl.
Die gebruik ik dus ook niet meer.

Ko
 
Je moet ingelogd zijn om te kunnen reageren. Log in | Registreer
Terug
Bovenaan