Problems with connection (R0) lag

[Aleo]

For me, every tracert shows packet loss problems at the following IP's

6 29 ms 29 ms 29 ms te0-2-0-5.ccr21.lon01.atlas.cogentco.com [130.117.14.205]
7 30 ms 29 ms * be2316.mpd21.lon13.atlas.cogentco.com [154.54.73.113]
8 36 ms * 36 ms be2285.ccr21.lpl01.atlas.cogentco.com [130.117.49.126]

Ping testing these IP's show packet loss between 11 and 25%.

The next step has no packet loss and thereafter.
9 137 ms 137 ms 135 ms be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44.137]

6-8 on the list and those IP's in particular are problematic and I have only had problems since the 2.15 patch this week. Something must have changed in the routing process recently, as I have had zero problems since launch last Aug.

[obscenelocust]

For me, every tracert shows packet loss problems at the following IP's

6 29 ms 29 ms 29 ms te0-2-0-5.ccr21.lon01.atlas.cogentco.com [130.117.14.205]
7 30 ms 29 ms * be2316.mpd21.lon13.atlas.cogentco.com [154.54.73.113]
8 36 ms * 36 ms be2285.ccr21.lpl01.atlas.cogentco.com [130.117.49.126]

Ping testing these IP's show packet loss between 11 and 25%.

The next step has no packet loss and thereafter.
9 137 ms 137 ms 135 ms be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44.137]

6-8 on the list and those IP's in particular are problematic and I have only had problems since the 2.15 patch this week. Something must have changed in the routing process recently, as I have had zero problems since launch last Aug.

Welcome to my world; the cogentco nodes have (likely) been the source of my lag since 2.1 began.