258 replies to this topic

[Wildcat22]

Played two matches 6/18 mid morning MST. Tried at 23:00 and began getting the 'Error Code 13'. Just Tried again 06/19 at 07:00 MST. Same Error. Sent an Email.

[DevilGoh]

same

[LLando]

Same here.

[Shado324]

same in Boston, Ma

[Augustus Ull]

I am now a member of the 'Error Code 13' club as well.

[Kobzarrr]

same -error 13 ,mid europe , tracert 192.99.109.129 finished with ping 148 (its usual ping for me )

[Oberst Jaime Wolf]

Same Here in Germany

[G A R G A N T U A]

same. 171 players are online somehow. It's the lowest online activity for a long time, except maintenance works. So, the problem is global. 1 day of premium as a compensation sounds reasonable, when the problem is fixed.

[Wildcat22]

Just got an automated tech support reply. Ran a trace and for some reason I can not connect to the NA servers with trace. Ping is OK which is weird, but with tracing it looks like the routing can not get to the servers in CA.

5 13 ms 15 ms 13 ms be-11-ar01.albuquerque.nm.albuq.comcast.net [96.108.67.109]
6 26 ms 25 ms 22 ms be-36811-cs01.1601milehigh.co.ibone.comcast.net [96.110.44.17]
7 22 ms 22 ms 22 ms be-1112-cr12.1601milehigh.co.ibone.comcast.net [96.110.39.82]
8 35 ms 36 ms 36 ms be-301-cr12.dallas.tx.ibone.comcast.net [96.110.38.98]
9 35 ms 35 ms 35 ms be-1412-cs04.dallas.tx.ibone.comcast.net [68.86.166.125]
10 37 ms 38 ms 36 ms be-3412-pe12.1950stemmons.tx.ibone.comcast.net [96.110.34.110]
11 36 ms 36 ms 35 ms be100.dfw-da2-bb2-a9.tx.us [192.99.146.77]
12 * * * Request timed out.
13 49 ms 51 ms 49 ms be100-1241.chi-5-a9.il.us [178.32.135.152]
14 70 ms 70 ms 70 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 72 ms 74 ms 70 ms ns577590.ip-51-222-109.net [51.222.109.38]

[lLinkZ]

same here gents cant log in error code 13

[Lord Refa]

Code XIII here also. Was winning too hard yesterday I guess.

[Shiloh Bane]

I know it's the Fathers Day holiday weekend, but I would think they'd have maybe 1 person on call that periodically checks the status of their game. I tried around Midnight last night to sign on and got the Error 13 message.

Here's its been over 9 hours and no response from them. Not even a "Hey, we got issues and are trying to fix them."

I like the idea of 1 day of premium time to make it better, but since I now won't be able to play for another week, just comp the stupid Mad Dog to everyone and move on to the July tourny.

But hey, this is just kinda the topper to a crap weekend, so I should have expected something else to go wrong.

Edited by Shiloh Bane, 19 June 2022 - 05:43 AM.

[Haisam]

Wildcat22, on 19 June 2022 - 05:26 AM, said:

Just got an automated tech support reply. Ran a trace and for some reason I can not connect to the NA servers with trace. Ping is OK which is weird, but with tracing it looks like the routing can not get to the servers in CA.

5 13 ms 15 ms 13 ms be-11-ar01.albuquerque.nm.albuq.comcast.net [96.108.67.109]
6 26 ms 25 ms 22 ms be-36811-cs01.1601milehigh.co.ibone.comcast.net [96.110.44.17]
7 22 ms 22 ms 22 ms be-1112-cr12.1601milehigh.co.ibone.comcast.net [96.110.39.82]
8 35 ms 36 ms 36 ms be-301-cr12.dallas.tx.ibone.comcast.net [96.110.38.98]
9 35 ms 35 ms 35 ms be-1412-cs04.dallas.tx.ibone.comcast.net [68.86.166.125]
10 37 ms 38 ms 36 ms be-3412-pe12.1950stemmons.tx.ibone.comcast.net [96.110.34.110]
11 36 ms 36 ms 35 ms be100.dfw-da2-bb2-a9.tx.us [192.99.146.77]
12 * * * Request timed out.
13 49 ms 51 ms 49 ms be100-1241.chi-5-a9.il.us [178.32.135.152]
14 70 ms 70 ms 70 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 72 ms 74 ms 70 ms ns577590.ip-51-222-109.net [51.222.109.38]

Some routers may deny IСMP , but the last hop is successful.
As far as I understand, in the automatic response they indicate game servers.
And the login server is not working (or the login server balancer)
How I studied expired certificates from them
I assume that the wrong one was applied on the balancer (the old config)

Edited by Haisam, 19 June 2022 - 05:43 AM.

[Tropico_Thunder]

Eastern USA error 13 here as well. I see two friends on discord that are logged on to MWO and Im waiting for a reply from them to see if they are really logged.

[Sgraz]

Error code 13 here too. Playing from Finland.

[Dankninja]

7:46 sunday morning happy fathers day yall ... and previously said im kinda annoyed my preimum time is running out with this ... been down at least 12 hours now and no response from tech support

[Saudaukar]

Client side issue will have to wait for a fix gents. Just happened to me this AM was laggy but still working for me late last night.

[DasMeenLeem]

Same with Error 13...
No wonder the Server status reports "operational" on the login servers....
"Last updated Wednesday 13t October 2021 11:03:57" LMAO

[CR0N05]

I will preorder a crusader if PGI hires a weekend tech to reboot the server.

[butchbottom]

Shiloh Bane, on 19 June 2022 - 05:42 AM, said:

I know it's the Fathers Day holiday weekend, but I would think they'd have maybe 1 person on call that periodically checks the status of their game. I tried around Midnight last night to sign on and got the Error 13 message.

Here's its been over 9 hours and no response from them. Not even a "Hey, we got issues and are trying to fix them."

I like the idea of 1 day of premium time to make it better, but since I now won't be able to play for another week, just comp the stupid Mad Dog to everyone and move on to the July tourny.

But hey, this is just kinda the topper to a crap weekend, so I should have expected something else to go wrong.

love u hope your weekend ends up better than expected