My results aren't much different from yours, so i suspect its actually a problem on EA's end. Check their service status, there's a chance its the node you're connected to that's struggling but this is unlikely. Here are my own results..
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS C:\WINDOWS\system32> tracert bfbc2-ps3.gos.ea.com
Tracing route to bfbc2-ps3.gos.ea.com [159.153.64.173]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms HuskySense.localdomain [192.168.1.1]
2 11 ms 8 ms 7 ms 10.53.37.121
3 9 ms 9 ms 9 ms nott-core-2a-xe-10112-0.network.virginmedia.net [80.7.83.161]
4 * * * Request timed out.
5 * * * Request timed out.
6 23 ms 26 ms 19 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
7 20 ms 19 ms 19 ms 213.46.175.250
8 * * 93 ms ae4.cs3.lhr11.uk.eth.zayo.com [64.125.28.194]
9 * * * Request timed out.
10 94 ms * * ae23.cs3.iad93.us.eth.zayo.com [64.125.28.189]
11 94 ms 92 ms 91 ms ae22.er2.iad10.us.zip.zayo.com [64.125.29.121]
12 99 ms 91 ms 91 ms 64.125.199.190.t00673-02.above.net [64.125.199.190]
13 92 ms 99 ms 91 ms 159.153.92.98
14 93 ms 93 ms 91 ms 159.153.92.94
15 91 ms 92 ms 90 ms da2.gos.ea.com [159.153.64.173]
Trace complete.
PS C:\WINDOWS\system32>
Looks like it would be unplayable for me as well but all other services are working so the main culprit is EA's servers unfortunately 😞 contact their support or check their site for any server issues - if EA bother to say! It is EA, after all..
Can you run a trace to 8.8.8.8 (google.dns) and post the results?
Kind regards,
Lee