Forum Discussion
Hey unfortunately this isnt a fix or answer but I wanted you to know you arent alone. I too (PS4 though) opened all my ports.. i even made both PS4s static and i found that during their tracert program that the NTT and 2 EA servers were dropping 100% of packets i sent.
* Unknown Host * 165.254.191.122 11 40ms 100% 0 / 103
unknown.prolexic.com 209.200.144.194 12 27ms 27ms 0% 103 / 103 27ms / 32ms
unknown.prolexic.com 209.200.144.199 13 30ms 30ms 0% 103 / 103 29ms / 48ms
unknown.prolexic.com 209.200.168.132 14 31ms 31ms 0% 103 / 103 30ms / 36ms
* Unknown Host * 159.153.93.2 15 31ms 100% 0 / 102
* Unknown Host * 159.153.225.65 16 29ms 30ms 0% 102 / 102 29ms / 50ms
fert01-eqx-iad.ea.com 159.153.226.65 17 41ms 100% 0 / 102
I was passed off by an agent and a specialist saying "contact your ISP"
So unless you have Frontier DSL in the middle of the US, i have a hard time believing ISPs are blocking EA servers somehow.
https://help.ea.com/en-us/help/faq/connection-troubleshooting-basic/
try the Run a UOTrace bit and see what servers drop you
Thanks, Lestat
I was on chat a few times with EA support, but that only yielded a "it's not us but you." and "Post it on the Answers forum as our developers will notice and resolve it." The UOTrace shows the same information WinMTR shows.
Found something else with the Frontlines game mode and inefficient routing to the endpoint. Why go from Illinois to Colorado, to Texas, back to Colorado, then 2/3 across the country to Massachusetts, then end in the other side of the US, in California ... when the server states in its description US EAST? And three of the Frontlines servers I joined all went to the same ending address 159.156.155.35 so I presume they are separated by port in the hosting server.
I miss the days of dedicated servers rented by gaming communities... Seems a shame for what, IMO, is a very good game in its own right, to have a poor infrastructure implementation. This was not an issue at launch; quite the opposite - at least for my region.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| - 0 | 670 | 670 | 0 | 0 | 8 | 0 |
| 10.132.88.1 - 6 | 554 | 525 | 5 | 10 | 47 | 13 |
| 68.11.12.70 - 6 | 546 | 515 | 6 | 10 | 49 | 8 |
| 68.11.14.82 - 6 | 546 | 515 | 6 | 11 | 50 | 7 |
| 68.1.2.109 - 5 | 566 | 540 | 50 | 56 | 94 | 53 |
| 68.105.30.22 - 5 | 566 | 540 | 51 | 66 | 184 | 55 |
| 64.125.20.233 - 6 | 558 | 530 | 51 | 56 | 102 | 54 |
| 64.125.30.182 - 5 | 566 | 540 | 66 | 71 | 109 | 68 |
| 64.125.28.102 - 6 | 558 | 530 | 66 | 84 | 147 | 99 |
| 64.125.29.44 - 6 | 542 | 510 | 65 | 73 | 122 | 67 |
| 64.125.30.249 - 7 | 538 | 505 | 66 | 70 | 113 | 73 |
| 64.125.20.122 - 6 | 546 | 515 | 65 | 70 | 109 | 69 |
| 64.125.199.190 - 6 | 550 | 520 | 66 | 70 | 111 | 69 |
| 159.153.92.78 - 6 | 546 | 515 | 66 | 74 | 282 | 68 |
| 159.153.155.35 - 7 | 538 | 505 | 85 | 90 | 127 | 89 |
|________________________________________|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
pathping 159.153.155.35
Tracing route to va1bf1prgm0262.ea.com [159.153.155.35]
over a maximum of 30 hops:
0 PC
1 router.asus.com
2 10.132.88.1
3 68.11.12.70
4 68.11.14.82
5 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
6 68.105.30.22
7 ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
8 ae27.cs2.dfw2.us.eth.zayo.com [64.125.30.182]
9 ae5.cs2.iah1.us.eth.zayo.com [64.125.28.102] Ill
10 ae3.cs2.dca2.us.eth.zayo.com [64.125.29.44] Colorado
11 ae27.cr2.dca2.us.zip.zayo.com [64.125.30.249] TX
12 ae1.er2.iad10.us.zip.zayo.com [64.125.20.122] Colorado
13 64.125.199.190.t00673-02.above.net [64.125.199.190] Mass
14 159.153.92.78 California
15 va1bf1prgm0262.ea.com [159.153.155.35] California
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC 0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com
5/ 100 = 5% |
2 9ms 11/ 100 = 11% 6/ 100 = 6% 10.132.88.1
0/ 100 = 0% |
3 9ms 7/ 100 = 7% 2/ 100 = 2% 68.11.12.70
0/ 100 = 0% |
4 9ms 8/ 100 = 8% 3/ 100 = 3% 68.11.14.82
0/ 100 = 0% |
5 38ms 8/ 100 = 8% 3/ 100 = 3% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
6 58ms 5/ 100 = 5% 0/ 100 = 0% 68.105.30.22
3/ 100 = 3% |
7 54ms 10/ 100 = 10% 2/ 100 = 2% ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
0/ 100 = 0% |
8 --- 100/ 100 =100% 92/ 100 = 92% ae27.cs2.dfw2.us.eth.zayo.com [64.125.30.182]
0/ 100 = 0% |
9 --- 100/ 100 =100% 92/ 100 = 92% ae5.cs2.iah1.us.eth.zayo.com [64.125.28.102]
0/ 100 = 0% |
10 --- 100/ 100 =100% 92/ 100 = 92% ae3.cs2.dca2.us.eth.zayo.com [64.125.29.44]
0/ 100 = 0% |
11 69ms 8/ 100 = 8% 0/ 100 = 0% ae27.cr2.dca2.us.zip.zayo.com [64.125.30.249]
3/ 100 = 3% |
12 70ms 11/ 100 = 11% 0/ 100 = 0% ae1.er2.iad10.us.zip.zayo.com [64.125.20.122]
2/ 100 = 2% |
13 --- 100/ 100 =100% 87/ 100 = 87% 64.125.199.190.t00673-02.above.net [64.125.199.190]
0/ 100 = 0% |
14 72ms 13/ 100 = 13% 0/ 100 = 0% 159.153.92.78
0/ 100 = 0% |
15 89ms 13/ 100 = 13% 0/ 100 = 0% va1bf1prgm0262.ea.com [159.153.155.35]
Trace complete.
- Anonymous9 years ago
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.
- 9 years ago
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.
- Anonymous9 years ago
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!
About Battlefield Franchise Discussion
Recent Discussions
- 18 hours ago