Forum Discussion

download333's avatar
download333
7 years ago

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

Tried to play again today after some time away from the game and it no longer will start, just gives that error message.

I tried all the other fixes and nothing worked so I took a look at the connections that Origin and Apex were making using TCPView. It looks like they're trying to make connections to a server at 159.153.190.222 by the name of proxy.novafusion.ea.com

It gets as far as a SYN_ACK before the connection hangs. Using nmap to check for open ports from my computer shows that the target ports 80 and 443 are filtered. I tried using some online port scanning services and they had no trouble connecting to port 443 at that IP so it does seem connectable from other places.

Next thing I tried was running traceroute to see where the traffic is getting blocked:

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

  1     4 ms     9 ms     8 ms  192.168.1.1
  2    25 ms    13 ms    25 ms  96.120.103.9
  3    12 ms    19 ms    19 ms  po-109-rur02.spokane.wa.seattle.comcast.net [68.86.98.249]
  4    20 ms    29 ms    28 ms  be-37-ar01.seattle.wa.seattle.comcast.net [68.86.96.5]
  5    35 ms    29 ms     *     lag-16.ear2.seattle1.level3.net [4.68.71.73]
  6     *       49 ms    48 ms  4.69.214.74
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.

It looks like the Level3 router at 4.69.214.74 is blocking traffic to that destination for some people. I don't know exactly how to contact them about this to see if they can fix it though. Is there a procedure for contact when an internet backbone provider blocks your traffic?

Edit: Tried running a traceroute from a free traceroute service and it also shows traffic being blocked at a Level3 router (though a different one than the one blocking my traffic). It seems like they have a blocking policy in place for their whole network. It's not just a misconfiguration of one router.

Edit for workaround: Go grab the Windscribe VPN software, set it to Switzerland, and turn it on. Open the game. As soon as it starts you can turn off Windscribe, as it only needs the alternate routing path for activation the first time you start the game.

7 Replies

  • Dangerdad137's avatar
    Dangerdad137
    7 years ago

    It doesn't appear to be just Level 3.  Using a VPN to Texas, I get the following:

    tracert proxy.novafusion.ea.com

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

    1 54 ms 53 ms 54 ms 10.87.10.1
    2 54 ms 54 ms 55 ms ip-253-232-239-173.texas.us.northamericancoax.com [173.239.232.253]
    3 56 ms 55 ms 54 ms 199.36.220.176
    4 54 ms 55 ms 55 ms te0-2-0-1.rcr52.dfw06.atlas.cogentco.com [38.122.200.225]
    5 56 ms 55 ms 55 ms be3681.ccr32.dfw01.atlas.cogentco.com [154.54.46.217]
    6 56 ms 56 ms 63 ms be2764.ccr41.dfw03.atlas.cogentco.com [154.54.47.214]
    7 * * * Request timed out.
    8 55 ms 56 ms 55 ms 4.69.209.29
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 94 ms 94 ms 94 ms 159.153.188.7
    14 91 ms 89 ms 90 ms proxy.novafusion.ea.com [159.153.190.222]

  • IMHwan's avatar
    IMHwan
    7 years ago

    Same issue here with Google Fiber from Irvine, CA.

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

    ...

    4 3 ms 2 ms 2 ms 10.26.1.194
    5 3 ms 2 ms 3 ms 23-255-225-168.mci.googlefiber.net [23.255.225.168]
    6 3 ms 3 ms 5 ms 23-255-225-124.mci.googlefiber.net [23.255.225.124]
    7 * * * Request timed out.
    8 5 ms 5 ms 4 ms ae4.pr01.lax101.googlefiber.net [192.119.17.183]
    9 4 ms 4 ms 4 ms 7-1-4.ear1.losangeles6.level3.net [4.14.190.5]
    10 * 5 ms 4 ms 4.69.214.74
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.

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

  • Unic0rn_Princes's avatar
    Unic0rn_Princes
    7 years ago

    Same thing, CenturyLink in the Phoenix AZ Metro area.  I can't do ANYTHING in Origin.

    1 <1 ms <1 ms <1 ms modem.domain [192.168.0.1]
    2 51 ms 42 ms 44 ms phn4-dsl-gw01.phn4.qwest.net [71.32.112.1]
    3 29 ms 44 ms 27 ms 71-32-113-1.phn4.qwest.net [71.32.113.1]
    4 * * 666 ms 209.181.128.2
    5 45 ms 47 ms 45 ms 4.69.214.66
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.

  • d_latch_69's avatar
    d_latch_69
    7 years ago
    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),
  • bleeeeet's avatar
    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's avatar
    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.
  • GutterB0nes's avatar
    GutterB0nes
    7 years ago

    Ya there is definitely some issues with the routing going on. The game was fine last week and the past few days there has been connection issues galore on both pc and ps4. traceroutes show quite a few timeouts when just last week there was only a few. A couple timeouts here and there are OK though, but something is definitely messed up somewhere.

About Apex Legends Technical Issues

Having issues with Apex Legends? Join here to find help with connectivity, performance issues, crashes and more.37,410 PostsLatest Activity: 5 hours ago