An Accepted Solution is available for this post.
Congestion/Latency on Verizon peering circuit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Where do I report an issue with congestion/latency on a verizon peering circuit our traffic is flowing through? This latency(~100ms) begins daily in the mornings and persists for several hours before dropping back down to normal. Traceroutes show the congestion beginning on hop 192.205.35.161.
Here is the info on Verizon peering point in LA
Max In: 19.7 Gb/s (98.4%)
Average In: 15.7 Gb/s (78.6%)
Current In: 16.0 Gb/s (80.2%)
Max Out: 2868.2 Mb/s (14.3%)
Average Out: 1833.4 Mb/s (9.2%)
Current Out: 2324.2 Mb/s (11.6%)
traceroutes
1 | <1 ms | 1 ms | <1 ms 192.168.224.3 | |
2 | <1 ms | <1 ms | 1 ms 192.168.227.254 | |
3 | 1 ms | 1 ms | 1 ms 66.116.98.130 | |
4 | 2 ms | 2 ms | 5 ms 66.209.64.33 | |
5 | 1 ms | 4 ms | 1 ms 66.209.64.138 | |
6 | 35 ms | 7 ms | 8 ms 208.222.10.173 | |
7 | * | * | * | Request timed out. |
8 103 ms 103 ms 102 ms 192.205.35.161
9 | 93 ms | 94 ms | * | 12.122.129.234 |
10 100 ms 105 ms 104 ms 12.122.31.9
11 | 88 ms | 88 ms | * | 12.122.109.105 |
12 | 90 ms | 95 ms | 97 ms 12.250.15.162 | |
13 106 ms 100 ms | * | 12.175.73.130 | ||
14 | 95 ms | 93 ms | 92 ms 12.175.73.130 |
1 | 1 ms | 2 ms | 1 ms 192.168.224.3 | |
2 | <1 ms | <1 ms | <1 ms 192.168.227.254 | |
3 | 1 ms | 1 ms | 1 ms 66.116.98.130 | |
4 | 4 ms | 4 ms | 6 ms 66.209.64.181 | |
5 | 5 ms | 3 ms | 4 ms 66.209.64.134 | |
6 | 7 ms | 7 ms | 8 ms 157.130.243.93 | |
7 | * | * | * | Request timed out. |
8 | 96 ms 101 ms | 98 ms 192.205.35.161 | ||
9 153 ms | * | 160 ms 12.122.129.234 | ||
10 151 ms 185 ms | * | 12.122.28.177 | ||
11 162 ms 160 ms | * | 12.122.2.2 |
12 158 ms 157 ms 155 ms 12.122.85.162
13 | * | * | 147 ms 12.122.112.29 |
14 144 ms 149 ms 153 ms 12.89.201.38
15 | * | 157 ms 152 ms 12.228.78.162 |
0 Replies