Fortnite queue diagnostics

Fortnite Matchmaking Error 1, 2 & 3 Fix (2026)

Read the exact message, separate an Epic-side queue failure from an Error 2 eligibility block, and repair only the local layer that is actually failing.

By 9 min read
MATCHMAKING // DIAGNOSTICCHECK
STATUS • MESSAGE • LOCAL
Error #1Match connection failed
Error #2Beacon or eligibility
Error #3Battle Buses are full
Quick answer

Check Epic status first. Then let the exact error text choose the next fix.

Epic says Matchmaking Errors #1, #2 and #3 are mainly caused by server maintenance or a network connection problem. If Matchmaking is down, wait. If services are operational, restart one clean queue and continue through clock, cache and connection checks. The exception is Error #2 saying you do not have permission: that usually needs an event-eligibility check, not a DNS fix.

Error meanings

Errors 1, 2 and 3 do not all describe the same failure

Do not start with a random fix. Read the complete line under the error number. The wording tells you whether Fortnite failed to connect to a match, could not reach a content service, blocked an event for eligibility, or simply had no immediate queue capacity.

Matchmaking Error #1Match connection

Fortnite could not connect your client to the match. Epic points first to Public Status, then to local connection troubleshooting when services are healthy.

Matchmaking Error #2Two possible routes

A content-beacon message is technical. A permission message is usually about the selected competitive event and its entry requirements.

Matchmaking Error #3Queue capacity

The Battle Buses are full. Wait a few minutes and retry before changing device settings. A widespread spike points back to Epic status.

Scope guard: Error 83 and 86 are party errors with their own workflow. Use the separate Fortnite Error 83 and 86 guide instead of mixing those fixes into this page.
First 60 seconds

Use this fix order before touching advanced network settings

The goal is to isolate the failing layer with the fewest changes. Test after every step. If the queue works, stop; stacking extra changes makes the real cause impossible to identify.

01Capture the full message

Record the number, complete wording, playlist, platform and time. Error #2 cannot be diagnosed from the number alone.

02Check Public Status

Look at Fortnite Game Services and Matchmaking. If either is degraded, local repairs cannot restore Epic’s service.

03Run one clean test

Leave the current queue, return to the lobby and try a normal public Battle Royale or Creative experience once.

04Restart the local path

When services are operational, restart Fortnite, the device and then the router before advanced DNS or proxy work.

Likely server-side

Friends on different networks fail at the same time, several playlists are affected, or Public Status reports a Fortnite Matchmaking incident. Wait and monitor the incident.

Likely local or account-specific

Public Status is healthy, another device or connection works, or only one competitive event rejects the account. Continue with the matching branch below.

Critical distinction

Matchmaking Error #2 has a technical form and a permission form

This is the most important part of the guide. Treating both Error #2 messages as the same problem wastes time and can lead players to change a healthy connection.

“Trouble connecting to content beacon service”

Use the technical route: status, clean restart, device clock, cache, DNS, proxy and local connection checks. Test a standard public playlist between steps.

“You don’t have permission to play this content”

Open the event lock or requirements panel. Confirm the event is live and check its current account level, rank, age, 2FA and qualification requirements.

Do not bypass event requirements. Epic’s current tournament page tells players to open the lock icon and review the missing requirements for that specific event. Rules can differ between events and change over time.
PC repair ladder

Fix local matchmaking connectivity on Windows without jumping to reinstall

Epic lists several local checks after server status. Work from reversible, low-cost actions toward advanced network changes. Keep Fortnite closed while clearing caches or changing network configuration.

Restart Fortnite and Epic Games Launcher completely

Exit both applications rather than only closing the visible window. Launch again and test a standard public playlist.

Synchronize the Windows clock

Open Time & language → Date & time, enable automatic time and time zone, then use Sync now.

Clear only the documented Launcher or device cache

Do not delete random Fortnite folders. Cache cleanup should target the named cache location for the affected platform.

Flush Windows DNS

Open Command Prompt as administrator, run ipconfig /flushdns, restart the Launcher and test again.

Check DNS, proxy and Hosts configuration

Disable an unintended proxy. Return custom DNS or Hosts entries to a known-good configuration before testing.

Close conflicting tools and submit a bug report

If the exact error survives every supported step, capture the message and submit an in-game bug report instead of repeating destructive reinstalls.

Different symptom? If Fortnite will not open or crashes before reaching the lobby, use the Fortnite crashing and not launching guide. That is a launch problem, not Matchmaking Error 1, 2 or 3.
Console workflow

Keep PlayStation, Xbox and Switch troubleshooting controlled

Start with the same status and exact-message checks used on PC. Then refresh the console session and network path. Menu names can change with system software, so use the platform’s current cache and network instructions.

PlayStationPS5 and PS4
  1. Close Fortnite completely.
  2. Restart the console, not Rest Mode.
  3. Confirm automatic date and time.
  4. Test the network connection.
  5. Clear console cache only if needed.
XboxSeries X|S and Xbox One
  1. Quit Fortnite from the guide.
  2. Restart the console fully.
  3. Check Xbox network status.
  4. Confirm automatic clock settings.
  5. Power-cycle the network path.
NintendoSwitch and Switch 2
  1. Close the software from HOME.
  2. Restart the console.
  3. Confirm internet clock settings.
  4. Test a standard playlist.
  5. Clear cache before reinstalling.

If matches connect but feel delayed or lossy, move to the dedicated Fortnite packet loss guide. If only the selected data center or ping is the concern, use the matchmaking region and ping guide.

Avoid wasted changes

Do not turn one matchmaking error into three new problems

The strongest troubleshooting is controlled troubleshooting. Preserve account links, settings and local data until the evidence points to them.

Do not unlink platform accounts

Errors 1, 2 and 3 do not justify risking progress or entitlement confusion.

Do not reinstall first

A reinstall cannot repair an active Epic outage or missing event qualification.

Do not change region at random

Leave matchmaking region on Auto during the first test.

Do not treat every Error #2 as DNS

The permission wording points to event access and eligibility.

Do not delete unknown folders

Clear only documented cache locations and preserve the exact error.

Do not follow old event requirements

Open the live event panel because eligibility can change.

FAQ

Fortnite Matchmaking Error 1, 2 and 3 FAQ

What causes Fortnite matchmaking error 1, 2 or 3?

Epic says these matchmaking errors are mainly connected to server maintenance or network connection problems. Error 2 can also be an eligibility message when an account does not meet the requirements for a competitive event.

What does Fortnite matchmaking error 1 mean?

Matchmaking Error 1 means Fortnite could not connect the client to the match. Check Epic Games Public Status first, retry a normal public playlist and continue with local connection troubleshooting only when matchmaking is operational.

What does Fortnite matchmaking error 2 mean?

Error 2 has two different forms. A content beacon message points to a service or connection failure. A message saying you do not have permission to play the content usually points to competitive-event eligibility instead of DNS or cache trouble.

What does Fortnite matchmaking error 3 mean?

Error 3 says the Battle Buses are full. Wait a few minutes, check Epic’s status page and retry. If it affects only your device while services are operational, continue through the local connection checklist.

Should I change my Fortnite matchmaking region to fix errors 1, 2 or 3?

Not as the first step. These exact errors are mainly server, connection or eligibility problems. Leave region selection on Auto during initial testing so a region change does not add another variable.

Does reinstalling Fortnite fix matchmaking errors?

A full reinstall is rarely the first useful step for errors 1, 2 or 3. Check server status, the exact Error 2 wording, a clean restart, clock and cache before considering a reinstall.

Why does Matchmaking Error 2 say I do not have permission?

You may be trying to enter a competitive event whose account, age, rank, 2FA or qualification requirements are not met. Open the lock or requirements panel for that event and check its current rules.

Related guides