Sure... Fun thing is I can't get to the ec2-reachability page because it also seems to be affected. for now, I've chosen console.aws.amazon.com (which is going to us-east-1) and docs.aws.amazon.com, as well as ec2-reachability.amazonaws.com
All follow the same path it seems... tracert ec2-reachability.amazonaws.com Tracing route to s3-website-us-east-1.amazonaws.com [54.231.114.201] over a maximum of 30 hops: 1 <1 ms <1 ms 1 ms <REDACTED> 2 2 ms 1 ms 1 ms <REDACTED> 3 168 ms 167 ms 167 ms BE-150.cor02.mel07.vic.VOCUS.net.au [114.31.196.54] 4 163 ms 163 ms 163 ms Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.au [114.31.192.114] 5 163 ms 163 ms 163 ms bundle-200.cor01.sjc01.ca.vocus.net [49.255.255.10] 6 167 ms 168 ms 168 ms bundle-100.bdr01.sjc01.ca.vocus.net [49.255.255.19] 7 168 ms 173 ms 168 ms sjo-b21-link.telia.net [62.115.154.12] 8 169 ms 170 ms 169 ms las-b21-link.telia.net [62.115.116.41] 9 201 ms 201 ms 205 ms dls-b21-link.telia.net [62.115.123.136] 10 206 ms 205 ms 205 ms a100us-ic-303629-dls-bb1.c.telia.net [213.248.85.222] 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * 282 ms 282 ms 54.240.229.175 16 * * * Request timed out. 17 * * * Request timed out. 18 281 ms * * 54.239.111.43 19 * * * Request timed out. 20 * 280 ms 281 ms 72.21.220.43 21 * * * Request timed out. 22 ^C On Tue, Jan 30, 2018 at 11:40 AM, Andras Toth <diosbej...@gmail.com> wrote: > Hi Giles, > > Do you have a traceroute and/or MTR output that you could include? > > Do you see packet loss to IP addresses listed on http://ec2-reachability. > amazonaws.com/ as well? If so, can you include traceroutes/MTR for those > too please? > > Andras > > > On Tue, Jan 30, 2018 at 11:34 AM, Giles Pollock <glp...@gmail.com> wrote: > >> Hi Everyone, >> A frustrating start to the morning with over 50% packet loss when trying >> to hit console.aws.amazon.com. Traffic heading via Vocus is fine up >> until it heads into Telia.net, specifically >> a-100-ic-300087-kbn-b3.c.telia.net >> >> Can't find any noise in the usual places yet that indicate theres an >> issue, so wondering if anyone else is seeing the same problem? >> >> _______________________________________________ >> AusNOG mailing list >> AusNOG@lists.ausnog.net >> http://lists.ausnog.net/mailman/listinfo/ausnog >> >> >
_______________________________________________ AusNOG mailing list AusNOG@lists.ausnog.net http://lists.ausnog.net/mailman/listinfo/ausnog