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 <liamfarr@me.com> 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 <jlaundry@jlaundry.com> 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@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog


_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog




--
Callum Barr
me@callumb.com