yea we all knew this is server side error related. do you have any solutions?
Amazing stuff, thanks @BuggeX!
So, mine doesn’t show the same error:
[2022.07.06-09.46.47] Loader initialized.
[2022.07.06-09.46.47] [Connection] Connecting to URL: https://download.eac-cdn.com/api/v1/games/580/client/wow64_win64/download/?uuid=---
[2022.07.06-09.46.47] Download Progress: 0%. (it repeats a lot of times, always at 0%)
[2022.07.06-09.46.47] [Connection] Connect result: No error (0) Response Code: 304 Destination IP: 108.139.134.122
[2022.07.06-09.46.47] No update needed.
[2022.07.06-09.46.47] Download Progress: 100%.
So I’ve pinged that IP 108.139.134.122 and got no errors:
Pinging server-108-139-134-122.for50.r.cloudfront.net [108.139.134.122] with 32 bytes of data:
Reply from 108.139.134.122: bytes=32 time=30ms TTL=243
Reply from 108.139.134.122: bytes=32 time=32ms TTL=243
Reply from 108.139.134.122: bytes=32 time=33ms TTL=243
Reply from 108.139.134.122: bytes=32 time=63ms TTL=243
Ping statistics for 108.139.134.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 63ms, Average = 39ms
So, it doesn’t seem related to this EAC if Offline bug 
And a quick GeoIP shows:
| IP Address | Country Code | Location | Network | Postal Code | Approximate Coordinates* | Accuracy Radius (km) | ISP | Organization | Domain | Metro Code |
|---|---|---|---|---|---|---|---|---|---|---|
| 108.139.134.122 | US | United States, | ||||||||
| North America | 108.139.128.0/20 | 37.751, | ||||||||
| -97.822 | 1000 | Amazon CloudFront | Amazon CloudFront | cloudfront.net |
Getting this error repeatedly on NA East - Galatur ever since July 5th; I was able to play without issues the day before (July 4th).
This error message shows up within 10 minutes of connecting to Galatur:
Cannot connect to the server. Exiting the game. [EAC Offline]
Waiting for the news about that
Mine looks similar to yours, does a ton of lines of [2022.07.06-12.57.43] Download Progress: 0%.
Then the bottom says: [2022.07.06-12.57.44] [Connection] Connect result: No error (0) Response Code: 304 Destination IP: 108.138.246.40
[2022.07.06-12.57.44] No update needed.
[2022.07.06-12.57.44] Download Progress: 100%.
It will not load after that, it just cuts out, does not even load up the game.
one full day passed because this problem started yesterday nigth so almost 24 hours and still no solution …
1 Like
Ok, so let us try and find the culprit of this SERVER SIDE ERROR…
Can you guys ask one of your friends that is able do play on any SA server without this EAC offline error to check the logs on %appdata%\EasyAntiCheat\580\loader.log and post here so we can compare to a “control” log?
SA - Kazeros
Desde o dia 05/06/22
3 Likes
up for visibility
whales must be very happy at this point, i mean 1 day to get a response and still no fix lmao
Maintenance came and went and its still happening.
@Roxx I know you’re not responsible for this but why is the team not taking this issue seriously? How much longer will we have to deal with this?
I just want to play the game.
1 Like
you are lucky you havent lost anything (legion raid entries, argos entries) related to this yet.
lost a valtan run and expecting a response that good luck next week
I didn’t lose any of those because I didn’t even try to queue. Been having this issue for two days already, and last week I had it for three in a row.
This is ridiculous. I just want to be able to play. I never complained or demanded anything from AGS/SG. I just want. To play. The damn game.
The CM are starting to answer some other topics regarding “bloodstone compensation”, yeah, that thing has a higher priority than our puny “EAC-is-offline-so-you-can’t-play-the-game”.
Let us all join hands and hope everyone else got their bloodstone compensation on their universal storages!!!
yea so fking bored here. imagine wasted hours and hours to farm, hone your gear, then get disconnected due to THEIR ERROR when doing one of the most important activity of the week Legion Raid, and was told to fkc off
1 Like
by the way, if you get DC-ed due to this and your team completes the raid, you will get locked out with no re-entry tickets. they will not care and will not help you if this happens to you
Still no fix? It’s a whole day already.
1 Like
It seems at the moment “there is no actions to fix this issue” 
It’s a similar situation as ours, but his was not as severe, but ppl are getting dc’d anyway.