[Chrysalis]

Got a brand new cogent issue, ntl to staminus going over cogent.

staminus have 3 backbones in their network mix, abovenet, cogent and nrs, they tried to depreference cogent and nrs but I am told ntl are making it go over cogent, there is a jump to 380ms which is usually 160ms on abovenet and 200ms on nrs.

Trace below, target ip private. but range is 72.20.x

1 24 ms 8 ms 7 ms 10.8.143.254
2 9 ms 8 ms 12 ms leic-t2cam1-a-ge914.inet.ntl.com [82.3.35.149]
3 7 ms 7 ms 7 ms leic-t2core-a-ge-220-0.inet.ntl.com [82.3.33.10]

4 8 ms 10 ms 9 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110]

5 15 ms 14 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

6 33 ms 16 ms 15 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82]

7 201 ms 200 ms 197 ms 212.250.14.62
8 272 ms 267 ms 270 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0
.46]
9 295 ms 323 ms 295 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.11
0]
10 298 ms 332 ms 299 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.6
2]
11 312 ms 312 ms 313 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3
3]
12 330 ms 338 ms 333 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.1
05]
13 369 ms 360 ms 388 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6
]
14 354 ms 357 ms 362 ms p4-0.core01.lax01.atlas.cogentco.com [66.28.4.77
]
15 371 ms 377 ms 381 ms p15-0.core02.lax04.atlas.cogentco.com [154.54.1.
54]
16 378 ms 410 ms 376 ms g0-2.na21.b000899-0.lax04.atlas.cogentco.com [66
.250.8.166]
17 372 ms 365 ms 393 ms brdr02-4ge.lax1.staminus.net [72.20.0.170]
18 373 ms 364 ms 375 ms edge01-ge.lax1.staminus.net [72.20.0.1]
19 397 ms 388 ms 400 ms core02-ge1.irv1.staminus.net [72.20.0.33]
20 397 ms 386 ms 386 ms csr1-ge.irv1.staminus.net [72.20.0.180]
21 389 ms 384 ms 390 ms xxx.xxx.org [72.20.x.x]

friend who works at ntl says ntl peering congested but he hasnt got the access to fix. So I am hoping ignition can have a look thanks.