Message d'alerte Bouygues Telecom Lien cliquable

Bbox

Latence anormalement élevée

Bonjour,

Je suis un nouveau client de l'offre BBox (numéro de série : 125216438619043, Modèle : F@st5330b).

Depuis la mise en place de l'offre Bouygues (depuis mi-avril, précédemment client Free), je constate une latence anormalement élevé (par fois de l'ordre de 2s).

Voici les traces de ping vers google.fr:
PING google.fr (172.217.19.35): 56 data bytes
64 bytes from 172.217.19.35: seq=0 ttl=51 time=495.738 ms
64 bytes from 172.217.19.35: seq=1 ttl=51 time=438.476 ms
64 bytes from 172.217.19.35: seq=2 ttl=51 time=553.169 ms
64 bytes from 172.217.19.35: seq=3 ttl=51 time=578.263 ms
64 bytes from 172.217.19.35: seq=4 ttl=51 time=661.410 ms
64 bytes from 172.217.19.35: seq=5 ttl=51 time=639.252 ms
64 bytes from 172.217.19.35: seq=6 ttl=51 time=404.529 ms
64 bytes from 172.217.19.35: seq=7 ttl=51 time=604.683 ms
64 bytes from 172.217.19.35: seq=8 ttl=51 time=763.156 ms
64 bytes from 172.217.19.35: seq=9 ttl=51 time=629.818 ms
64 bytes from 172.217.19.35: seq=10 ttl=51 time=733.827 ms
64 bytes from 172.217.19.35: seq=11 ttl=51 time=625.010 ms
64 bytes from 172.217.19.35: seq=12 ttl=51 time=515.106 ms
64 bytes from 172.217.19.35: seq=13 ttl=51 time=729.433 ms
64 bytes from 172.217.19.35: seq=14 ttl=51 time=617.822 ms
64 bytes from 172.217.19.35: seq=15 ttl=51 time=671.492 ms
64 bytes from 172.217.19.35: seq=16 ttl=51 time=835.246 ms
64 bytes from 172.217.19.35: seq=17 ttl=51 time=542.324 ms
64 bytes from 172.217.19.35: seq=18 ttl=51 time=712.139 ms
64 bytes from 172.217.19.35: seq=19 ttl=51 time=716.653 ms
64 bytes from 172.217.19.35: seq=20 ttl=51 time=489.766 ms
64 bytes from 172.217.19.35: seq=21 ttl=51 time=496.132 ms
64 bytes from 172.217.19.35: seq=22 ttl=51 time=506.350 ms
64 bytes from 172.217.19.35: seq=23 ttl=51 time=530.763 ms
64 bytes from 172.217.19.35: seq=24 ttl=51 time=522.269 ms
64 bytes from 172.217.19.35: seq=25 ttl=51 time=533.973 ms
64 bytes from 172.217.19.35: seq=26 ttl=51 time=544.725 ms
64 bytes from 172.217.19.35: seq=27 ttl=51 time=558.128 ms
64 bytes from 172.217.19.35: seq=28 ttl=51 time=567.561 ms
64 bytes from 172.217.19.35: seq=29 ttl=51 time=577.831 ms
64 bytes from 172.217.19.35: seq=30 ttl=51 time=590.062 ms
64 bytes from 172.217.19.35: seq=31 ttl=51 time=597.478 ms
64 bytes from 172.217.19.35: seq=32 ttl=51 time=614.491 ms
64 bytes from 172.217.19.35: seq=33 ttl=51 time=619.158 ms
64 bytes from 172.217.19.35: seq=34 ttl=51 time=624.619 ms
64 bytes from 172.217.19.35: seq=35 ttl=51 time=627.236 ms
64 bytes from 172.217.19.35: seq=36 ttl=51 time=632.730 ms
64 bytes from 172.217.19.35: seq=37 ttl=51 time=649.968 ms
64 bytes from 172.217.19.35: seq=38 ttl=51 time=660.238 ms
64 bytes from 172.217.19.35: seq=39 ttl=51 time=539.557 ms

J'ai fait un traceroute pour identifier le souci :
traceroute to google.fr (172.217.19.35), 30 hops max, 38 byte packets
1 192.168.0.1 (192.168.0.1) 0.065 ms 0.591 ms 0.559 ms
2 192.168.1.254 (192.168.1.254) 1.235 ms 1.075 ms 1.241 ms
3 static-89-94-79-254.axione.abo.bbox.fr (89.94.79.254) 1078.952 ms 1253.458 ms 1371.162 ms
4 * 89.89.100.129 (89.89.100.129) 1118.556 ms 1158.389 ms
5 89.89.100.128 (89.89.100.128) 910.528 ms 1038.935 ms 1059.862 ms
6 * * *
7 212.194.170.0 (212.194.170.0) 1157.022 ms 1066.825 ms 1104.402 ms
8 * la64.bsr01-aix.net.bbox.fr (212.194.171.153) 30.536 ms 31.233 ms
9 * lag23.rpt02-mrs.net.bbox.fr (212.194.170.54) 30.316 ms *
10 209.85.148.0 (209.85.148.0) 1230.939 ms 1286.276 ms 1054.336 ms
11 108.170.252.241 (108.170.252.241) 1281.393 ms 108.170.252.225 (108.170.252.225) 1194.555 ms 108.170.252.241 (108.170.252.241) 1137.530 ms
12 72.14.233.67 (72.14.233.67) 1146.553 ms 66.249.95.55 (66.249.95.55) 1230.371 ms 72.14.233.67 (72.14.233.67) 1138.353 ms
13 mrs08s03-in-f3.1e100.net (172.217.19.35) 1133.419 ms 1171.920 ms 1099.019 ms

Cette trace me porte à croire que le souci semble se situer à partir du noeud 3 static-89-94-79-254.axione.abo.bbox.fr 89.94.79.254.

Le souci apparaît plus souvent en fin de journée et le week-end.

Je ne vous cache pas que la navigation dans de telles conditions est très pénibles.

Un incident réseau ?

Merci de votre retour,

Grégory BONNARDEL

MARTINE B.
MARTINE B.

MARTINE B.

Niveau
0
3 / 100
points

Aucune réponse