Loading...
Loading...
Apex Legends is having one of those weekends. You know the one. You queue up, ready to drop, and then nothing. Infinite matchmaking. Error code 429. Or the game just sits there like it forgot what it's supposed to do.
I ran into this myself around 9pm EST on April 2. Three restarts, two server switches, and one very confused Bangalore later, I got into a match. Then it happened again an hour later.
So no, you're not crazy. The servers are borked.
Here's the weird part: the game isn't fully down. You can log in. You can stare at your legend skins. But matchmaking? That's where it falls apart.
I talked to a few folks in Discord who saw lobbies pop with only 12 players. That's not a battle royale. That's a sad skirmish.
This is the number one complaint right now. You hit start, the spinner spins, and nothing happens for five minutes.
Most likely cause: the matchmaking service is getting hammered and dropping requests. Think of it like a restaurant where the kitchen is still open but the waiter stopped taking orders.
Quick things that actually worked for me:
"Switched to London from Frankfurt and got a match in 40 seconds. But then next game same issue again. It's random."
- Reddit u/nexus_reborn
Error 429 is EA's way of saying "too many requests." It's a rate limiting error. Your game keeps pinging the server, the server gets overwhelmed, and it tells you to back off.
The "Unable to connect to EA servers" message is broader. That one usually means your login token expired or the authentication gateway is half dead.
I saw both errors cycle on the same night. One minute it's 429, next it's a hard disconnect. That points to backend instability, not your router.
Steam and EA App both have a verify integrity option. It fixed the crash on launch issue for a few people in the subreddit. Won't fix matchmaking but at least you'll get to the lobby.
Here's something nobody's talking about. Reports popped up on Downdetector for FIFA and Battlefield around the same time. Same error patterns. Same regions.
That suggests EA's shared infrastructure (probably the matchmaking or authentication layer) is taking a hit. Not the Apex servers specifically.
If I had to guess: they pushed a backend change or an anti-cheat update that didn't scale well. Respawn has done this before. Season 17 launch was messy the same way.
From what I've seen and scraped from player reports:
| Region | Severity | Notes |
|---|---|---|
| US East | High | Worst during 8-11pm EST |
| US West | Medium | Better but still failing |
| EU West | High | Frankfurt and London unstable |
| Asia (Tokyo/Singapore) | Medium | Intermittent, better off-peak |
| South America | Low | Most stable region reported |
Switch to South America if you're desperate. Ping will suck but at least you'll play.
No official statement yet. That's frustrating. Respawn usually tweets within an hour of major outages. This time? Silence.
My read: it's not a simple on/off switch. Intermittent issues are harder to diagnose than full crashes. They're probably hunting a memory leak or a throttling misconfiguration.
I'd expect a fix within 24 to 48 hours. But (and this is my opinion) if it's still broken by Monday, someone's getting paged on the weekend.
Look, I love Apex. But this is annoying. The game is technically online, but "online" doesn't matter if you can't actually play.
Your best bet right now: restart, switch to a low-population server, and keep trying. Or just take a break. Seriously. Play something else for an hour. The servers will either come back or they won't. You smashing the queue button won't speed it up.
If you're still stuck after trying everything here? Yeah, that's on EA. Not you.
Yes, but same issues. Platform doesn't matter. The matchmaking service is cross-platform. If it's broken, it's broken for everyone. I tested on PC and PS5. Identical failure patterns.
One thing console players can do: hard reset your console (hold power for 10 seconds). That clears the local cache. Helped one person I know get past the login screen. Worth a shot.
Third party sites like Downdetector and the EA help Twitter are your best bets. But honestly? The fastest check is just trying to queue. If you hit infinite matchmaking three times in a row, it's not you.
Some players also use the net.connect console command on PC to ping specific server IPs. That's overkill unless you're really curious.
