TL;DR
What to know first
- Apex Ranked detected 137 active console ban-tracker entries: 101 on Xbox and 36 on PlayStation.
- The affected console entries carried 3,906,847 last-known RP before disappearing or being marked by the detector.
- 90 active console entries were last seen inside the top 750 ladder positions.
- Xbox accounts make up the majority of the current wave, with 2,917,016 last-known RP across 101 active flags.
- PlayStation has 36 active entries, including 2 high-confidence permaban signals and 34 off-ladder flagged entries.
- The top apparent removals were still checked around 2026-06-06 03:05 UTC and still showed current ladder position -1.
Apex Legends ban wave
Live Snapshot: Console Ban Tracker Totals
The Apex Ranked ban tracker shows an apparent console-focused ladder cleanup during Season 29 Split 1. The strongest spike landed from June 3 through June 5, with June 5 alone accounting for 83 active console entries in the current table.
This is an Apex Ranked tracker snapshot, not an official EA or Respawn enforcement report. The numbers below describe active console entries in the tracker as of 2026-06-06 03:07 UTC.
The safest wording is "apparent ban wave" because most console entries are off-ladder flags, not direct official ban confirmations. The exception is the PlayStation permaban tier, where Apex Ranked detected 2 accounts with ban_seconds above the one-year threshold used by the detector.
| Platform | Signal | Players | Last-known RP | Top-750 |
|---|---|---|---|---|
| PS4 | Permaban signal | 2 | 15,384 | 0 |
| PS4 | Flagged off-ladder | 34 | 974,447 | 19 |
| X1 | Flagged off-ladder | 101 | 2,917,016 | 71 |
Apex Legends ban wave
Highest Ranked Console Players Currently Flagged
The highest-impact rows are the players that were last seen closest to the top of the console ladder. Apex Ranked re-checked the leading flagged accounts around 2026-06-06 03:05 UTC; those rows still showed current_ladder_pos = -1 while retaining their last-known RP.
| Player | Platform | Last ladder | Last RP | Detected UTC | Last checked UTC |
|---|---|---|---|---|---|
| Owqlez | X1 | #5 | 82,754 | 2026-06-03 19:30 | 2026-06-06 03:05 |
| only zass2 | X1 | #11 | 69,241 | 2026-06-05 10:30 | 2026-06-06 03:05 |
| OnixOCEE | X1 | #13 | 66,059 | 2026-06-04 05:30 | 2026-06-06 03:05 |
| seijom4ru | X1 | #22 | 56,814 | 2026-06-05 18:30 | 2026-06-06 03:05 |
| AkumaRenshiro | PS4 | #36 | 58,215 | 2026-06-04 02:00 | 2026-06-06 03:05 |
| WhyPeridG | X1 | #38 | 49,078 | 2026-06-05 18:30 | 2026-06-06 03:05 |
| CIA GlOWIES | X1 | #51 | 45,095 | 2026-06-04 03:00 | 2026-06-06 03:05 |
| rMukki | X1 | #51 | 44,649 | 2026-06-05 18:30 | 2026-06-06 03:05 |
| iZerxlon | PS4 | #53 | 52,796 | 2026-06-05 18:30 | 2026-06-06 03:05 |
| PeIlicule | X1 | #54 | 46,229 | 2026-06-05 20:30 | 2026-06-06 03:05 |
| TheTinoks | X1 | #62 | 42,603 | 2026-06-03 23:00 | 2026-06-06 03:05 |
| Axle Crutch | X1 | #69 | 41,409 | 2026-06-04 05:00 | 2026-06-06 03:05 |
This table is deduped for readability. The headline totals still count tracked account entries, because some visible names can map to more than one tracked UID.
Apex Legends ban wave
When the Console Wave Hit
The current active console rows show the wave accelerating after June 2, then peaking on June 5. This is not a full historical ban count for every player ever affected; it is the current active table after auto-clears.
| Date UTC | Xbox players | PS4 players | Last-known RP total |
|---|---|---|---|
| 2026-05-23 | 1 | 0 | 18,902 |
| 2026-05-24 | 1 | 2 | 40,289 |
| 2026-06-02 | 2 | 0 | 50,244 |
| 2026-06-03 | 5 | 7 | 464,361 |
| 2026-06-04 | 22 | 14 | 1,211,209 |
| 2026-06-05 | 70 | 13 | 2,121,842 |
Apex Legends ban wave
How Apex Ranked Flags These Entries
Apex Ranked uses two ban-tracker signals. The highest-confidence signal is a permaban field where ban_seconds is greater than 31,536,000 seconds. That threshold represents more than one year and is treated as a direct permaban-style signal.
The second signal is a flagged off-ladder entry. It looks for a high-RP player with current rank_ladder_pos <= 0, current split ladder history, and a later API refresh after that ladder sample. That combination catches players who had ladder presence and then disappeared after being checked again.
Important: ban_reason = 2 is not used by itself. The detector intentionally ignores that field alone because normal ranked accounts can return the same value.
Flagged entries are not permanent accusations. They clear automatically if the player returns to the ladder. That is why this article uses careful language: apparent wave, ban-tracker entries, flagged, and last-known RP.
Apex Legends ban wave
Official Confirmation and Historical Context
Apex Ranked did not find an official EA, Respawn, PlayApex, or anti-cheat statement confirming a June 2026 console ban wave at publication time. That is why this report treats the June data as an apparent tracker event rather than an official enforcement announcement.
There is still useful context. Respawn published a March 2026 anti-cheat update saying input-manipulating hardware such as Strikepacks, Cronus, XIM, and similar devices undermines competitive integrity, especially across console and controller ecosystems. The update also said confirmed cheating with those devices would receive permanent bans.
Past high-rank Apex enforcement has also affected visible ranked ladders. In 2021, PC Gamer reported that Respawn permanently banned more than 700 ranked-cheating accounts from Gold through Predator, with more than 180 among Diamond and Predator. The June 2026 console tracker data should be read in that broader context: large enforcement actions can visibly reshape high-rank ladder slots, but this article does not claim every flagged row is officially confirmed by EA.
Apex Legends ban wave
What This Means for the Console Leaderboard
The console ladder impact is concentrated near the top. Ninety active entries were last seen inside the top 750, which means the apparent wave is not just a low-rank cleanup or a few inactive accounts falling out of tracking. It includes players who were occupying Predator-range ladder slots before the current checks showed them off-ladder.
Xbox appears to be carrying most of the current impact. The active Xbox flags account for 101 entries and 2,917,016 last-known RP, compared with 36 PlayStation entries and 989,831 last-known RP. That does not prove Xbox had more enforcement overall; it only describes what the Apex Ranked tracker currently sees for active console flags in this split.
The practical leaderboard effect is that cutoff, ladder rank, and top-750 visibility can shift quickly after a wave like this. If an account was holding a high ladder position and then disappears, everyone below that slot can move up without earning the RP that would normally be needed to pass that player.
The clean takeaway: the tracker shows a real console ladder disruption, but the exact reason for each off-ladder account should be treated carefully unless the row has a direct permaban signal.
More on Apex Ranked
Related ranked resources
FAQ
Common questions
Was there an Apex Legends console ban wave?
Apex Ranked detected an apparent console-focused wave of ban-tracker entries during Season 29 Split 1, with 137 active Xbox and PlayStation entries as of 2026-06-06 03:07 UTC.
How much RP is tied to these console flags?
The active console ban-tracker entries had 3,906,847 last-known RP. This is a last-known RP total from tracked entries, not an official EA removal total.
Which platform was hit harder?
Xbox had the larger current impact, with 101 active flagged entries and 2,917,016 last-known RP. PlayStation had 36 active entries and 989,831 last-known RP.
Are all flagged players officially banned?
No. Apex Ranked distinguishes permaban signals from off-ladder flags. Flagged rows can clear if the player returns to the ladder.
Why can the tracker count differ from the visible-name table?
The headline totals count tracked account entries. The article table is deduped by visible name and platform so repeated display names do not clutter the top-player list.