Seems like the destination is in Hetzner, they could also raise it with
Twelve99 or prepend routes to use an alternate path.
On Fri, Jan 26, 2024 at 7:46 PM Phil Lavin via Outages
wrote:
> Thanks, ytti. I have raised a case with AWS but I expect it to be as
> unproductive as usual. In this
I see the AWS->me path has just changed to Cogent. me->AWS path still appears
to be Twelve99. Loss and latency has now subsided.
Thanks
> On 26 Jan 2024, at 08:19, Phil Lavin wrote:
>
> Hi Folks,
>
> Cross posting to outages and nanog.
>
> Can anybody from Twelve99 / AWS investigate high
Thanks, ytti. I have raised a case with AWS but I expect it to be as
unproductive as usual. In this type of issue, there is often a friendly
Engineer keeping an eye on NANOG list or IRC channel who can mitigate it.
Hoping that to be the case this time, also.
> On 26 Jan 2024, at 08:40, Saku
Hi Folks,
Cross posting to outages and nanog.
Can anybody from Twelve99 / AWS investigate high loss and latency around SJO
between Twelve99 and AWS?
Traces below:
88.99.88.67 to 216.147.3.209:
My traceroute [v0.94]
phil (10.88.10.10) -> 216.147.3.209
