Forum Discussion

Re: More information about "We've noticed your computer is currently offline..."

Likewise, I tried pinging it from two different hosts in seattle, WA. One succeeded, the other did not. Opened this in wireshark to analyze, no RST packet was sent. I am not getting a response from that host on my main desktop. It is probably firewalled. My guess is that EA needs to fix their loadbalancer config.

==============Host A===============
traceroute to proxy.novafusion.ea.com (159.153.190.222), 30 hops max, 60 byte packets
1 * * *
2 et-0-0-1-1.cr4-sea2.ip4.gtt.net (173.205.48.77) 1.156 ms 129.250.199.213 (129.250.199.213) 0.693 ms 0.651 ms
3 ae-14.r05.sttlwa01.us.bb.gin.ntt.net (129.250.5.133) 0.544 ms et-0-0-35.cr5-sea2.ip4.gtt.net (89.149.130.34) 5.133 ms ae-14.r05.sttlwa01.us.bb.gin.ntt.net (129.250.5.133) 0.476 ms
4 ae-0.level3.sttlwa01.us.bb.gin.ntt.net (129.250.9.169) 0.524 ms 0.689 ms 0.866 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
PING proxy.novafusion.ea.com (159.153.190.222) 56(84) bytes of data.
64 bytes from proxy.novafusion.ea.com (159.153.190.222): icmp_seq=1 ttl=241 time=100 ms
64 bytes from proxy.novafusion.ea.com (159.153.190.222): icmp_seq=2 ttl=241 time=100 ms
64 bytes from proxy.novafusion.ea.com (159.153.190.222): icmp_seq=3 ttl=241 time=100 ms
64 bytes from proxy.novafusion.ea.com (159.153.190.222): icmp_seq=4 ttl=241 time=100 ms
64 bytes from proxy.novafusion.ea.com (159.153.190.222): icmp_seq=5 ttl=241 time=100 ms
64 bytes from proxy.novafusion.ea.com (159.153.190.222): icmp_seq=6 ttl=241 time=100 ms
64 bytes from proxy.novafusion.ea.com (159.153.190.222): icmp_seq=7 ttl=241 time=100 ms

==============Host B===============
Tracing route to proxy.novafusion.ea.com [159.153.190.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.4.1
2 8 ms 8 ms 9 ms 96.120.102.81
3 10 ms 12 ms 9 ms po-103-rur101.seattle.wa.seattle.comcast.net [162.151.209.101]
4 12 ms 9 ms 9 ms po-2-rur102.seattle.wa.seattle.comcast.net [69.139.161.38]
5 8 ms 8 ms 11 ms be-120-ar01.seattle.wa.seattle.comcast.net [69.139.160.241]
6 * * * Request timed out.
7 37 ms 37 ms 37 ms 4.69.214.66
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.

ping proxy.novafusion.ea.com

Pinging proxy.novafusion.ea.com [159.153.190.222] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 159.153.190.222:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

2 Replies

bleeeeet
7 years ago
I spoke to support on the phone yesterday and they told me the team is aware of the issue and are working to release a patch. No ETA on the fix at all.
Update : Just spoke with tech support again and they said the exact same thing thanking us for our patience and there is no ETA because they don't want to set false expectations.
I'm mildly concerned that there has been no official post from EA about the issues for those of us who are locked out for 3 days. There should be a sticky thread so folks know whats going on and it gives a slight sense that its important to them that they get us online again.
Nightstick24
7 years ago
Grab a free VPN like ProtonVPN, launch the game, exit out, disable the VPN, and you should be able to get in just fine. Not sure what's causing it, but that's the fix that's been working for people.