may want to run a series of normal traces and not pathping. You're getting the average latency over 100 pings for each hop in those reports and not seeing the potential jitter in play. You may be averaging 19ms coming through LA, but could be getting congestion that causes a 180+ lag spike to show every 12th time or something odd like that. This can compound with additional jitter as you move further down the route, so your issue may not necessarily be at the VLAN coming through Ormuco but actually earlier in the route but it's just not showing up in a pathping report. When I run traces, those last hops (including 10.2.2.1) are typically on par or slightly lower than where I cross the IPX from TATA/Cogent/Level3 and into Ormuco.
Code:
C:\Windows\System32>tracert 199.91.189.30
Tracing route to 199.91.189.30 over a maximum of 30 hops
1 2 ms <1 ms <1 ms LPTSRV [10.10.100.1]
2 25 ms 26 ms 46 ms cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
3 26 ms 16 ms 25 ms cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
4 19 ms 18 ms 19 ms 24.31.196.212
5 21 ms 23 ms 26 ms be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
6 26 ms 25 ms 27 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
7 26 ms 24 ms 24 ms 107.14.19.99
8 26 ms 26 ms 27 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
9 27 ms 28 ms 26 ms be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
10 36 ms 34 ms 34 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
11 39 ms 39 ms 42 ms be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
12 44 ms 44 ms 45 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
13 48 ms 48 ms 50 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
14 63 ms 65 ms 65 ms 38.122.42.34
15 49 ms 48 ms 50 ms 10.2.2.1
16 50 ms 51 ms 49 ms 192.34.76.2
17 47 ms 49 ms 51 ms 199.91.189.234
18 49 ms 49 ms 51 ms 199.91.189.30
Trace complete.
That's taken on Wifi from the back of the condo, so there's some odd jitter that creeps in at the start, but notice the variances in my nodes here in the Carolinas. A good bit of jitter likes to creep in there during high volume times, and when it gets really bad I start to feel it in game. Otherwise, things run great now that they're staying on top of things with their peering partners. They typically catch it once it starts to spike above the 230-280 range and change it up without me contacting them now. Early on, I had to generate the reports and forward them and it would take about 3 days to get things changed. But I haven't had to contact them about things on that end for almost 2 months now. We are back to trying to address the congestion in our local area again though. To that end, I am on a new gateway now (75.176.160.1 which is assigned to Conway... I used to be assigned to Hilton Head, which started with 66).
Code:
C:\Windows\System32>ping -n 25 75.176.160.1
Pinging 75.176.160.1 with 32 bytes of data:
Reply from 75.176.160.1: bytes=32 time=23ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=10ms TTL=254
Reply from 75.176.160.1: bytes=32 time=12ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=12ms TTL=254
Reply from 75.176.160.1: bytes=32 time=10ms TTL=254
Reply from 75.176.160.1: bytes=32 time=23ms TTL=254
Reply from 75.176.160.1: bytes=32 time=10ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=12ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=9ms TTL=254
Reply from 75.176.160.1: bytes=32 time=9ms TTL=254
Reply from 75.176.160.1: bytes=32 time=12ms TTL=254
Reply from 75.176.160.1: bytes=32 time=10ms TTL=254
Reply from 75.176.160.1: bytes=32 time=10ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Reply from 75.176.160.1: bytes=32 time=10ms TTL=254
Reply from 75.176.160.1: bytes=32 time=22ms TTL=254
Reply from 75.176.160.1: bytes=32 time=11ms TTL=254
Ping statistics for 75.176.160.1:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 23ms, Average = 12ms
Code:
C:\Windows\System32>pathping 75.176.160.1
Tracing route to cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
over a maximum of 30 hops:
0 G75VXLAP [10.10.100.10]
1 LPTSRV [10.10.100.1]
2 cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 G75VXLAP [10.10.100.10]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% LPTSRV [10.10.100.1]
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
Trace complete.
Notice the difference in the stats amongst those reports. Pathping is showing an average latency of 11ms, but in the tracert it was showing a swing of 25-46, and when I pinged it directly 25 times it swung from 9-23, with right at 1/8 of them clocking in at 2x the average reported by the pathping report. From that small ping sample, the line is showing jitter of just over 3ms against what pathping was showing as an average of 11ms. That comes out to ~30% of the pathping's reported latency... which is not a good result.
Even looking at the short results of the one tracert, it is ~10ms jitter against an average of ~32ms latency which still comes out to around 30% again, which is simply not were you want to be... especially if it is happening at multiple points in your route. If you consistently see those 10, 20, 30ms or higher spikes show up, it can mean your route is in for a bumpy ride. But you won't be seeing that in a pathping report... but you may capture it with some tracerts.