<div dir="ltr">Seems like the destination is in Hetzner, they could also raise it with Twelve99 or prepend routes to use an alternate path.<div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 26, 2024 at 7:46 PM Phil Lavin via Outages <<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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.<br>
<br>
<br>
> On 26 Jan 2024, at 08:40, Saku Ytti <<a href="mailto:saku@ytti.fi" target="_blank">saku@ytti.fi</a>> wrote:<br>
> <br>
> On Fri, 26 Jan 2024 at 10:23, Phil Lavin via NANOG <<a href="mailto:nanog@nanog.org" target="_blank">nanog@nanog.org</a>> wrote:<br>
> <br>
> <br>
>> 88.99.88.67 to <a href="http://216.147.3.209" rel="noreferrer" target="_blank">216.147.3.209</a>:<br>
>> Host Loss% Snt Last Avg Best Wrst StDev<br>
>> 1. 10.88.10.254 0.0% 176 0.2 0.1 0.1 0.3 0.1<br>
>> 7. <a href="http://nug-b1-link.ip.twelve99.net" rel="noreferrer" target="_blank">nug-b1-link.ip.twelve99.net</a> 0.0% 176 3.3 3.5 3.1 24.1 1.6<br>
>> 8. <a href="http://hbg-bb2-link.ip.twelve99.net" rel="noreferrer" target="_blank">hbg-bb2-link.ip.twelve99.net</a> 86.9% 175 18.9 18.9 18.7 19.2 0.1<br>
>> 9. <a href="http://ldn-bb2-link.ip.twelve99.net" rel="noreferrer" target="_blank">ldn-bb2-link.ip.twelve99.net</a> 92.0% 175 30.5 30.6 30.4 30.8 0.1<br>
>> 10. <a href="http://nyk-bb1-link.ip.twelve99.net" rel="noreferrer" target="_blank">nyk-bb1-link.ip.twelve99.net</a> 4.6% 175 99.5 99.5 99.3 100.1 0.2<br>
>> 11. <a href="http://sjo-b23-link.ip.twelve99.net" rel="noreferrer" target="_blank">sjo-b23-link.ip.twelve99.net</a> 56.3% 175 296.8 306.0 289.7 315.0 5.5<br>
>> 12. <a href="http://amazon-ic-366608.ip.twelve99-cust.net" rel="noreferrer" target="_blank">amazon-ic-366608.ip.twelve99-cust.net</a> 80.5% 175 510.0 513.5 500.7 539.7 8.4<br>
> <br>
> This implies the problem is not on this path, because #10 is not<br>
> experiencing it, possibly because it happens to return a packet via<br>
> another option, but certainly shows the problem didn't happen in this<br>
> direction yet at #10, but because #8 and #9 saw it, they already saw<br>
> it on the other direction.<br>
> <br>
> <br>
>> 44.236.47.236 to <a href="http://178.63.26.145" rel="noreferrer" target="_blank">178.63.26.145</a>:<br>
>> Host Loss% Snt Last Avg Best Wrst StDev<br>
>> 1. ip-10-96-50-153.us-west-2.compute.internal 0.0% 267 0.2 0.2 0.2 0.4 0.0<br>
>> 11. <a href="http://port-b3-link.ip.twelve99.net" rel="noreferrer" target="_blank">port-b3-link.ip.twelve99.net</a> 0.0% 267 5.8 5.9 5.6 11.8 0.5<br>
>> 12. <a href="http://palo-b24-link.ip.twelve99.net" rel="noreferrer" target="_blank">palo-b24-link.ip.twelve99.net</a> 4.9% 267 21.1 21.5 21.0 58.4 3.1<br>
>> 13. <a href="http://sjo-b23-link.ip.twelve99.net" rel="noreferrer" target="_blank">sjo-b23-link.ip.twelve99.net</a> 0.0% 266 21.4 22.7 21.3 86.2 6.5<br>
>> 14. <a href="http://nyk-bb1-link.ip.twelve99.net" rel="noreferrer" target="_blank">nyk-bb1-link.ip.twelve99.net</a> 58.1% 266 432.7 422.7 407.2 438.5 6.5<br>
>> 15. <a href="http://ldn-bb2-link.ip.twelve99.net" rel="noreferrer" target="_blank">ldn-bb2-link.ip.twelve99.net</a> 98.1% 266 485.6 485.4 481.6 491.1 3.9<br>
>> 16. <a href="http://hbg-bb2-link.ip.twelve99.net" rel="noreferrer" target="_blank">hbg-bb2-link.ip.twelve99.net</a> 92.5% 266 504.1 499.8 489.8 510.1 5.9<br>
>> 17. <a href="http://nug-b1-link.ip.twelve99.net" rel="noreferrer" target="_blank">nug-b1-link.ip.twelve99.net</a> 55.5% 266 523.5 519.6 504.4 561.7 7.6<br>
>> 18. <a href="http://hetzner-ic-340780.ip.twelve99-cust.net" rel="noreferrer" target="_blank">hetzner-ic-340780.ip.twelve99-cust.net</a> 53.6% 266 524.4 519.2 506.0 545.5 6.9<br>
>> 19. <a href="http://core22.fsn1.hetzner.com" rel="noreferrer" target="_blank">core22.fsn1.hetzner.com</a> 70.2% 266 521.7 519.2 498.5 531.7 6.6<br>
>> 20. <a href="http://static.213-239-254-150.clients.your-server.de" rel="noreferrer" target="_blank">static.213-239-254-150.clients.your-server.de</a> 33.2% 266 382.4 375.4 364.9 396.5 4.1<br>
>> 21. <a href="http://static.145.26.63.178.clients.your-server.de" rel="noreferrer" target="_blank">static.145.26.63.178.clients.your-server.de</a> 62.0% 266 529.9 518.4 506.9 531.3 6.1<br>
> <br>
> This suggests the congestion point is from sjo to nyk, in 1299, not AWS at all.<br>
> <br>
> You could try to fix SPORT/DPORT, and do several SPORT options, to see<br>
> if loss goes away with some, to determine if all LAG members are full<br>
> or just one.<br>
> <br>
> <br>
> At any rate, this seems business as usual, sometimes internet is very<br>
> lossy, you should contact your service provider, which I guess is AWS<br>
> here, so they can contact their service provider or 1299.<br>
> <br>
> -- <br>
> ++ytti<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org" target="_blank">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div>