.-- My secret spy satellite informs me that at 2014-09-08 10:31 PM joel
jaeggli via Outages wrote:
is anyone else seeing routing implosion on l3 or first symtoms were in
western europe.
I had packets bound for l3 ips in ams making lazy circles. started circa
0430 utc
Same here, 100% loss
Seeing similar issues between a few US, Asia and EU sites. What I'm
seeing is what appears to be a congested peering connection between GTT
and NTT in Seattle as that is what all traceroutes have in common.
Our graphs indicate this started Jan 1st, around ~ 15:00 utc.
Example traceroute from
Also see here for more details:
http://www.bgpmon.net/massive-route-leak-cause-internet-slowdown/
.-- My secret spy satellite informs me that at 2015-06-12 6:17 AM Hoyle
Anderson (AM) via Outages wrote:
Possibly related: http://seclists.org/nanog/2015/Jun/586 and
Yup lots of packet loss (up to 100%) between US and EU over level3.
First packet loss detected at 21:04 UTC, things got better at around
21:55 UTC
.-- My secret spy satellite informs me that at 2015-09-04 2:52 PM Luca
Salvatore via Outages wrote:
> Anyway else seeing this?
> Huge loss in
Hi Brandon,
My secret spy satellite informs me that Brandon Bianchi via Outages
wrote On 2017-08-17, 7:49 PM:
> I have Level 3 transit services that connect in Vegas and Los Angeles
> that seem to be experiencing loss and increased latency to the point
> where the circuits are not useable. Anyone
There's also an AWS US east issue affecting folks with direct connects
there.. may be related to the east coast issues.. That or memcache..
https://status.aws.amazon.com/
7:29 AM PST We are investigating increased packet loss possibly
impacting some AWS Direct Connect customers in the US-EAST-1
We are seeing major packet loss on Level3 at various of our west coast
north America locations, also Denver.
Guessing it's related...
Cheers
Andree
Sam Thomas via Outages wrote on 2020-04-21 8:35 AM:
A number of our remote users and some of our remote offices on COX are
having some extreme
