Escape from Tarkov error 614: "Matching is disabled"
Pressing Play or start matching shows "One or more errors occurred. 614 - Matching is disable..." straight away and every time. Restarting the launcher and the game doesn't change it.
Also appears as: 614 - Matching is disabled, One or more errors occurred. 614, tarkov error 614, error 614 tarkov, tarkov matching is disabled, tarkov 614 matchmaking disabled pve, tarkov can't start matching pve
Error 614 looks like matchmaking being switched off on Battlestate's side, not a problem on your PC. Two Steam threads opened on 16 October 2026, within about 20 minutes of each other and shortly after a server-side technical update, and around 11 posters reported the same error. Both thread titles are cut off by Steam at "Matching is disable", so "Matching is disabled" is our reading of the dialog.
Posters in PvE and one in the PvP season hit it, and one said they could only play in local (offline) PvE. Battlestate has not replied in either thread, and nobody has linked the error to the update with any official statement. We don't know whether it has cleared. An earlier 9 October Reddit thread also had 614 popping up repeatedly.
No problems reported in the last 15 minutes.
Is Escape from Tarkov down right now? Live reports →What to try
- 01Reported
Check the status page and Battlestate's channels for an update or outage
Check the live Escape from Tarkov status page and Battlestate's own channels for a technical update or maintenance. The error appeared shortly after a server-side technical update on 16 October, per the posters. If one is active, wait for it to finish and try again.
- 02Reported
Restarting the launcher and game did not help reporters
The original poster said they restarted both the launcher and the game and the error kept coming back, so a restart is unlikely to clear it while the cause is on the server.
- 03Unconfirmed
Reinstall BattlEye (one reply, unconfirmed)
On 9 October a r/EscapefromTarkov thread asked what Error 614 is, after repeated pop-ups and crashes. One reply said uninstalling and reinstalling BattlEye "100% fixes it". The original poster later wrote "its fixed now" without saying what fixed it, and the 16 October wave started minutes after a server-side update, so treat this as unproven.
- 04Unconfirmed
Local (offline) PvE still worked for one poster
One poster said they could only play in local server mode while 614 appeared. That is one report, and it doesn't fix the error for online play.
- 05Reported
See the other Tarkov matchmaking error pages
Different messages can appear at the same stage; see errors occurred during matchmaking and invalid matchmaking operation.
- 06Unconfirmed
No confirmed fix yet; this page will be updated
No confirmed fix yet; this page will be updated. Battlestate has not replied in either Steam thread and no workaround has been confirmed.
Did this fix it for you?
Your answer helps the next player know whether these steps are worth trying first.
Hit this error? Leave a comment
Say where you are, what you see on screen, and whether any fix worked for you.
No links. Anonymous, no account. Keep it about the game.
What people are saying
Notes from players who've hit this one โ no time limit, an answer from months ago is still an answer.
- Nothing reported here yet.
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
Other Escape from Tarkov error codes
Recently added
- AION 2 "insufficient gameplay record" market listing block
- ARC Raiders error ARMR0014 on Storms and Night Raids
- Enshrouded server exits 0xC0000135 on Windows Server Core (fix)
- Gears of War: E-Day stuck on "Fetching Data" (fix)
- Gears of War: E-Day lucas-gnasher: reward expired
- Gears of War: E-Day reaver-tyrus: can't queue ranked
- Valheim server "App 896660 state is 0x6" after update (fix)
- Valheim Unity crash error (0xc0000005): what to try