@victor : cela persiste de mon côté également. Le problème ne semble pas venir des délais de connexion au serveur, que de soit pour le joindre via ping ou netcat, les temps de réponses sont normaux.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31 | $ ping -c 10 www.zestedesavoir.com
PING zdsprod1.zestedesavoir.com (92.243.7.44): 56 data bytes
64 bytes from 92.243.7.44: icmp_seq=0 ttl=50 time=44.409 ms
64 bytes from 92.243.7.44: icmp_seq=1 ttl=50 time=43.809 ms
64 bytes from 92.243.7.44: icmp_seq=2 ttl=50 time=44.103 ms
64 bytes from 92.243.7.44: icmp_seq=3 ttl=50 time=44.714 ms
64 bytes from 92.243.7.44: icmp_seq=4 ttl=50 time=44.052 ms
64 bytes from 92.243.7.44: icmp_seq=6 ttl=50 time=42.827 ms
64 bytes from 92.243.7.44: icmp_seq=7 ttl=50 time=45.343 ms
64 bytes from 92.243.7.44: icmp_seq=9 ttl=50 time=43.832 ms
--- zdsprod1.zestedesavoir.com ping statistics ---
10 packets transmitted, 8 packets received, 20.0% packet loss
round-trip min/avg/max/std-dev = 42.827/44.136/45.343/0.688 ms
$ ping -c 10 linuxfr.org
PING linuxfr.org (88.191.250.176): 56 data bytes
64 bytes from 88.191.250.176: icmp_seq=0 ttl=51 time=44.847 ms
64 bytes from 88.191.250.176: icmp_seq=1 ttl=51 time=45.240 ms
64 bytes from 88.191.250.176: icmp_seq=2 ttl=51 time=44.753 ms
64 bytes from 88.191.250.176: icmp_seq=3 ttl=51 time=44.556 ms
64 bytes from 88.191.250.176: icmp_seq=4 ttl=51 time=46.237 ms
64 bytes from 88.191.250.176: icmp_seq=5 ttl=51 time=45.124 ms
64 bytes from 88.191.250.176: icmp_seq=6 ttl=51 time=45.168 ms
64 bytes from 88.191.250.176: icmp_seq=7 ttl=51 time=45.011 ms
64 bytes from 88.191.250.176: icmp_seq=8 ttl=51 time=44.755 ms
64 bytes from 88.191.250.176: icmp_seq=9 ttl=51 time=44.809 ms
--- linuxfr.org ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 44.556/45.050/46.237/0.445 ms
|
Par contre, le délai de réponse aux requêtes HTTP est parfois long, sans raison visible. Que ce soit via Firefox, netcat ou openssl, j’observe des temps de réponse parfois important. À noter qu’en cas de réponse courte type 301, la réponse arrive immédiatement, là ou l’affichage d’une page comme celle de l’accueil prend plus de temps pour arriver.
@Sandhose : de mon côté je ne passe a priori pas par France-IX
1
2
3
4
5
6
7
8
9
10
11
12
13 | ~ doas traceroute -I www.zestedesavoir.com
traceroute to zdsprod1.zestedesavoir.com (92.243.7.44), 64 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.92 ms 1.801 ms 1.67 ms
2 1.240-134-109.adsl-dyn.isp.belgacom.be (109.134.240.1) 82.271 ms 66.691 ms 91.006 ms
3 * lag-62-100.iarmar1.isp.belgacom.be (91.183.241.250) 27.165 ms *
4 lag-24-1000.ibrmar4.isp.belgacom.be (91.183.246.180) 26.896 ms 26.863 ms 26.502 ms
5 he.bnix.net (194.53.172.33) 26.498 ms 37.471 ms 30.106 ms
6 10ge10-8.core1.par2.he.net (184.105.64.17) 48.482 ms 41.582 ms 34.497 ms
7 gandi-sas.10gigabitethernet8-18.core1.par2.he.net (216.66.89.126) 47.707 ms 49.357 ms 46.198 ms
8 v601.csd5.paris.gandi.net (217.70.176.3) 42.715 ms 45.082 ms 42.912 ms
9 i0.edge-b.sd5.paris.gandi.net (217.70.176.11) 43.597 ms 43.382 ms 43.896 ms
10 xvm-136-5.sd5.ghst.net (155.133.136.5) 43.832 ms 43.986 ms 43.703 ms
11 zdsprod1.zestedesavoir.com (92.243.7.44) 46.829 ms 43.724 ms 43.654 ms
|
