Titanfall PC connection issues fixed, Respawn says

4.6
Error Code 503 should no longer plague users

Respawn Entertainment says it has fixed issues which kept Titanfall players from connecting to the game on PC.

The official Titanfall Twitter account responded to hundreds of players who reported receiving an error code 503 when attempting to connect to the game's servers Tuesday night through Wednesday morning.

The PC version of Titanfall launched exclusively through Origin, Electronic Arts' digital distribution platform. It is supported with the same cloud servers that power the Xbox One version of the game.

Xbox Live issues similarly befuddled Xbox One players on Tuesday, though Microsoft specified that it was a service-wide problem and "not a Titanfall issue".

Titanfall is available on PC and Xbox One in North America ahead of its rollout in other regions throughout the rest of the week. The Xbox 360 Titanfall release date is March 25 in the US and March 28 in Europe.



Posted:
Related Forum: Gaming Discussion

Source: http://www.computerandvideogames.com/453513/titanfall-pc-connection-issues-fixed-respawn-says/

Comments

"Titanfall PC connection issues fixed, Respawn says" :: Login/Create an Account :: 28 comments

If you would like to post a comment please signin to your account or register for an account.

MultitaskPosted:

Glad they fixed this i was getting this allot!.

MawderzPosted:

Oasis It took one day. That's how dedicated this dev team is. As long as they keep on top of any bugs like this then we should have no problems.


If it was cod it probably would of taken a few days to a week.

-CPPosted:

Thank God, it was getting annoying....

KopaPosted:

im really glad this is finally out

MaggardoPosted:

Thank goodness, when I get on I don't want no connection issues messing up the game.

ResortPosted:

im happy to see them fixing things fast and making their community happy

OasisPosted:

It took one day. That's how dedicated this dev team is. As long as they keep on top of any bugs like this then we should have no problems.

BxnHPosted:

I have never experienced this error?
But I'm using the Early startup exe to run it, as I'm from the UK.