We also observed this today, UTC morning, esp. across the pond, and our
alternative paths from Europe to the US were suffering from the still unfixed
fibre cut, so I was a bit unhappy with 200 extra ms, and 60% loss.

1299 seems to've found an alternative path in the meantime, looks good to us.

Elmar.


nanog@nanog.org (Andrian Visnevschi via NANOG) wrote:

> We had the same issue with Arelion this morning, a huge increase in the
> latency and jitter was happening across the US and of course for any
> traffic sourced from the EU flowing to the US.
> Within the US we noticed a latency spike from 20-50ms to ~200ms. From the
> EU to our US facilities, we noticed a spike from  ~130ms to ~400ms.
>
>
> We ended up shifting traffic from Arelion to a different carrier, and will
> stay there until we are confident that they fixed any issue that they had
> in their network. To be honest, we've been experiencing quite similar
> issues with unstable latency on Arelion over the past couple of months, and
> it's becoming quite frustrating
>
>
>
>
> *Andrian Visnevschi*
>
> VP of Network & Security
>
> +373 68374133
>
> andrian@acreto.io | https://acreto.io
>
>
>
>
> On Tue, Oct 24, 2023 at 6:03 PM David Hubbard <dhubbard@dino.hostasaurus.com>
> wrote:
>
> > Hey all, anyone aware of issues with Arelion this morning?  We have a
> > bunch of end users on at least Cox and Cogeco who are having serious issues
> > with service access, and the problem appears to be on the return path where
> > it traverses Arelion.  Source net is Lumen/L3 3356 but loss/latency doesn’t
> > appear to creep up until already within Arelion’s network.
> >
> >
> >
> > Imperva mentioned outage/degradation due to a national ISP issue too, so I
> > suspect it’s affecting more than just certain peerings.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > David
> >