August 30, 2026

On 2026-08-30 the tracker detected a ban wave: 10 bans over 1h 55m, peaking at 10 bans/hour — 11.0× the 7-day baseline.

10Bans detected

10/hPeak rate

11.0×vs baseline

—RP removed · top 750

Full day on the ban list Atom feed

Aug 30 wave · 10 bans

Ended

Detected16:41Hourly bans passed 3× the 7-day normal of 0.9/h
Peak10 bans in the busiest hour, 11.0× normal
Ended18:37Back under 1.5× normal after 1h 55m

Show these 10 bansTimes in UTC

Wave window (UTC)

16:41 – 18:371h 55m · 10 bans · peak 10/h · 11.0× baseline

Rank mix at time of ban

Predator (ladder 1–750): 0
Master (16k+ RP): 10
Other / unknown: 0
10 permanent · 0 temporary

Platform mix

PC10

Region mix (inferred)

Unknown: 10

Derived from each player's match schedule — see the note below. Unknown means the classifier wasn't confident enough to say.

Pred cutoff impact

25,764+1,237
21,009+985
17,394+233

Accounts banned in this wave · 10

Full day on the ban list

Player	RP at ban	Position	Time (UTC)
Homura	24,259	#851	17:27
Homura	24,259	#851	17:30
YYfps-y-	21,653	#1,068	17:28

These are Apex Ban Tracker's independent observations of the top-750 ranked ladders, not an official EA/Respawn list. A wave opens when the hourly detection rate exceeds 3× the rolling 7-day baseline. At-ban RP and ladder position are snapshots from the moment of detection; reversals, when they happen, are tracked publicly on the unban list. Region is inferred (no EA endpoint reports a region): a label is shown only when a player's match schedule clears a validated confidence threshold, or when their recurring squad corroborates it — everyone else counts as Unknown.