Ban Wave Tracker
IGG does not announce ban waves. Here we publish the waves we measured ourselves in the account pools of our scanning servers, once each wave has ended.
Calm — last wave 4 days ago
No wave is still recovering. This page only shows waves that have ended.
Ban history per server
Each square is one day (Turkey time). The color shows the highest impact on that server that day.
- No wave
- Light< 5%
- Moderate5–20%
- Heavy≥ 20%
- Impact not measured
Tap or hover over a colored square for details.
Wave history
Newest first. Reports hitting several servers within the same half hour count as one wave; tap a row for the per-server breakdown.
September 2026 · 12 waves · heaviest 53%
Light 3.9%1 of 4 serversrecovered in ~6 min (estimated)
- Multi Node Server 1impact 3.9%recovery ~6 min (estimated)
Impact not measured1 of 4 serversrecovery not measured
- Multi Node Server 3impact not measuredrecovery not measured
Impact not measured1 of 4 serversrecovery not measured
- Multi Node Server 1impact not measuredrecovery not measured
Heavy 28%4 of 4 serversrecovery not measured
- Multi Node Server 1impact 8.6%recovery not measured
- Multi Node Server 2impact 7.0%recovery ~17 min (estimated)
- Multi Node Server 3impact 9.3%recovery not measured
- Multi Node Server 4impact 28%recovery ~1 d 2 h (estimated)
Heavy 27%3 of 4 serversrecovery not measured
- Multi Node Server 2impact 27%recovery ~12 min (estimated)
- Multi Node Server 3impact 16%recovery not measured
- Multi Node Server 4impact 0.8%recovery ~6 min (estimated)
Heavy 51%4 of 4 serversrecovery not measured
- Multi Node Server 1impact 50%recovery ~3 d 5 h (estimated)
- Multi Node Server 2impact 42%recovery ~3 d 5 h (estimated)
- Multi Node Server 3impact 51%recovery not measured
- Multi Node Server 4impact 50%recovery ~3 d 5 h (estimated)
Impact not measured4 of 4 serversrecovery not measured
- Multi Node Server 1impact not measuredrecovery not measured
- Multi Node Server 2impact not measuredrecovery not measured
- Multi Node Server 3impact not measuredrecovery not measured
- Multi Node Server 4impact not measuredrecovery not measured
Light 4.7%2 of 4 serversrecovered in ~6 min (estimated)
- Multi Node Server 1impact 2.4%recovery ~6 min (estimated)
- Multi Node Server 4impact 4.7%recovery ~6 min (estimated)
Light 1.6%2 of 4 serversrecovered in ~8 min (estimated)
- Multi Node Server 1impact 0.8%recovery ~6 min (estimated)
- Multi Node Server 2impact 1.6%recovery ~8 min (estimated)
Light 3.1%2 of 4 serversrecovered in ~6 min (estimated)
- Multi Node Server 2impact 3.1%recovery ~6 min (estimated)
- Multi Node Server 3impact 0.8%recovery ~6 min (estimated)
Impact not measured1 of 4 serversrecovery not measured
- Multi Node Server 4impact not measuredrecovery not measured
Heavy 53%2 of 4 serversrecovery not measured
- Multi Node Server 1impact 53%recovery ~6 d 20 h (estimated)
- Multi Node Server 4impact 53%recovery not measured
August 2026 · 4 waves · heaviest 100% (capped)
Light 0.8%1 of 4 serversrecovered in ~5 min (estimated)
- Multi Node Server 3impact 0.8%recovery ~5 min (estimated)
Heavy 100% (capped)2 of 4 serversrecovered in ~19 d 2 h (estimated)
- Multi Node Server 1impact 100% (capped)recovery ~19 d 2 h (estimated)
- Multi Node Server 4impact 100% (capped)recovery ~19 d 2 h (estimated)
Impact not measured2 of 4 serversrecovery not measured
- Multi Node Server 1impact not measuredrecovery not measured
- Multi Node Server 4impact not measuredrecovery not measured
Impact not measured2 of 4 serversrecovery not measured
- Multi Node Server 1impact not measuredrecovery not measured
- Multi Node Server 4impact not measuredrecovery not measured
Ban waves and LordsRally
What is an IGG ban wave?
From time to time IGG closes, in bulk, accounts it considers to break the game rules. Waves are not announced, so nobody can know in advance when the next one will come.
It affects every scanning bot
Every bot that scans the game with accounts is hit: the area a closed account was scanning goes dark, scanning slows down and some zones can be skipped. What sets bots apart is how quickly the loss is made up.
The LordsRally difference: a spare account pool
We keep a spare account pool behind every scanning server. When a wave ends, spare accounts are brought in; as the pool recovers, slow scanning and skipped zones decrease. The times above are measured values or, where marked, estimates from log records. When needed, compensation time is added to your license.
How we measure
- Impact: the share of the accounts in the server's pool right before the wave that were banned.
- Recovery time: from the start of the wave until the server's account pool is back to 95% of its pre-wave level.
- Median recovery time: the middle value of the measured server-wave recovery times when sorted (with an even count, halfway between the two middle values); each server's own time is shown in the wave list.
- Not measured: the pre-wave pool size could not be read reliably, recovery could not be measured within 14 days, or (for waves from before permanent logging) it could not be derived from log records, so it is left blank instead of guessed.
- Estimated: recovery times of waves from before permanent logging started were derived from log records.
- Capped: when the reported ban count exceeds the pool, impact is shown as 100%.
- Times are Turkey time (UTC+3).
- Privacy: only percentages and durations are shown; account counts, group and kingdom details are never shared.