[PC] Higher Ping to DICE EAST servers than normal

Question

Hello,&nbsp;I am hardwired into my router, not using WiFi. Over the past week or so, I am noticing about a 20 - 40ms increase in my ping relative to BF1 servers in the server browser in my region - EAST.&nbsp; Previously, I would get consistent 40-50ms. Now it will range from 60-80ms+.&nbsp;Also, prior did NOT have port forwarding for my desktop in my router with EA services, so I decided to allow the ports designated for BF1 in this post https://help.ea.com/en-us/help/pc/connection-troubleshooting-advanced-pc/. This yielded no change, unfortunately. I also tried the other steps outlined such as DNS cache flush and enabling UPnP. Also to no avail.I decided to begin viewing the connection status on my side. My modem is a DOCSIS 3.0 compliant and specs on all downstream channels are within normal&nbsp;SNR ~40dB and Power ~6dBmV. Upstream channels also appeared normal, though a little on the high side ~48dBmV.&nbsp;After a test on&nbsp;www.dslreports.com&nbsp;I decided to enable QoS on my router in an effort to minimize 'bufferbloat'. This helped with the bufferbloat rating on my test from dslreports.com, but did nothing to improve my ping relative to servers in the BF1 server browser.Next I decided to run some packet captures while in-game and found the destination address 104.153.84.194 with a large number of data exchange between me, as soon as I joined a server. I then ran a trace to that address and&nbsp;have the statistics from that attached in this post - labeled BF1trace.txt. You can roughly deduce my location based on this and why I choose EAST servers.&nbsp;I find it curious why during some of these hops, the data is going from east coast, west coast, back to east, ending west? I have the locales listed below in order of hop:1 -&nbsp; &nbsp; me2 -&nbsp; &nbsp; private address, probably a ISP CO or dist block close to me3,4 - Local ISP router5 -&nbsp; &nbsp; same ISP but in Phoenix, AZ6 -&nbsp; &nbsp; Westbury, NY7 -&nbsp; &nbsp; Seattle, WA8,9 -&nbsp;El Segundo, CA10 -&nbsp; Los Angeles, CA11 -&nbsp; El Segundo, CA12 -&nbsp; New York, NY13 -&nbsp; Othello, WALooking at the path this data is taking, hop 6 goes east then back west in 7. Down to CA from hops 8-11. Back east on hop 12, then finally west at the destination?Hops 6-12 subnets are owned by NTT Communications and I'm not sure if EA is using their services for the hosting of game communication. The final destination address carries the EA designation, but of course, I am not certain of it's function.Apologies for the long post, but I am not sure this is all my ISP's fault or not. The majority of this traffic is external to my locale's ISP excluding the one hop to Phoenix, but that has very minimal latency compared to hops after.Any insight is appreciated. Again, apologies for the long-winded post.-Skag

skagnatti · Answer

Bumping this as I discovered another glaring routing issue with the Operations game mode. Particularly when you choose to 'Join any Operation'&nbsp; from the Operations menu.I was dumped into a South American server. This was the path data was taking Louisiana to Brazil for some reason. Pathping does not see the hops with no response, but MTR does. This is also attached to the post.Very frustrating as my ability to play this game mode is more or less impossible from my region at the moment.|------------------------------------------------------------------------------------------||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WinMTR statistics&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Host&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp; %&nbsp; | Sent | Recv | Best | Avrg | Wrst | Last ||------------------------------------------------|------|------|------|------|------|------||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 0 |&nbsp; 366 |&nbsp; 366 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 2 |&nbsp;&nbsp;&nbsp; 0 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10.132.88.1 -&nbsp;&nbsp;&nbsp; 3 |&nbsp; 331 |&nbsp; 322 |&nbsp;&nbsp;&nbsp; 5 |&nbsp;&nbsp;&nbsp; 9 |&nbsp;&nbsp; 37 |&nbsp;&nbsp;&nbsp; 8 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 68.11.12.178 -&nbsp;&nbsp;&nbsp; 4 |&nbsp; 327 |&nbsp; 317 |&nbsp;&nbsp;&nbsp; 6 |&nbsp;&nbsp;&nbsp; 9 |&nbsp;&nbsp; 29 |&nbsp;&nbsp;&nbsp; 7 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 68.11.14.82 -&nbsp;&nbsp;&nbsp; 4 |&nbsp; 319 |&nbsp; 307 |&nbsp;&nbsp;&nbsp; 6 |&nbsp;&nbsp;&nbsp; 9 |&nbsp;&nbsp; 59 |&nbsp;&nbsp; 10 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 68.1.2.109 -&nbsp;&nbsp;&nbsp; 5 |&nbsp; 311 |&nbsp; 297 |&nbsp;&nbsp; 51 |&nbsp;&nbsp; 54 |&nbsp;&nbsp; 74 |&nbsp;&nbsp; 54 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dallas 129.250.194.173 -&nbsp; 4 |&nbsp; 323 |&nbsp; 312 |&nbsp;&nbsp; 51 |&nbsp;&nbsp; 56 |&nbsp;&nbsp; 86 |&nbsp;&nbsp; 60 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dallas 129.250.4.233 -&nbsp;&nbsp;&nbsp; 4 |&nbsp; 323 |&nbsp; 312 |&nbsp;&nbsp; 83 |&nbsp;&nbsp; 86 |&nbsp; 136 |&nbsp;&nbsp; 84 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dallas 129.250.5.15 -&nbsp;&nbsp;&nbsp; 4&nbsp; |&nbsp; 323 |&nbsp; 312 |&nbsp;&nbsp; 51 |&nbsp;&nbsp; 54 |&nbsp;&nbsp; 76 |&nbsp;&nbsp; 55 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Miami 129.250.2.218 -&nbsp;&nbsp;&nbsp; 4 |&nbsp; 327 |&nbsp; 317 |&nbsp;&nbsp; 86 |&nbsp;&nbsp; 91 |&nbsp; 178 |&nbsp;&nbsp; 92 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Miami 129.250.4.251 -&nbsp;&nbsp;&nbsp; 5 |&nbsp; 311 |&nbsp; 297 |&nbsp;&nbsp; 86 |&nbsp;&nbsp; 89 |&nbsp; 110 |&nbsp;&nbsp; 89 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Miami 129.250.2.203 -&nbsp;&nbsp;&nbsp; 4 |&nbsp; 327 |&nbsp; 317 |&nbsp;&nbsp; 86 |&nbsp;&nbsp; 90 |&nbsp; 117 |&nbsp;&nbsp; 91 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Miami 129.250.201.190 -&nbsp; 4 |&nbsp; 327 |&nbsp; 317 |&nbsp; 169 |&nbsp; 179 |&nbsp; 204 |&nbsp; 186 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No response from host -&nbsp; 100 |&nbsp;&nbsp; 74 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No response from host -&nbsp; 100 |&nbsp;&nbsp; 74 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No response from host -&nbsp; 100 |&nbsp;&nbsp; 74 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Brazil 177.72.240.116 -&nbsp;&nbsp; 78 |&nbsp;&nbsp; 90 |&nbsp;&nbsp; 20 |&nbsp;&nbsp;&nbsp; 0 |&nbsp; 252 |&nbsp; 296 |&nbsp; 292 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Brazil 54.240.244.180 -&nbsp;&nbsp; 78 |&nbsp;&nbsp; 90 |&nbsp;&nbsp; 20 |&nbsp;&nbsp;&nbsp; 0 |&nbsp; 248 |&nbsp; 805 |&nbsp; 180 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Brazil 54.240.244.16 -&nbsp;&nbsp; 74 |&nbsp;&nbsp; 94 |&nbsp;&nbsp; 25 |&nbsp;&nbsp;&nbsp; 0 |&nbsp; 206 |&nbsp; 321 |&nbsp; 175 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Brazil 54.240.244.23 -&nbsp;&nbsp; 74 |&nbsp;&nbsp; 94 |&nbsp;&nbsp; 25 |&nbsp;&nbsp;&nbsp; 0 |&nbsp; 299 |&nbsp; 337 |&nbsp; 303 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Brazil 54.240.244.21 -&nbsp;&nbsp;&nbsp; 4 |&nbsp; 327 |&nbsp; 317 |&nbsp; 284 |&nbsp; 293 |&nbsp; 318 |&nbsp; 295 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Brazil&nbsp; 54.233.122.32 -&nbsp;&nbsp;&nbsp; 4 |&nbsp; 323 |&nbsp; 312 |&nbsp; 279 |&nbsp; 291 |&nbsp; 312 |&nbsp; 290 ||________________________________________________|______|______|______|______|______|______|&nbsp;&nbsp; WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting &amp; Cloud Providerpathping 54.233.122.32Tracing route to ec2-54-233-122-32.sa-east-1.compute.amazonaws.com [54.233.122.32]over a maximum of 30 hops:&nbsp; 0&nbsp; PC&nbsp; 1&nbsp; router.asus.com&nbsp; 2&nbsp; 10.132.88.1&nbsp; 3&nbsp; mctycmtc01.no.no.cox.net [68.11.12.178]&nbsp; 4&nbsp; 68.11.14.82&nbsp; 5&nbsp; dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]&nbsp; 6&nbsp; ae-12.a02.dllstx09.us.bb.gin.ntt.net [129.250.194.173]&nbsp; 7&nbsp; ae-4.r11.dllstx09.us.bb.gin.ntt.net [129.250.4.233]&nbsp; 8&nbsp; ae-0.r22.dllstx09.us.bb.gin.ntt.net [129.250.5.15]&nbsp; 9&nbsp; ae-6.r21.miamfl02.us.bb.gin.ntt.net [129.250.2.218]&nbsp;10&nbsp; ae-2.r04.miamfl02.us.bb.gin.ntt.net [129.250.4.251]&nbsp;11&nbsp; ae-7.a00.miamfl02.us.bb.gin.ntt.net [129.250.2.203]&nbsp;12&nbsp; ae-1.amazon.miamfl02.us.bb.gin.ntt.net [129.250.201.190]&nbsp;13&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *Computing statistics for 300 seconds...&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Source to Here&nbsp;&nbsp; This Node/LinkHop&nbsp; RTT&nbsp;&nbsp;&nbsp; Lost/Sent = Pct&nbsp; Lost/Sent = Pct&nbsp; Address&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -PC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp; 1&nbsp;&nbsp;&nbsp; 0ms&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp; router.asus.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1/ 100 =&nbsp; 1%&nbsp;&nbsp; |&nbsp; 2&nbsp;&nbsp;&nbsp; 7ms&nbsp;&nbsp;&nbsp;&nbsp; 4/ 100 =&nbsp; 4%&nbsp;&nbsp;&nbsp;&nbsp; 3/ 100 =&nbsp; 3%&nbsp; 10.132.88.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp; 3&nbsp;&nbsp;&nbsp; 8ms&nbsp;&nbsp;&nbsp;&nbsp; 2/ 100 =&nbsp; 2%&nbsp;&nbsp;&nbsp;&nbsp; 1/ 100 =&nbsp; 1%&nbsp; mctycmtc01.no.no.cox.net [68.11.12.178]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp; 4&nbsp;&nbsp;&nbsp; 8ms&nbsp;&nbsp;&nbsp;&nbsp; 3/ 100 =&nbsp; 3%&nbsp;&nbsp;&nbsp;&nbsp; 2/ 100 =&nbsp; 2%&nbsp; 68.11.14.82&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp; 5&nbsp;&nbsp; 37ms&nbsp;&nbsp;&nbsp;&nbsp; 2/ 100 =&nbsp; 2%&nbsp;&nbsp;&nbsp;&nbsp; 1/ 100 =&nbsp; 1%&nbsp; dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp; 6&nbsp;&nbsp; 55ms&nbsp;&nbsp;&nbsp;&nbsp; 2/ 100 =&nbsp; 2%&nbsp;&nbsp;&nbsp;&nbsp; 1/ 100 =&nbsp; 1%&nbsp; ae-12.a02.dllstx09.us.bb.gin.ntt.net [129.250.194.173]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp; 7&nbsp;&nbsp; 53ms&nbsp;&nbsp;&nbsp;&nbsp; 6/ 100 =&nbsp; 6%&nbsp;&nbsp;&nbsp;&nbsp; 5/ 100 =&nbsp; 5%&nbsp; ae-4.r11.dllstx09.us.bb.gin.ntt.net [129.250.4.233]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp; 8&nbsp;&nbsp; 54ms&nbsp;&nbsp;&nbsp;&nbsp; 3/ 100 =&nbsp; 3%&nbsp;&nbsp;&nbsp;&nbsp; 2/ 100 =&nbsp; 2%&nbsp; ae-0.r22.dllstx09.us.bb.gin.ntt.net [129.250.5.15]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp; 9&nbsp;&nbsp; 86ms&nbsp;&nbsp;&nbsp;&nbsp; 1/ 100 =&nbsp; 1%&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp; ae-6.r21.miamfl02.us.bb.gin.ntt.net [129.250.2.218]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4/ 100 =&nbsp; 4%&nbsp;&nbsp; |&nbsp;10&nbsp;&nbsp; 84ms&nbsp;&nbsp;&nbsp;&nbsp; 6/ 100 =&nbsp; 6%&nbsp;&nbsp;&nbsp;&nbsp; 1/ 100 =&nbsp; 1%&nbsp; ae-2.r04.miamfl02.us.bb.gin.ntt.net [129.250.4.251]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp;&nbsp; |&nbsp;11&nbsp;&nbsp; 86ms&nbsp;&nbsp;&nbsp;&nbsp; 5/ 100 =&nbsp; 5%&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp; ae-7.a00.miamfl02.us.bb.gin.ntt.net [129.250.2.203]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 95/ 100 = 95%&nbsp;&nbsp; |&nbsp;12&nbsp; ---&nbsp;&nbsp;&nbsp;&nbsp; 100/ 100 =100%&nbsp;&nbsp;&nbsp;&nbsp; 0/ 100 =&nbsp; 0%&nbsp; ae-1.amazon.miamfl02.us.bb.gin.ntt.net [129.250.201.190]Trace complete.

Answer

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

skagnatti · Answer

Thanks, LestatI 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.&nbsp;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...&nbsp;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.&nbsp;|------------------------------------------------------------------------------------------|| 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 &amp; Cloud Providerpathping 159.153.155.35Tracing route to va1bf1prgm0262.ea.com [159.153.155.35]over a maximum of 30 hops:0 PC1 router.asus.com2 10.132.88.13 68.11.12.704 68.11.14.825 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]6 68.105.30.227 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] Ill10 ae3.cs2.dca2.us.eth.zayo.com [64.125.29.44] Colorado11 ae27.cr2.dca2.us.zip.zayo.com [64.125.30.249] TX12 ae1.er2.iad10.us.zip.zayo.com [64.125.20.122] Colorado13 64.125.199.190.t00673-02.above.net [64.125.199.190] Mass14 159.153.92.78 California15 va1bf1prgm0262.ea.com [159.153.155.35] CaliforniaComputing statistics for 375 seconds...Source to Here This Node/LinkHop RTT Lost/Sent = Pct Lost/Sent = Pct Address0 PC 0/ 100 = 0% |1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com5/ 100 = 5% |2 9ms 11/ 100 = 11% 6/ 100 = 6% 10.132.88.10/ 100 = 0% |3 9ms 7/ 100 = 7% 2/ 100 = 2% 68.11.12.700/ 100 = 0% |4 9ms 8/ 100 = 8% 3/ 100 = 3% 68.11.14.820/ 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.223/ 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.780/ 100 = 0% |15 89ms 13/ 100 = 13% 0/ 100 = 0% va1bf1prgm0262.ea.com [159.153.155.35]Trace complete.

Answer

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.

skagnatti · Answer

Hey JakeMy 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.

Forum Discussion

[PC] Higher Ping to DICE EAST servers than normal

6 Replies

About Battlefield Franchise Discussion

Recent Discussions

Battlefield 3 – “Could not activate” / Signed in as blank

BF 1 SE falsely claims an expired trial

Weekly weapons Scrap Exchange updates

i dont get the unlocks from the story

my bf4 steam premium edition bf4 shows up as regular BF4 in the EA app