That's odd. I've just been watching my server monitoring (Datadog) start
skipping tons of datapoints.
It is also going to us-east-1, but using NTT not Vocus/Telia.
This started at about 10:55 for me. Before that was perfect.
I don't think my traceroute has anything in common with yours?
traceroute to s3-website-us-east-1.amazonaws.com (52.216.161.90), 30
hops max, 60 byte packets
2 rtif-118.127.7.2-31.cs-1.as45671.net.au (118.127.7.2) 0.398 ms
0.462 ms 0.570 ms
3 ten2-1.br-1-2.as45671.net.au (203.26.198.27) 0.292 ms 0.456 ms
0.617 ms
4 203.26.197.9 (203.26.197.9) 13.695 ms 13.707 ms 13.683 ms
5 xe-1-0-0.gw101.sy1.ap.equinix.com (27.111.240.140) 0.189 ms
xe-0-0-0.gw101.sy1.ap.equinix.com (27.111.240.142) 0.233 ms 0.213 ms
6 202.68.70.145 (202.68.70.145) 0.271 ms 0.309 ms 0.316 ms
7 ae-8.r22.lsanca07.us.bb.gin.ntt.net (129.250.3.164) 157.394 ms
157.397 ms 157.458 ms
8 ae-7.r22.dllstx09.us.bb.gin.ntt.net (129.250.7.68) 184.012 ms
186.950 ms 183.988 ms
9 ae-2.r10.dllstx09.us.bb.gin.ntt.net (129.250.4.82) 194.855 ms
ae-2.r11.dllstx09.us.bb.gin.ntt.net (129.250.5.14) 176.294 ms 178.943 ms
10 ae-0.a02.dllstx09.us.bb.gin.ntt.net (129.250.4.204) 184.306 ms
ae-1.a00.dllstx04.us.bb.gin.ntt.net (129.250.4.202) 199.942 ms 209.388 ms
11 * * ae-2.amazon.dllstx04.us.bb.gin.ntt.net (129.250.201.150) 196.363 ms
12 * * *
13 * * *
14 * * *
15 54.240.229.189 (54.240.229.189) 277.958 ms * *
16 * * *
17 54.239.109.30 (54.239.109.30) 294.726 ms * *
18 54.239.109.251 (54.239.109.251) 285.324 ms * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 s3-website-us-east-1.amazonaws.com (52.216.161.90) 276.608 ms * *
On 30/01/18 11:47, Giles Pollock wrote:
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
<http://console.aws.amazon.com> (which is going to us-east-1) and
docs.aws.amazon.com <http://docs.aws.amazon.com>, as well as
ec2-reachability.amazonaws.com <http://ec2-reachability.amazonaws.com>
All follow the same path it seems...
tracert ec2-reachability.amazonaws.com
<http://ec2-reachability.amazonaws.com>
Tracing route to s3-website-us-east-1.amazonaws.com
<http://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
<http://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
<http://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
<http://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
<http://bundle-100.bdr01.sjc01.ca.vocus.net> [49.255.255.19]
7 168 ms 173 ms 168 ms sjo-b21-link.telia.net
<http://sjo-b21-link.telia.net> [62.115.154.12]
8 169 ms 170 ms 169 ms las-b21-link.telia.net
<http://las-b21-link.telia.net> [62.115.116.41]
9 201 ms 201 ms 205 ms dls-b21-link.telia.net
<http://dls-b21-link.telia.net> [62.115.123.136]
10 206 ms 205 ms 205 ms a100us-ic-303629-dls-bb1.c.telia.net
<http://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
<mailto: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/
<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
<mailto: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
<http://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
<http://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 <mailto:AusNOG@lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog
<http://lists.ausnog.net/mailman/listinfo/ausnog>
_______________________________________________
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
--
Nick Stallman
Technical Director
Email n...@agentpoint.com <mailto:n...@agentpoint.com>
Phone 02 8039 6820 <tel:0280396820>
Website www.agentpoint.com.au <https://www.agentpoint.com.au/>
Agentpoint <https://www.agentpoint.com.au/>
Netpoint <https://netpoint.group/>
Level 3, 100 Harris Street, Pyrmont NSW 2009 Facebook
<https://www.facebook.com/agentpoint/> Twitter
<https://twitter.com/agentpoint> Instagram
<https://www.instagram.com/Agentpoint/> Linkedin
<https://www.linkedin.com/company/agentpoint-pty-ltd>
_______________________________________________
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
