Just want to add that I am seeing the same thing on Cox, my traceroute matches the reply above mine:
Tracing route to ca1bf1prgm0240.ea.com [159.153.87.83]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms pfSense.domain.local [192.168.1.1]
2 10 ms 11 ms 8 ms 10.52.96.1
3 9 ms 11 ms 9 ms 100.122.225.24
4 11 ms 18 ms 11 ms 100.122.224.182
5 29 ms 30 ms 33 ms dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
6 31 ms 32 ms 29 ms 68.105.30.22
7 35 ms 30 ms 30 ms ae8.er1.dfw2.us.zip.zayo.com [64.125.29.121]
8 31 ms 31 ms 31 ms ae11.cr1.dfw2.us.zip.zayo.com [64.125.20.65]
9 106 ms 71 ms 75 ms ae27.cs1.dfw2.us.eth.zayo.com [64.125.30.180]
10 71 ms 72 ms 71 ms ae3.cs1.lax112.us.eth.zayo.com [64.125.29.53]
11 71 ms 78 ms 71 ms ae2.cs1.sjc2.us.eth.zayo.com [64.125.28.144]
12 72 ms 71 ms 84 ms ae27.cr1.sjc2.us.zip.zayo.com [64.125.30.231]
13 79 ms 78 ms 70 ms ae12.er1.sjc2.us.zip.zayo.com [64.125.25.22]
14 72 ms 74 ms 77 ms 209.66.92.106.t00673-04.above.net [209.66.92.106]
15 146 ms 149 ms 148 ms 159.153.68.38
16 70 ms 83 ms 70 ms ca1bf1prgm0240.ea.com [159.153.87.83]
Consistent 180ms ping in game.
Hey Jake
My ping started to level out, going back to what it was, fairly recently. Within the last couple weeks.
There is a post by a DICE dev in Reddit that I used to contact the third-party that is handling some of the routing for EA BF1. I wouldn't use the Washington DC address they are referencing in this post, but use the address of a few servers you have a really high ping to that you formerly did not. i3d.net is the group providing the managed infrastructure, it appears and they have a page on how to collect the data they need to assist you.
I was finally able to play Operations without getting kicked to a South American server. Also Frontlines and Conquest are showing more server options to me with normal pings.
EA chat assistance was only helpful to a point.
Awesome find. I have a ticket open with them now with the MTR they are requesting on their support page. Hopefully something comes from it. Thanks!
