Happy new year to all!
I hope everyone has had a good start to the year. And to help everyone kick
start it even more, we're going to start our industry socials once again
for 2018.
amaysim and IAA invite you to beer, wine, stuff, pizza, ginger ale
(non-alcoholic :)), food etc etc etc at amaysim'
On 1/30/2018 12:00 PM, ausnog-requ...@lists.ausnog.net 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
Hi All,
This is now resolved.
Seems HE has started doing something funky with our routes resulting in sending
all our traffic to our Asia POP’s rather than our SJC POP.
We have disabled our transit links in HKG and SIN and service has been
restored, working with HE for a permanent resolution.
Telia has a planned maintenance in London until 06:00 UTC. The timing seems
suspicious...
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
http://status.vocus.com.au/view-incident.aspx?IncidentID=403
On 30 January 2018 at 12:14, Matt Perkins wrote:
> Yep Vocus is toast somewhere in telia. We dropped international from them
> and issue was resolved quickly.
>
> Matt
>
>
> On 30/1/18 12:03 pm, Karl Latiss wrote:
>
> Add me to the lis
Yep Vocus is toast somewhere in telia. We dropped international from
them and issue was resolved quickly.
Matt
On 30/1/18 12:03 pm, Karl Latiss wrote:
Add me to the list
1?: [LOCALHOST] pmtu 1500
1: 0.466ms
1: 0.405ms
2: ip-245.202.255.49.in-add
If you've got kit in Derby, Broome or Fitzroy area be aware widespread
flooding, sporadic power failures, strong winds gusting to 100k/h.
Broome's had 412mm (yes, 412mm) of rain since 9am yesterday, Derby 102mm
and Fitzroy river at Willaire Bridge is near peak. Floodplains are
saturated. Broom
Add me to the list
1?: [LOCALHOST] pmtu 1500
1:0.466ms
1:0.405ms
2: ip-245.202.255.49.in-addr.VOCUS.net.au0.998ms
3: BE-150.cor02.mel07.vic.VOCUS.net.au 158.514ms asymm 11
4: Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.
We're seeing the same thing, but weirdly, one connection is stable, but the
other is flaky, but we have the same tracert from both...
* Working - completely stable
Tracing route to s3-website-us-east-1.amazonaws.com [52.216.224.226]
over a maximum of 30 hops:
1<1 ms<1 ms<1 ms 192
Hi All,
I can replicate what you are seeing, at this stage it looks like something
in the return path. Please be sure to raise this with our NOC including
SRC/DST so they can keep you informed.
Cheers,
Damien.
On Tue, Jan 30, 2018 at 11:34 AM, Giles Pollock wrote:
> Hi Everyone,
> A frustratin
Same here, but from a different telia.net host.
Hops after sjo-b21-link.telia.net are impacted.
From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of Matt Hare
Sent: Tuesday, 30 January 2018 11:54 AM
To: ausnog@lists.ausnog.net
Subject: Re: [AusNOG] Anyone else seeing massive packet
Also seeing massive packet loss on our Vocus links next hop after
a100us-ic-303629-dls-bb1.c.telia.net
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
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?
tracero
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-reachabi
I am seeing very bad packet loss from one of our Vocus connections to
Telecity/Equinix London starting from about 40 minutes ago, in the
region of 40-50% packet loss. Traffic from both London -> AU and AU ->
London is going via he.net in my case, but the packet loss appears to
only happen on th
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 wro
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
17 matches
Mail list logo
