Hello,

Cassé ici aussi dans le 25, connexion FTTH grand public Orange/Sosh.

Les services google sont à peu près revenus chez moi, mais par contre Amazon 
c'est pas la joie (pas d'autre destination que leur site en tête la tout de 
suite pour tester):

[12:37:56] romain@intersect /home/romain % ping amazon.com
PING amazon.com (205.251.242.103) 56(84) bytes of data.
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=13 ttl=235 time=1390 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=15 ttl=235 time=1390 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=18 ttl=235 time=1388 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=22 ttl=235 time=1391 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=24 ttl=235 time=1390 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=31 ttl=235 time=1388 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=51 ttl=235 time=1396 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=55 ttl=235 time=1395 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=56 ttl=235 time=1393 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=59 ttl=235 time=1396 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=64 ttl=235 time=1396 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=65 ttl=235 time=1397 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=66 ttl=235 time=1394 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=73 ttl=235 time=1396 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): 
icmp_seq=75 ttl=235 time=1396 ms
^C
--- amazon.com ping statistics ---
78 packets transmitted, 15 received, 80% packet loss, time 78384ms
rtt min/avg/max/mdev = 1388.600/1393.496/1397.732/3.537 ms, pipe 2

On dirait que ca merdoie côté TATA/AS6453:

[12:42:49] romain@intersect /home/romain % traceroute amazon.com
traceroute to amazon.com (176.32.98.166), 30 hops max, 60 byte packets
 1  gateway (192.168.1.254)  0.197 ms  0.235 ms  0.279 ms
 2  192.168.2.1 (192.168.2.1)  0.795 ms  0.790 ms  0.738 ms
 3  80.10.233.145 (80.10.233.145)  2.008 ms  2.091 ms  2.246 ms
 4  ae115-0.ncdij102.dijon.francetelecom.net (193.253.91.190)  4.368 ms  4.374 
ms  4.403 ms
 5  ae41-0.nistr202.strasbourg.francetelecom.net (193.252.160.118)  25.171 ms  
25.184 ms  25.191 ms
 6  ae40-0.nistr201.schiltigheim.francetelecom.net (81.253.180.117)  10.430 ms  
10.105 ms  10.099 ms
 7  193.252.137.82 (193.252.137.82)  11.740 ms  11.575 ms  11.560 ms
 8  ix-ae-36-0.tcore2.fnm-frankfurt.as6453.net (195.219.87.114)  11.916 ms  
11.849 ms  11.900 ms
 9  if-ae-9-2.tcore1.pvu-paris.as6453.net (195.219.87.10)  107.184 ms 
if-ae-12-2.tcore1.fnm-frankfurt.as6453.net (195.219.87.2)  100.321 ms 
if-ae-12-60.tcore1.fnm-frankfurt.as6453.net (195.219.156.132)  100.321 ms
10  if-ae-6-2.tcore1.av2-amsterdam.as6453.net (195.219.194.149)  100.805 ms  
100.662 ms  100.736 ms
11  if-ae-2-2.tcore2.av2-amsterdam.as6453.net (195.219.194.6)  100.344 ms  
100.442 ms  100.318 ms
12  if-ae-14-2.tcore2.l78-london.as6453.net (80.231.131.160)  109.031 ms  
108.678 ms  108.253 ms
13  if-ae-15-2.tcore2.ldn-london.as6453.net (80.231.131.118)  108.586 ms 
if-ae-12-2.tcore1.n75-new-york.as6453.net (66.110.96.5)  98.808 ms  98.736 ms
14  if-ae-32-3.tcore2.nto-new-york.as6453.net (80.231.20.107)  109.117 ms  
100.640 ms 66.110.96.157 (66.110.96.157)  99.273 ms
15  if-ae-12-2.tcore1.n75-new-york.as6453.net (66.110.96.5)  101.830 ms  92.738 
ms  100.698 ms
16  66.110.96.157 (66.110.96.157)  92.573 ms  100.971 ms *



Romain
________________________________________
De : frnog-requ...@frnog.org [frnog-requ...@frnog.org] de la part de Stephane 
Bortzmeyer [bortzme...@nic.fr]
Envoyé : lundi 15 avril 2019 12:22
À : Benoit Moreau
Cc : frnog@frnog.org
Objet : [FRnOG] Re: [ALERT] Amazon EC2 down ?

On Mon, Apr 15, 2019 at 12:12:25PM +0200,
 Benoit Moreau <m...@virtit.fr> wrote
 a message of 192 lines which said:

> même problème dans le 79 et le 86.

En Espagne aussi, ça déconne, si on en croit Twitter (dont je rappelle
que c'est un outil aussi indispensable pour un NOC que les sondes RIPE
Atlas).


---------------------------
Liste de diffusion du FRnOG
http://www.frnog.org/


---------------------------
Liste de diffusion du FRnOG
http://www.frnog.org/

Répondre à