Its fascinating the differences between two traceroutes from the same physical location but two different ISPs -- yet still going through similar NTT nodes once it gets to California:

ATT:

7 cgcil402igs.ip.att.net (12.122.132.197) 8.477 ms 8.791 ms 8.019 ms
8 192.205.32.194 (192.205.32.194) 15.443 ms 7.090 ms 20.245 ms
9 ae-4.r23.chcgil09.us.bb.gin.ntt.net (129.250.4.239) 7.508 ms 7.972 ms 8.069 ms
10 * ae-1.r24.snjsca04.us.bb.gin.ntt.net (129.250.5.17) 55.329 ms 60.330 ms
11 ae-4.a00.scrmca03.us.bb.gin.ntt.net (129.250.7.57) 111.620 ms 113.681 ms 112.283 ms
12 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18) 113.674 ms 113.522 ms 114.396 ms
13 * * 204.2.29.241 (204.2.29.241) 114.096 ms
Comcast:

9 be-2311-pe11.350ecermak.il.ibone.comcast.net (96.110.33.202) 19.727 ms
10 ae-3.a06.chcgil09.us.bb.gin.ntt.net (129.250.8.65) 29.949 ms 23.228 ms 21.926 ms
11 ae-10.r23.chcgil09.us.bb.gin.ntt.net (129.250.3.37) 45.485 ms 26.543 ms 21.283 ms
12 ae-1.r24.snjsca04.us.bb.gin.ntt.net (129.250.5.17) 65.812 ms 74.105 ms 68.419 ms
13 ae-4.a00.scrmca03.us.bb.gin.ntt.net (129.250.7.57) 70.537 ms 71.024 ms 74.866 ms
14 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18) 67.851 ms 73.041 ms 70.355 ms
Something is definitely going on between NTT + ATT - who knows whose fault it is at this point but good grief can't someone update their routing tables to get around their own congestion? *sigh*