Hey, Is anyone else noticing high packet loss to AWS Sydney this morning? PING ap-southeast-2.console.aws.amazon.com (54.240.195.68) 56(84) bytes of data. 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=12 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=17 ttl=240 time=39.6 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=20 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=32 ttl=240 time=161 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=34 ttl=240 time=40.2 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=39 ttl=240 time=294 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=41 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=47 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=54 ttl=240 time=65.5 ms Thanks, Jed.
Cloud flare NZ node is also down (see https://www.cloudflarestatus.com/ https://www.cloudflarestatus.com/), and Ben tells me there is 50% packet loss to cloud flare Sydney. I note that my NZ cloud flare sites are being served from Syd “very slowly”.
On 9/02/2017, at 9:24 AM, Jed Laundry
wrote: Hey,
Is anyone else noticing high packet loss to AWS Sydney this morning?
PING ap-southeast-2.console.aws.amazon.com (54.240.195.68) 56(84) bytes of data. 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=12 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=17 ttl=240 time=39.6 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=20 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=32 ttl=240 time=161 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=34 ttl=240 time=40.2 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=39 ttl=240 time=294 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=41 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=47 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=54 ttl=240 time=65.5 ms
Thanks, Jed. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
AWS looks sweet for me;
PING 54.240.195.68 (54.240.195.68): 56 data bytes
64 bytes from 54.240.195.68: icmp_seq=0 ttl=247 time=24.575 ms
64 bytes from 54.240.195.68: icmp_seq=1 ttl=247 time=24.478 ms
64 bytes from 54.240.195.68: icmp_seq=2 ttl=247 time=24.422 ms
64 bytes from 54.240.195.68: icmp_seq=3 ttl=247 time=24.466 ms
64 bytes from 54.240.195.68: icmp_seq=4 ttl=247 time=24.487 ms
64 bytes from 54.240.195.68: icmp_seq=5 ttl=247 time=24.448 ms
Can confirm that Cloudflare is buggered.
On Thu, Feb 9, 2017 at 9:27 AM, Liam Farr
Cloud flare NZ node is also down (see https://www.cloudflarestatus.com/), and Ben tells me there is 50% packet loss to cloud flare Sydney.
I note that my NZ cloud flare sites are being served from Syd “very slowly”.
On 9/02/2017, at 9:24 AM, Jed Laundry
wrote: Hey,
Is anyone else noticing high packet loss to AWS Sydney this morning?
PING ap-southeast-2.console.aws.amazon.com (54.240.195.68) 56(84) bytes of data. 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=12 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=17 ttl=240 time=39.6 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=20 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=32 ttl=240 time=161 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=34 ttl=240 time=40.2 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=39 ttl=240 time=294 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=41 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=47 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=54 ttl=240 time=65.5 ms
Thanks, Jed. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
-- Callum Barr me(a)callumb.com
Yes, seeing it across Equinix Sydney IX from our peer to theirs.
On 9 February 2017 at 07:30, Callum Barr
AWS looks sweet for me;
PING 54.240.195.68 (54.240.195.68): 56 data bytes 64 bytes from 54.240.195.68: icmp_seq=0 ttl=247 time=24.575 ms 64 bytes from 54.240.195.68: icmp_seq=1 ttl=247 time=24.478 ms 64 bytes from 54.240.195.68: icmp_seq=2 ttl=247 time=24.422 ms 64 bytes from 54.240.195.68: icmp_seq=3 ttl=247 time=24.466 ms 64 bytes from 54.240.195.68: icmp_seq=4 ttl=247 time=24.487 ms 64 bytes from 54.240.195.68: icmp_seq=5 ttl=247 time=24.448 ms
Can confirm that Cloudflare is buggered.
On Thu, Feb 9, 2017 at 9:27 AM, Liam Farr
wrote: Cloud flare NZ node is also down (see https://www.cloudflarestatus.com/), and Ben tells me there is 50% packet loss to cloud flare Sydney.
I note that my NZ cloud flare sites are being served from Syd “very slowly”.
On 9/02/2017, at 9:24 AM, Jed Laundry
wrote: Hey,
Is anyone else noticing high packet loss to AWS Sydney this morning?
PING ap-southeast-2.console.aws.amazon.com (54.240.195.68) 56(84) bytes of data. 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=12 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=17 ttl=240 time=39.6 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=20 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=32 ttl=240 time=161 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=34 ttl=240 time=40.2 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=39 ttl=240 time=294 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=41 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=47 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=54 ttl=240 time=65.5 ms
Thanks, Jed. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
-- Callum Barr me(a)callumb.com
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
-- Regards, Mark L. Tees
Getting to that AWS IP via GGI seems ok, via Vocus, not so much tonyw(a)mgmt1:~$ mtr ap-southeast-2.console.aws.amazon.com My traceroute [v0.85] mgmt1 (0.0.0.0) Thu Feb 9 09:36:53 2017 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 10.98.32.1 0.0% 74 2.1 4.3 2.1 33.5 5.3 2. 10.98.47.1 0.0% 74 0.5 0.6 0.4 1.1 0.0 3. 103-208-143-249.feenix.co.nz 0.0% 74 2.0 2.1 1.8 2.8 0.0 4. ae9-134.akcr11.global-gateway.net.nz 0.0% 73 1.8 4.4 1.7 41.1 8.3 5. ae7-2.akbr7.global-gateway.net.nz 0.0% 73 1.9 2.2 1.7 14.3 1.7 6. 122.56.119.18 0.0% 73 25.8 25.9 25.6 32.5 0.9 7. ae7-10.sebr4.global-gateway.net.nz 0.0% 73 27.9 26.1 25.6 34.5 1.1 8. 202.50.232.94 0.0% 73 25.4 25.4 25.2 26.2 0.0 9. 52.95.36.48 0.0% 73 33.7 50.2 25.4 825.4 108.1 10. 52.95.36.57 2.7% 73 25.2 25.4 25.2 28.4 0.3 11. 54.240.192.107 0.0% 73 26.8 26.9 26.4 38.2 1.6 12. 54.240.192.167 0.0% 73 27.1 27.0 26.7 27.5 0.0 13. 54.240.195.68 0.0% 73 26.0 26.0 25.8 26.5 0.0 [root(a)zaxxon ~]# mtr ap-southeast-2.console.aws.amazon.com My traceroute [v0.75] zaxxon.wicks.co.nz (0.0.0.0) Thu Feb 9 09:36:49 2017 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. my.router 0.0% 73 0.4 0.3 0.2 0.6 0.1 2. 103-9-40-42.flip.co.nz 0.0% 73 8.2 10.9 7.5 42.9 6.2 3. 100-64-5-1.flip.co.nz 0.0% 73 8.6 12.0 8.6 58.7 7.5 4. ak3-r2.flip.co.nz 0.0% 73 8.3 11.3 7.5 39.6 7.2 5. pts-n.cpcak4-r1.tranzpeer.net 0.0% 73 8.5 13.0 7.9 78.5 10.8 6. pts-s.cpcak4-r1.tranzpeer.net 0.0% 73 8.4 11.0 7.9 31.5 4.8 7. bundle-100.bdr02.akl05.akl.vocus.net.nz 0.0% 72 9.9 14.7 8.7 76.5 12.2 8. bundle-10.cor01.akl05.akl.VOCUS.net.nz 0.0% 72 32.0 35.3 31.5 75.0 7.8 9. ten-0-0-0-2.cor03.syd03.nsw.VOCUS.net.au 0.0% 72 32.2 36.9 31.8 74.4 8.6 10. ten-1-2-0.bdr03.syd03.nsw.VOCUS.net.au 0.0% 72 31.7 34.7 30.7 64.2 6.1 11. 16509.syd.equinix.com 85.9% 72 53.4 38.1 31.4 53.4 6.6 12. 52.95.36.66 87.3% 72 32.5 41.9 32.5 65.5 9.7 13. 52.95.36.75 83.1% 72 283.0 76.0 31.3 290.4 98.6 14. 54.240.192.109 80.3% 72 35.9 109.0 32.7 344.3 125.7 15. 54.240.192.177 71.8% 72 40.5 48.0 33.3 268.7 52.3 16. 54.240.192.175 83.1% 72 318.1 101.3 33.3 318.1 111.4 17. ap-southeast-2.console.aws.amazon.com 84.5% 72 32.9 81.2 32.9 311.7 107.2
On 9/02/2017, at 9:32 AM, Mark Tees
wrote: Yes, seeing it across Equinix Sydney IX from our peer to theirs.
On 9 February 2017 at 07:30, Callum Barr
mailto:me(a)callum.net.nz> wrote: AWS looks sweet for me;
PING 54.240.195.68 (54.240.195.68): 56 data bytes 64 bytes from 54.240.195.68: icmp_seq=0 ttl=247 time=24.575 ms 64 bytes from 54.240.195.68: icmp_seq=1 ttl=247 time=24.478 ms 64 bytes from 54.240.195.68: icmp_seq=2 ttl=247 time=24.422 ms 64 bytes from 54.240.195.68: icmp_seq=3 ttl=247 time=24.466 ms 64 bytes from 54.240.195.68: icmp_seq=4 ttl=247 time=24.487 ms 64 bytes from 54.240.195.68: icmp_seq=5 ttl=247 time=24.448 ms
Can confirm that Cloudflare is buggered.
On Thu, Feb 9, 2017 at 9:27 AM, Liam Farr
wrote:
…including the cloudflarestatus.com http://cloudflarestatus.com/ page via Vocus.
On 9/02/2017, at 9:27 AM, Liam Farr
wrote: Cloud flare NZ node is also down (see https://www.cloudflarestatus.com/ https://www.cloudflarestatus.com/), and Ben tells me there is 50% packet loss to cloud flare Sydney.
I note that my NZ cloud flare sites are being served from Syd “very slowly”.
On 9/02/2017, at 9:24 AM, Jed Laundry
mailto:jlaundry(a)jlaundry.com> wrote: Hey,
Is anyone else noticing high packet loss to AWS Sydney this morning?
PING ap-southeast-2.console.aws.amazon.com http://ap-southeast-2.console.aws.amazon.com/ (54.240.195.68) 56(84) bytes of data. 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=12 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=17 ttl=240 time=39.6 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=20 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=32 ttl=240 time=161 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=34 ttl=240 time=40.2 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=39 ttl=240 time=294 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=41 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=47 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=54 ttl=240 time=65.5 ms
Thanks, Jed. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz mailto:NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
We noticed cloudfare Auckland was down, and CF Sydney has packet loss, so likely related?
Kind regards
Matthew Harrison
The Top Dog / Managing Director
PrimoWireless
Connecting Taranaki
0800 123 774
The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
-----Original Message-----
From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Jed Laundry
Sent: Thursday, 9 February 2017 9:25 AM
To: NZNOG List
Can confirm no loss through GGI Clayton Hubbard Senior Engineer The Network for Learning Ltd M +64 22 043 0155 DDI +64 9 972 2906 P 0800 LEARNING A Suite 306, Geyser Building, 100 Parnell Road, Parnell, Auckland 1052 A PO Box 37118, Parnell, Auckland 1151 n4l.co.nz On Thu, Feb 9, 2017 at 9:27 AM, Matthew Harrison @ PrimoWireless < matthew(a)staff.primowireless.co.nz> wrote:
We noticed cloudfare Auckland was down, and CF Sydney has packet loss, so likely related?
Kind regards
Matthew Harrison The Top Dog / Managing Director
PrimoWireless Connecting Taranaki 0800 123 774
The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
-----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list. waikato.ac.nz] On Behalf Of Jed Laundry Sent: Thursday, 9 February 2017 9:25 AM To: NZNOG List
Subject: [nznog] AWS Sydney Hey,
Is anyone else noticing high packet loss to AWS Sydney this morning?
PING ap-southeast-2.console.aws.amazon.com (54.240.195.68) 56(84) bytes of data. 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=12 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=17 ttl=240 time=39.6 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=20 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=32 ttl=240 time=161 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=34 ttl=240 time=40.2 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=39 ttl=240 time=294 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=41 ttl=240 time=40.7 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=47 ttl=240 time=40.4 ms 64 bytes from 54.240.195.68 (54.240.195.68): icmp_seq=54 ttl=240 time=65.5 ms
Thanks, Jed. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog
We also lost two services in Equinix one running on AWS and one not.
Both going through the Vocus links so possibly an issue there.
Craig Smith
Technical Support Specialist
Codeblue Core
[cid:image001.png(a)01D282BA.8A336E40]
t:
+64 9 970 5625
f:
craig.smith(a)codeblue.co.nzmailto:craig.smith(a)codeblue.co.nz
m:
www.codeblue.co.nzhttp://www.codeblue.co.nz
This email is intended solely for the use of the addressee and may contain information that is confidential or subject to legal professional privilege. If you receive this email in error please immediately notify the sender and delete the email.
From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Clayton Hubbard
Sent: Thursday, 9 February 2017 9:52 AM
To: NZNOG List
For future reference, AWS has hosts available for global connectivity testing, including several in ap-southeast-2: http://ec2-reachability.amazonaws.com/ http://ipv6.ec2-reachability.amazonaws.com/
participants (10)
-
Callum Barr
-
Clayton Hubbard
-
Craig Smith
-
Jed Laundry
-
Karl Hardisty
-
Liam Farr
-
Luke Flemington
-
Mark Tees
-
Matthew Harrison @ PrimoWireless
-
Tony Wicks