INVESTIGATION: Disconnects (Error Code: 2001, 2014, 3013, 4001) & General Connectivity Issues

FIX YOUR SERVERS!!! My internet connection hasn’t changed in 2 years and half and you broke the game with some recent patch!

1st machine: errors 2001 at 20:06, 2014 at 20:10 both (machines), 2014 at 20:18:

console-2025-09-06-17.48.54-9eb584ed-1a73-4410-947a-5c524a9d2e48.log (157.9 KB)

console-2025-09-06-17.58.50-3fa866e4-5951-4c01-93c4-e6a66ed64b7a.log (241.9 KB)

2nd machine: 2014 at 20:10 both (machines), 2001 at 20:20, 2014 at 20:25:

console-2025-09-06-17.50.19-e00644e1-085b-4a3f-9ecc-285fc19fe541.log (396.7 KB)

Now im facing nothing but 2001 and 2014s with some Slow Fatshark Server Errors. Cant even connect with 170 pings. Used to run fine at 240 plus. Now all I see are enemies sliding and flying around then get kicked asking to reconnect

  • Describe your issue, including the most common error code you receive (if any)
    Mostly 2001 2014 sometimes I do be seeing these 3013 4001 and a lot of Slow Fatshark Servers in Red Popup to the left.

  • Which platform are you playing on, and are you using a Cloud service (such as GeForce Now)? Xbox PC app. Direct Launcher Launch from Win Desktop.

  • Which country are you playing from, and what’s the name of your internet service provider (ISP)? India, Kerala Vision Broadband Ltd

  • How are you connected to the internet (e.g. wired, Wi-Fi, using a booster, etc.)? Fiber, Wired Cat6 cable, 200 mbps upload and 200 mbps download

  • Is this a consistent issue, or does it occur during specific times (such as peak hours)? Can happen at any time. Unpredictable.

  • If you’re using mods, have you tried disabling them to see if the issues persist?

    • This is important, as we’ve seen an increase in mods causing connectivity-related issues

    No Mods

Issue Type (Required):

Loadouts

Issue Description (Required):

cannot play game at all due to crashing [ error code 2011 disconnected from server
every time i select start
its constant cannot play at all since stupid hotfix was applied
why dont you roll it back and then try a different approach !!!
getting really boring now ,waiting to get it fixed
about time this error was sorted 11 days

Ever have this happen when playing without dog? Half my runs are 2014s with dog but I’ve been playing lone wolf for a few days and haven’t had any server crashes even after a clutch or big fight.

Issue Type (Required):

Performance

Issue Description (Required):

Lately (passed two weeks) I’ve noticed random full team disconnects where everyone lags for about 8 seconds then everyone is sent to operative select screen and the game of course is ended. This is especially annoying on Havoc since people who are climbing lose a try also the game are normally 20+ minutes sometimes depending on map and teams pace sometimes closer to an hour. Now imagine that gets cut short for some reason. Is there any fix for this recently started Disconnect or is this going to be a permanent thing now? (server related?)

Reproduction Rate (Required):

Common (<50%)

Platform (Required):

Xbox

Player ID (Optional):

FireStyleApe

[PC] Crash Report (Optional):

Play Havoc < randomly have full team disconnect < regret

1 Like

Yep this happened last night on havoc 40 arena map. Flawless game with a well oiled team. Whole team crashed to operative select after 45 f***ing minutes of nonstop sweats. We all quit the game because it was so deflating.

I only get 1 chance at a havoc mission per night due to the huge time and concentration commitment it demands.

Unbelievable that we all crashed out right at the end.

It usually counts as a loss too! To rub salt and pins into the wound.

3 Likes

Yeah, I was denied my H40 win time after time because of crashes. Did finally get it, but damn.

2 Likes

Hi all, I am aware some of you have experienced a decline in connectivity stability since the release of 1.8.6. I’ve been chatting to the team, and I’ll keep you posted as soon as I can.

5 Likes

Adding yesterday’s logs.

As always my specs are in my previous posts.

Comparatively it went better, I mean: it wasn’t peak hour and it disconnected without too much fuss (fewer visual lags and flying entities before the error).

1st machine: error 2001 at 20:24 (the 2nd computer got 2014 at the same time)

console-2025-09-09-18.09.43-572cc59d-c49e-40b6-8fe5-4101944e8051.log (303.1 KB)

2nd machine: error 2024 at 20:31

console-2025-09-09-18.13.37-cf42288e-98f0-41af-9deb-e7485e46bb2d.log (377.8 KB)

it seems dog is a problem right now… i played ogryn and without the dog and yet didnt got disconnected.
yet if there is at least 1 person with a dog in party ,game decide to crush (mostly when you clutch or the game send 2 waves at the same time (game event then boss spawn with a support of another wave ) ).
in game where i stayed solo killed plague ogryn and capitan the game didnt crush while if we had anyone playing with a dog companion it was almost guarantee that game would crush after you do the same.

2 Likes

adding last logs from the 2 PCs.

Machine 1: error 2014 at 20:35. Note: just before embarking the ship to evacuate from the mission groaners were running and flying through the air, but mission ended (probably) before it disconnected again.

console-2025-09-10-18.20.25-24a75a06-8b1a-479d-948c-46e6c8a604b4.log (236.3 KB)

Machine 2: error 2014 at 20:34 (just before the other PCs error)

console-2025-09-10-18.21.48-e21626c4-466c-4032-bdb7-eb7c3cc938e1.log (228.9 KB)

hello

16 days later and i still cannot play the game

looks to me like your not taking it seriously enough !!!

Did some more runs with and without a dog and can confirm that having a dog on the team is the cause of error 2014 in these scenarios.

@FatsharkJulia Maybe the devs can be made aware of this.

1 Like

adding today’s logs:

MACHINE 1: error 2001 at 18:40 and 20:06

console-2025-09-11-16.22.01-24d61e98-ee3f-45ea-8e99-7d2f0815883c.log (270.1 KB)

console-2025-09-11-17.57.57-32818a81-24e5-4348-b05f-22f02df6ec57.log (272.0 KB)

MACHINE 2: error 2001 at 20:22 and 2014 at 20:32

console-2025-09-11-17.59.29-88a4c9c2-b4ec-4808-9211-584f39572922.log (286.6 KB)

This has certainly piqued our interest! We’re looking in to this and @kejetok’s report above. Thanks for the information both :slight_smile:

1 Like

If anybody happens to spot any other situations (think certain locations in maps, actions, etc.) where disconnections with the dawg are more likely to occur, please let us know.

1 Like

so far we haven’t noticed anyh correlation with the dog(s). Lags and disconnections happen at the most crowdy moments and at peak hours. Like now.

Here are the logs, very bad games tonight.

MACHINE 1: error 2001 at 22:08, 2001 at 22:11, 2001 at 22:12 (both machines), 2014 at 22:19 and 3013 (failed reconnection)

console-2025-09-12-19.55.23-5982fcb6-a8d2-489c-a25d-18ef323f3b21.log (447.6 KB)

MACHINE 2: error 2014 at 22:10, 2001 at 22:12 (both machines), 2001 at 22:14, 2014 at 22:29.

console-2025-09-12-20.04.25-be490476-4381-4b1d-94f4-0c10a8e0c9e9.log (437.8 KB)

my friend in brazil get crazy dc sometimes when playing on us east, im guessing peak hours since its 6pm here in na east. 2001, 2014, everything

The most consistent way i got to get error 2014 is by playing arbitrator with the dog . Error 2014 happens after everyone in your team died making you last man standing and after cleaning all the enemy targeting player.

even after i revive everyone i could already call that crush is about to happen.

console-2025-09-13-14.03.49-61d13a52-e6a7-4dfe-b398-cef8fccb5f13.log (2.4 MB)
error 2014 around 16:01

today’s logs. Very bad unplayable games with flying enemies and non-registered commands (ex.: on weapons swap). I disconnected twice or thrice inside the last elevator. I have no words left to describe how dissapointed I am by this situation.

MACHINE 1: 2014 at 14:16, 2014 at 14:18, 2001 at 14:20, 20(can’t recall if 2001 or 2014) 14:23, 2001 at 20:24

console-2025-09-14-10.51.11-ff36534c-12e7-448b-99af-25655cbe6782.log (1.0 MB)

MACHINE 2: error 2001 at 14:04

console-2025-09-14-10.49.55-d1b03c0c-3615-4b7e-bb43-38c84d712cb9.log (661.7 KB)

BTW: second PC got one only error but saw flying enemies through the walls many many times for the whole games.