Pas de prbleme de fluidité de navigation pour moi.
Après un diag rapide, et non intrusif, les temps de réponses ICMP (ping) semblent correctes, quleques pics mais ces derniers sont également présent sur une IP en amont de celle du serveur (un des derniers bonds avant club944.net)
Dernier saut :
64 bytes from 80.248.218.1: icmp_seq=30 ttl=245 time=21.9 ms
64 bytes from 80.248.218.1: icmp_seq=31 ttl=245 time=21.3 ms
64 bytes from 80.248.218.1: icmp_seq=32 ttl=245 time=21.2 ms
64 bytes from 80.248.218.1: icmp_seq=34 ttl=245 time=108 ms
64 bytes from 80.248.218.1: icmp_seq=35 ttl=245 time=21.8 ms
64 bytes from 80.248.218.1: icmp_seq=36 ttl=245 time=229 ms
64 bytes from 80.248.218.1: icmp_seq=37 ttl=245 time=145 ms
sur l'IP club944.net :64 bytes from 80.248.218.1: icmp_seq=33 ttl=245 time=21.2 ms64 bytes from mail.club944.net (80.248.218.230): icmp_seq=216 ttl=53 time=22.1 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=217 ttl=53 time=21.3 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=218 ttl=53 time=23.7 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=219 ttl=53 time=21.7 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=220 ttl=53 time=22.7 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=221 ttl=53 time=22.1 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=222 ttl=53 time=258 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=223 ttl=53 time=23.5 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=223 ttl=53 time=23.5 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=224 ttl=53 time=22.0 ms
64 bytes from mail.club944.net (80.248.218.230): icmp_seq=225 ttl=53 time=21.4 ms
Idem sur un petit test non agressif sur le serveur Apache :
Starting Nmap 5.21 (
http://nmap.org ) at 2011-08-26 14:18 CEST
NSE: Loaded 36 scripts for scanning.
Initiating Ping Scan at 14:18
Scanning club944.net (80.248.218.230) [4 ports]
Completed Ping Scan at 14:18, 0.04s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 14:18
Completed Parallel DNS resolution of 1 host. at 14:18, 0.14s elapsed
Initiating SYN Stealth Scan at 14:18
Scanning club944.net (80.248.218.230) [1 port]
Discovered open port 80/tcp on 80.248.218.230
Completed SYN Stealth Scan at 14:18, 0.04s elapsed (1 total ports)
Initiating Service scan at 14:18
Scanning 1 service on club944.net (80.248.218.230)
Completed Service scan at 14:18, 6.05s elapsed (1 service on 1 host)
Initiating OS detection (try #1) against club944.net (80.248.218.230)
Retrying OS detection (try #2) against club944.net (80.248.218.230)
Initiating Traceroute at 14:18
Completed Traceroute at 14:18, 1.03s elapsed
Initiating Parallel DNS resolution of 12 hosts. at 14:18
Completed Parallel DNS resolution of 12 hosts. at 14:18, 0.69s elapsed
NSE: Script scanning 80.248.218.230.
NSE: Starting runlevel 1 (of 1) scan.
Initiating NSE at 14:18
Completed NSE at 14:19, 24.33s elapsed
NSE: Script Scanning completed.
Nmap scan report for club944.net (80.248.218.230)
Host is up (0.016s latency).
rDNS record for 80.248.218.230: mail.club944.net
Scanned at 2011-08-26 14:18:27 CEST for 36s
PORT STATE SERVICE VERSION
80/tcp open http Apache httpd 2.2.9 ((Debian) PHP/5.2.6-1+lenny9 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g)
Enfin ca pas l'air méchant, et pas imputable au serveur, enfin sans être dessus je vois rien d'anormal.
En tout cas le ping n'est probablement pas un test fiable pour détecter ce type de pb
iftop, nmap, tcpdump, netstat, etc... seront vos amis côté serveur
Si ces le poste client, désolé mais PWILL+1 (Ubuntu ou un autre linux, Fedora par exemple
...)