Regarding high latency from Los Angeles/surrounding area

[Rapture]

In my case from Central California, starting a couple weeks ago S-E's NA datacenter's latency to the Tata Communications backbone doubled. Here is a tracert from just now:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 <1 ms 1 ms <1 ms 001.131-78-65.ftth.swbr.surewest.net [65.78.131.1]
3 <1 ms <1 ms <1 ms 172.22.5.13
4 1 ms <1 ms <1 ms 172.21.2.13
5 1 ms <1 ms <1 ms 172.21.0.250
6 4 ms 4 ms 4 ms sjo-bb1-link.telia.net [213.248.88.73]
7 5 ms 5 ms 4 ms tata-ic-140123-sjo-bb1.c.telia.net [213.248.95.130] (San Jose, CA)
8 78 ms 77 ms 77 ms if-1-2.tcore2.SQN-SanJose.as6453.net [63.243.205.2] (San Jose, CA)
9 78 ms 79 ms 78 ms if-5-2.tcore2.PDI-PaloAlto.as6453.net [64.86.21.2]
10 82 ms 77 ms 77 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
11 80 ms 77 ms 77 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
12 151 ms 151 ms 151 ms 66.198.96.50 (also a Montreal as6453.net allocated IP)
13 150 ms 157 ms 158 ms 192.34.76.2 (most likely this is the S-E NA datacenter port)
14 120 ms 119 ms 123 ms 199.91.189.234
15 157 ms 157 ms 154 ms 199.91.189.36

That 66.198.96.45 -> 66.198.96.50 must be the router involved which services one of S-E's paid backbone links for their NA datacenter. In which case they would need to file a support ticket, since either that router is malfunctioning or the port is overloaded.

The link from Telia -> as6453.net (Tata) in San Jose is also horrible.

During Phase 4 beta, I had 80ms ping all the way to my server, which is to be expected considering distance. Ironically now my ping to the JP server (103-110ms same as always) is lower than the NA servers by ~40-50ms, since they are unaffected by this backbone peering issue with Tata which cropped up recently.

My ISP uses the following backbones:
Level 3 (Primary)
Telia (Secondary)
Global Crossing (Tertiary)
Sprint (Backup)