La Fibre
Télécom => Peering Transit (appairage) => Peering entre opérateurs => Discussion démarrée par: Damien06 le 19 mai 2020 à 22:11:13
-
SFR -> fdcservers Paris
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 15 | 7 | 6 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| 26.206.185.81.rev.sfr.net - 3 | 45 | 44 | 0 | 2 | 96 | 1 |
| 74.56.154.77.rev.sfr.net - 2 | 67 | 66 | 1 | 1 | 2 | 1 |
| 170.61.6.109.rev.sfr.net - 0 | 525 | 525 | 1 | 1 | 10 | 2 |
| 174.11.128.77.rev.sfr.net - 0 | 145 | 145 | 7 | 7 | 16 | 7 |
| 114.11.128.77.rev.sfr.net - 0 | 78 | 78 | 13 | 14 | 19 | 14 |
| 101.216.129.77.rev.sfr.net - 0 | 74 | 74 | 13 | 14 | 35 | 13 |
| be5261.ccr31.par04.atlas.cogentco.com - 0 | 23 | 23 | 42 | 47 | 58 | 45 |
| be3184.ccr42.par01.atlas.cogentco.com - 0 | 22 | 22 | 38 | 49 | 62 | 56 |
| be2416.rcr21.par02.atlas.cogentco.com - 0 | 21 | 21 | 39 | 49 | 63 | 57 |
| core01.aggr0.par.fdcservers.net - 0 | 21 | 21 | 36 | 46 | 60 | 54 |
| lg.par.fdcservers.net - 0 | 21 | 21 | 37 | 46 | 57 | 53 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
fdcservers -> SFR sortie sur Cogent à Marseille
HOST: lg-par.fdcservers.net Loss% Snt Last Avg Best Wrst StDev
1. core-jn1.par01.ent.fdcserver 0.0% 5 0.6 0.7 0.6 0.8 0.1
2. be4970.rcr21.par02.atlas.cog 0.0% 5 0.7 0.7 0.7 0.7 0.0
3. be2416.ccr42.par01.atlas.cog 0.0% 5 0.8 0.9 0.8 0.9 0.1
4. be3093.ccr22.mrs01.atlas.cog 0.0% 5 11.9 11.9 11.6 12.1 0.2
5. sfr.demarc.cogentco.com 0.0% 5 46.3 45.8 41.0 54.1 5.0
6. 209.61.6.109.rev.sfr.net 0.0% 5 47.5 63.5 43.3 130.6 37.6
7. 209.61.6.109.rev.sfr.net 0.0% 5 221.5 85.2 44.9 221.5 76.3
8. ??? 100.0 5 0.0 0.0 0.0 0.0 0.0
9. 220.8.119.80.rev.sfr.net 0.0% 5 55.4 50.5 46.3 55.4 3.7
= Cogent sature sur Marseille SFR
-
Meric, il est important d'avoir un traceroute et un traceroute inverse pour ne pas faire d'erreur.
Le plus probable, ca serait que le transit SFR sur Marseille sature (mais d'autres cas sont possibles).
Cogent étant aussi un des transitaire de Bouygues sur Marseille, il serait intéressant de regarder si cela sature également chez Bouygues.
-
Aucun soucis chez Bouygues à l'instant. ( Via Cogent Marseille)
traceroute to lg-par.fdcservers.net (50.7.148.4), 64 hops max, 52 byte packets
1 bbox.lan (192.168.1.254) 2.153 ms 1.593 ms 1.565 ms
2 i19-les01-t2-31-37-192-2.sfr.lns.abo.bbox.fr (31.37.192.2) 5.634 ms 6.789 ms 10.956 ms
3 62.34.2.36 (62.34.2.36) 5.692 ms 4.958 ms 3.965 ms
4 62.34.2.41 (62.34.2.41) 4.178 ms 4.406 ms 2.978 ms
5 be21.cbr01-poi.net.bbox.fr (212.194.170.74) 9.856 ms 9.991 ms 9.137 ms
6 * 212.194.170.253 (212.194.170.253) 9.662 ms 9.018 ms
7 be4887.agr21.mrs01.atlas.cogentco.com (149.14.126.217) 9.185 ms 9.586 ms 8.540 ms
8 be2345.ccr21.mrs01.atlas.cogentco.com (154.54.38.169) 9.233 ms 11.221 ms
be2346.ccr22.mrs01.atlas.cogentco.com (154.54.38.173) 9.005 ms
9 be3092.ccr41.par01.atlas.cogentco.com (130.117.49.153) 20.666 ms
be3093.ccr42.par01.atlas.cogentco.com (130.117.50.165) 20.691 ms
be3092.ccr41.par01.atlas.cogentco.com (130.117.49.153) 18.334 ms
10 be2415.rcr21.par02.atlas.cogentco.com (130.117.48.250) 20.807 ms
be2416.rcr21.par02.atlas.cogentco.com (130.117.48.254) 20.047 ms 21.022 ms
11 core01.aggr0.par.fdcservers.net (149.6.163.58) 21.780 ms 20.808 ms 20.744 ms
12 lg.par.fdcservers.net (50.7.148.4) 19.492 ms 20.340 ms 20.931 ms
-
je re testerais demain soir, maintenant ça ne sature plus, la saturation n'a pas durée longtemps.
-
Depuis Montpellier sur Orange FTTH
traceroute to lg-par.fdcservers.net (50.7.148.4)
1 192.168.1.1 (192.168.1.1) 0.389 ms 0.342 ms 0.309 ms
2 80.10.235.121 (80.10.235.121) 1.118 ms 1.932 ms 1.173 ms
3 ae112-0.ncmon101.Montpellier.francetelecom.net (193.253.95.118) 2.234 ms 1.808 ms 1.975 ms
4 ae44-0.nimar101.Marseille03.francetelecom.net (193.252.101.158) 3.114 ms 3.950 ms 3.003 ms
5 ae40-0.nimar102.Marseille3eArrondissement.francetelecom.net (193.252.161.22) 3.361 ms 5.192 ms 3.952 ms
6 193.252.137.54 (193.252.137.54) 12.351 ms 13.795 ms 13.656 ms
7 be5511.ccr31.par04.atlas.cogentco.com (130.117.15.57) 12.965 ms 12.665 ms 12.673 ms
8 be3184.ccr42.par01.atlas.cogentco.com (154.54.38.157) 13.141 ms 12.835 ms 13.249 ms
9 be2415.rcr21.par02.atlas.cogentco.com (130.117.48.250) 13.569 ms 14.550 ms 13.783 ms
10 core01.aggr0.par.fdcservers.net (149.6.163.58) 13.355 ms 14.518 ms 13.569 ms
11 lg.par.fdcservers.net (50.7.148.4) 13.469 ms 14.007 ms 13.586 ms
-
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 15 | 7 | 6 | 0 | 0 | 0 | 0 |
| 1.14.3.93.rev.sfr.net - 1 | 101 | 100 | 0 | 8 | 97 | 1 |
| 74.56.154.77.rev.sfr.net - 1 | 229 | 228 | 0 | 0 | 2 | 1 |
| ae62-0.ier02.mrs20.ntwk.msn.net - 0 | 171 | 171 | 22 | 23 | 44 | 23 |
| ae24-0.by2-96c-1a.ntwk.msn.net - 25 | 4 | 3 | 23 | 23 | 23 | 23 |
| 104.44.33.107 - 0 | 85 | 85 | 46 | 47 | 146 | 46 |
| be-10-0.ibr01.gva20.ntwk.msn.net - 0 | 86 | 86 | 46 | 46 | 48 | 46 |
| be-4-0.ibr01.zrh20.ntwk.msn.net - 0 | 79 | 79 | 46 | 50 | 142 | 48 |
| be-6-0.ibr01.fra21.ntwk.msn.net - 0 | 85 | 85 | 46 | 46 | 47 | 46 |
| be-8-0.ibr01.ams30.ntwk.msn.net - 0 | 83 | 83 | 46 | 47 | 148 | 46 |
| be-4-0.ibr03.ams06.ntwk.msn.net - 0 | 84 | 84 | 46 | 46 | 48 | 46 |
| ae143-0.icr04.ams06.ntwk.msn.net - 0 | 78 | 78 | 45 | 49 | 119 | 46 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
satu Microsoft Marseille
-
Depuis Orange Marseille
traceroute to www.microsoft.fr (65.52.144.160), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 1.162 ms 0.656 ms 0.733 ms
2 80.10.234.77 (80.10.234.77) 1.818 ms 1.637 ms 1.875 ms
3 193.249.213.2 (193.249.213.2) 1.976 ms 1.887 ms 1.867 ms
4 193.252.161.25 (193.252.161.25) 2.172 ms 1.403 ms 1.495 ms
5 81.253.183.34 (81.253.183.34) 2.150 ms 3.672 ms 2.440 ms
6 microsoft-10.gw.opentransit.net (193.251.249.230) 2.559 ms 2.418 ms 2.473 ms
7 ae20-0.bay-96c-1a.ntwk.msn.net (104.44.238.70) 2.496 ms 2.469 ms 2.213 ms
8 104.44.21.55 (104.44.21.55) 22.960 ms 24.620 ms 125.144 ms
9 104.44.29.69 (104.44.29.69) 25.826 ms 23.144 ms 25.439 ms
10 be-4-0.ibr02.zrh20.ntwk.msn.net (104.44.18.52) 23.140 ms 24.793 ms 22.554 ms
11 be-6-0.ibr01.fra21.ntwk.msn.net (104.44.18.79) 29.078 ms 25.048 ms 25.044 ms
12 be-9-0.ibr02.ams30.ntwk.msn.net (104.44.19.236) 25.747 ms 24.885 ms 25.046 ms
13 ae100-0.icr01.ams30.ntwk.msn.net (104.44.22.214) 24.138 ms 25.003 ms 25.108 ms
14 * * *
-
Orange qui ne met plus les reverses DNS à jour, ça aussi c'est quelque chose.
-
Orange qui ne met plus les reverses DNS à jour, ça aussi c'est quelque chose.
Très très grave
-
Très très grave
C'est pourtant pas compliqué, ça permet le debug et de savoir où on en est dans la route réseau.
-
D'accord ;D
Mais, ça changera quelque chose aux saturations de SFR ? :D
-
je vous met free a toute fin utiles :
tracert www.microsoft.fr
Détermination de l’itinéraire vers msfrbrun3.cloudapp.net [65.52.144.160]
avec un maximum de 30 sauts :
1 <1 ms <1 ms <1 ms 192.168.1.254
2 5 ms 1 ms 1 ms sek76-1_migr-82-67-95-254.fbx.proxad.net [82.67.95.254]
3 <1 ms <1 ms <1 ms 78.255.124.126
4 1 ms 1 ms 1 ms marseille-9k-1-be1015.intf.nro.proxad.net [78.254.252.93]
5 11 ms 11 ms 11 ms p11-crs16-1-be1115.intf.routers.proxad.net [194.149.162.153]
6 * * * Délai d’attente de la demande dépassé.
7 10 ms 10 ms 11 ms ae63-0.pra-96cbe-1a.ntwk.msn.net [104.44.36.117]
8 12 ms 11 ms 11 ms ae27-0.icr01.par21.ntwk.msn.net [104.44.236.93]
9 25 ms 25 ms 25 ms be-120-0.ibr02.par21.ntwk.msn.net [104.44.11.247]
10 22 ms 22 ms 23 ms 104.44.29.35
11 25 ms 25 ms 25 ms 104.44.16.3
12 24 ms 24 ms 24 ms ae120-0.icr01.ams21.ntwk.msn.net [104.44.22.242]
13 * * * Délai d’attente de la demande dépassé.
14 * * * Délai d’attente de la demande dépassé.