28June2024 packet loss 90% within Sonic

[bc.houston]

I'm having very slow connectivity because of a Sonic internal network issue...
Here's my MTR diagnosic...

Code: Select all

[brian@CentOS7-9-2009 ~]$ mtr google.com
                                   My traceroute  [v0.85]
CentOS7-9-2009 (0.0.0.0)                                           Fri Jun 28 11:59:11 2024
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                   Packets               Pings
 Host                                            Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. GT-AXE16000-E368                              0.0%    52    0.4   0.6   0.3   0.9   0.0
 2. lo0.bng1.cncrca01.sonic.net                   0.0%    52    1.9   2.3   1.1  18.6   2.3
 3. irb.300.cncrca01.sonic.net                    0.0%    52    6.6   7.7   1.9  52.6   7.5
 4. ae2.eo-sw1-2.cncrca01.sonic.net               0.0%    52    8.9   7.3   1.9  28.4   4.8
 5. ae2.cr1.lfytca11.sonic.net                    3.8%    52   13.4  46.1  11.8 334.3  71.5
 6. ae5.cr3.rcmdca11.sonic.net                   11.5%    52  4496. 5482. 4249. 6396. 627.3
 7. ae3.cr6.rcmdca11.sonic.net                   86.3%    52  4257. 4219. 4037. 4337.  97.3
 8. ae3.cr1.hywrca01.sonic.net                   90.2%    52  8820. 8596. 8299. 8820. 223.4
 9. 0.ae0.cr1.equinix-sj.sonic.net               90.2%    52  9066. 8791. 8585. 9066. 194.5
10. 100.ae1.nrd1.equinix-sj.sonic.net             0.0%    52   34.4  13.0   3.5  45.7  11.6
11. 209.148.113.38                                1.9%    52    4.7   4.5   3.3   7.2   0.4
12. 142.251.69.83                                 1.9%    52    4.9   5.1   4.4   6.9   0.3
13. 142.251.224.189                               3.8%    52    4.7   4.4   3.3   4.8   0.1
14. nuq04s44-in-f14.1e100.net                     5.8%    52    4.6   4.3   3.3   4.8   0.0

[bc.houston]

At the moment, I'm now able to get through without too much delay, which is good.

My MTR diagnostic output hasn't changed, which I'm concerned about, in regards to
my traffic flowing through Sonic.

The MTR diagnostic, which is good, also depends on UDP, which can be optionally dropped by intermediate routers if they are under critical load, or the intermediate connected links are near saturation point. UDP is used by a LOT of things (voip, DNS to name two).

Ultimately I hope that Sonic will address the issue I've brought up.
I've filed a ticket, although it seems completely reasonable that they already know about it through their normal internal monitoring (this isn't rocket science, and things like CheckMK and Pager Duty make this easy to be constantly aware of).

Here's to things getting better.