Sonic → Congestion on ae2.cr2.lsatca11.sonic.net

I'm noticing some high ping times when this address shows up on tracert.

This node (4th hop) times out or responds with really high ping.

Is anyone going to fix this?

I don't think this board is regularly monitored by Sonic staff anymore. You may want to post over in their forum for an official response.

Thanks for the reply.

Is there trouble at the destination?

Intermediate routers don't have the CPU to respond to ping, but are focused on forwarding traffic. If you use a tool like MTR that'll show latency at each hop AND beyond it, and you see no consistent increase in latency beyond it, the link is not congested.

Two rather simplified examples might make this clearer:

Hop 1: 30ms (LA)
Hop 2: 32ms (LA)
Hop 3: 145ms (LA)
Hop 4: 38ms (Palo Alto)
Hop 5: 60ms (New York)

Hop 3 is not congested, it just isn't able to prioritize ping response.

Hop 1: 30ms (LA)
Hop 2: 32ms (LA)
Hop 3: 145ms (LA)
Hop 4: 151ms (Palo Alto)
Hop 5: 173ms (LA)

An increase at Hop 3 in this example is then followed by consistently higher ping to the sites beyond, which could point toward Hop 3 being congested.

THAT all said, the route could also be asymmetric, so the issue may not be between 3 and 4; it could be the return path from 5, which is invisible unless you can run a reverse traceroute from 5.