LordsRally's own measurement

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.

Recovery in progress — last wave 2 days ago

Spare accounts are being brought in; scanning does not stop, it may only be slower until the pool is full again.

Last wave
2026-11-10 02:35 (UTC+3)
2 days ago
In the last 30 days
29 waves
Median recovery time (typical)
~17 min
from 79 server waves · 15 of 79 estimated

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%
  • Estimated impact

Colored squares are days with a wave; each wave's details are in the wave history below.

Multi Node Server 1
Multi Node Server 2
Multi Node Server 3
Multi Node Server 4
30 days agoToday

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.

November 2026 · 18 waves · heaviest 100% (capped)
  1. Light 4.7%2 of 4 serversrecovered in 7 min
    • Multi Node Server 2impact 3.1%recovery 6 min
    • Multi Node Server 3impact 4.7%recovery 7 min
  2. Light 1.2%1 of 4 serversrecovered in 6 min
    • Multi Node Server 1impact 1.2%recovery 6 min
  3. Moderate 11%4 of 4 serversrecovery in progress (77 h so far)
    • Multi Node Server 1impact 3.4%recovery 7 min
    • Multi Node Server 2impact 3.9%recovery 17 h 12 min
    • Multi Node Server 3impact 11%recovery 17 h 12 min
    • Multi Node Server 4impact 9.8%recovery in progress (77 h so far)
  4. Heavy 61%4 of 4 serversrecovery in progress (82 h so far)
    • Multi Node Server 1impact 61%recovery in progress (82 h so far)
    • Multi Node Server 2impact 33%recovery in progress (82 h so far)
    • Multi Node Server 3impact 52%recovery in progress (82 h so far)
    • Multi Node Server 4impact 9.4%recovery 9 min
  5. Heavy 37%4 of 4 serversrecovered in 23 h 13 min
    • Multi Node Server 1impact 30%recovery 23 h 13 min
    • Multi Node Server 2impact 37%recovery 23 h 13 min
    • Multi Node Server 3impact 36%recovery 23 h 12 min
    • Multi Node Server 4impact 4.7%recovery 6 min
  6. Light 3.3%1 of 4 serversrecovered in 6 min
    • Multi Node Server 3impact 3.3%recovery 6 min
  7. Light 2.1%1 of 4 serversrecovered in 6 min
    • Multi Node Server 2impact 2.1%recovery 6 min
  8. Light 3.4%1 of 4 serversrecovered in 6 min
    • Multi Node Server 1impact 3.4%recovery 6 min
  9. Light 3.2%2 of 4 serversrecovered in 9 min
    • Multi Node Server 1impact 1.1%recovery 6 min
    • Multi Node Server 4impact 3.2%recovery 9 min
  10. Moderate 6.3%4 of 4 serversrecovered in 2 d 5 h
    • Multi Node Server 1impact 6.3%recovery 6 h 59 min
    • Multi Node Server 2impact 4.9%recovery 12 h 6 min
    • Multi Node Server 3impact 4.8%recovery 2 d 5 h
    • Multi Node Server 4impact 0.8%recovery 6 min
  11. Light 1.6%1 of 4 serversrecovered in 6 min
    • Multi Node Server 3impact 1.6%recovery 6 min
  12. Light 1.0%1 of 4 serversrecovered in 6 min
    • Multi Node Server 2impact 1.0%recovery 6 min
  13. Light 2.3%2 of 4 serversrecovered in 27 min
    • Multi Node Server 1impact 2.0%recovery 27 min
    • Multi Node Server 4impact 2.3%recovery 6 min
  14. Heavy 91%2 of 4 serversrecovered in 7 min
    • Multi Node Server 2impact 1.0%recovery 6 min
    • Multi Node Server 3impact 91%recovery 7 min
  15. Heavy 94%2 of 4 serversrecovered in 6 min
    • Multi Node Server 1impact 1.0%recovery 6 min
    • Multi Node Server 3impact 94%recovery 6 min
  16. Heavy 100% (capped)2 of 4 serversrecovered in 43 min
    • Multi Node Server 2impact 20%recovery 38 min
    • Multi Node Server 3impact 100% (capped)recovery 43 min
  17. Moderate 10%2 of 4 serversrecovered in 10 min
    • Multi Node Server 1impact 10%recovery 5 min
    • Multi Node Server 2impact 6.3%recovery 10 min
  18. Heavy 45%3 of 4 serversrecovered in 5 d 18 h
    • Multi Node Server 1impact 45%recovery 9 min
    • Multi Node Server 2impact 2.3%recovery 5 d 18 h
    • Multi Node Server 3impact 2.3%recovery 5 min
October 2026 · 12 waves · heaviest 100% (capped)
  1. Heavy 100% (capped)3 of 4 serversrecovered
    • Multi Node Server 1impact ~16% (estimated)recovery complete
    • Multi Node Server 1impact ~24% (estimated)recovery complete
    • Multi Node Server 1impact ~23% (estimated)recovery complete
    • Multi Node Server 2impact 100% (capped)recovery 2 h 40 min
    • Multi Node Server 3impact 2.3%recovery 15 min
    • Multi Node Server 3impact ~3.1% (estimated)recovery complete
    • Multi Node Server 3impact ~6.3% (estimated)recovery complete
  2. Heavy 42%1 of 4 serversrecovered in 18 h 23 min
    • Multi Node Server 2impact 42%recovery 18 h 23 min
  3. Heavy 100% (capped)4 of 4 serversrecovered
    • Multi Node Server 1impact ~23% (estimated)recovery complete
    • Multi Node Server 1impact 22%recovery 1 h 20 min
    • Multi Node Server 2impact 100% (capped)recovery 2 h 43 min
    • Multi Node Server 3impact 17%recovery 2 h 29 min
    • Multi Node Server 4impact 8.6%recovery 1 h 48 min
  4. Heavy 41%2 of 4 serversrecovered in 1 h 42 min
    • Multi Node Server 1impact 41%recovery 1 h 42 min
    • Multi Node Server 2impact 5.5%recovery 47 min
  5. Moderate 16%4 of 4 serversrecovered in 53 min
    • Multi Node Server 1impact 12%recovery 24 min
    • Multi Node Server 2impact 16%recovery 53 min
    • Multi Node Server 3impact 3.1%recovery 19 min
    • Multi Node Server 4impact 0.8%recovery 6 min
  6. Light ~0.8% (estimated)1 of 4 serversrecovered
    • Multi Node Server 3impact ~0.8% (estimated)recovery complete
  7. Moderate 9.7%4 of 4 serversrecovered in 5 h 22 min
    • Multi Node Server 1impact 1.6%recovery 5 h 21 min
    • Multi Node Server 2impact 1.6%recovery 6 min
    • Multi Node Server 3impact 9.7%recovery 5 h 22 min
    • Multi Node Server 4impact 1.6%recovery 5 min
  8. Moderate 8.2%1 of 4 serversrecovered in 11 h 49 min
    • Multi Node Server 3impact 8.2%recovery 11 h 49 min
  9. Heavy 100%1 of 4 serversrecovered in 18 min
    • Multi Node Server 3impact 100%recovery 18 min
  10. Light 0.8%1 of 4 serversrecovered in 6 min
    • Multi Node Server 4impact 0.8%recovery 6 min
  11. Light 0.8%1 of 4 serversrecovered in 5 min
    • Multi Node Server 4impact 0.8%recovery 5 min
  12. Heavy 59%4 of 4 serversrecovered in 1 d 3 h
    • Multi Node Server 1impact 51%recovery 6 h 9 min
    • Multi Node Server 2impact 59%recovery 1 d 3 h
    • Multi Node Server 3impact 58%recovery 6 h 9 min
    • Multi Node Server 4impact 43%recovery 6 h 9 min
September 2026 · 13 waves · heaviest 53%
  1. Heavy 41%4 of 4 serversrecovered in 55 min
    • Multi Node Server 1impact 32%recovery 55 min
    • Multi Node Server 2impact 26%recovery 42 min
    • Multi Node Server 3impact 25%recovery 21 min
    • Multi Node Server 4impact 41%recovery 51 min
  2. Light 3.9%1 of 4 serversrecovered in ~6 min (estimated)
    • Multi Node Server 1impact 3.9%recovery ~6 min (estimated)
  3. Light ~2.3% (estimated)1 of 4 serversrecovered
    • Multi Node Server 3impact ~2.3% (estimated)recovery complete
  4. Light ~0.8% (estimated)1 of 4 serversrecovered
    • Multi Node Server 1impact ~0.8% (estimated)recovery complete
  5. Heavy 28%4 of 4 serversrecovered
    • Multi Node Server 1impact 8.6%recovery complete
    • Multi Node Server 2impact 7.0%recovery ~17 min (estimated)
    • Multi Node Server 3impact 9.3%recovery complete
    • Multi Node Server 4impact 28%recovery ~1 d 2 h (estimated)
  6. Heavy 27%3 of 4 serversrecovered
    • Multi Node Server 2impact 27%recovery ~12 min (estimated)
    • Multi Node Server 3impact 16%recovery complete
    • Multi Node Server 4impact 0.8%recovery ~6 min (estimated)
  7. Heavy 51%4 of 4 serversrecovered
    • 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 complete
    • Multi Node Server 4impact 50%recovery ~3 d 5 h (estimated)
  8. Heavy ~23% (estimated)4 of 4 serversrecovered
    • Multi Node Server 1impact ~23% (estimated)recovery complete
    • Multi Node Server 2impact ~17% (estimated)recovery complete
    • Multi Node Server 3impact ~19% (estimated)recovery complete
    • Multi Node Server 4impact ~20% (estimated)recovery complete
  9. 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)
  10. 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)
  11. 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)
  12. Light ~2.3% (estimated)1 of 4 serversrecovered
    • Multi Node Server 4impact ~2.3% (estimated)recovery complete
  13. Heavy 53%2 of 4 serversrecovered
    • Multi Node Server 1impact 53%recovery complete
    • Multi Node Server 4impact 53%recovery complete
August 2026 · 4 waves · heaviest 100% (capped)
  1. Light 0.8%1 of 4 serversrecovered in ~5 min (estimated)
    • Multi Node Server 3impact 0.8%recovery ~5 min (estimated)
  2. Heavy 100% (capped)2 of 4 serversrecovered
    • Multi Node Server 1impact 100% (capped)recovery complete
    • Multi Node Server 4impact 100% (capped)recovery complete
  3. Light ~1.6% (estimated)2 of 4 serversrecovered
    • Multi Node Server 1impact ~1.6% (estimated)recovery complete
    • Multi Node Server 4impact ~1.6% (estimated)recovery complete
  4. Heavy ~100% (estimated)2 of 4 serversrecovered
    • Multi Node Server 1impact ~100% (estimated)recovery complete
    • Multi Node Server 4impact ~100% (estimated)recovery complete

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. How long this takes depends on the size of the wave and on how full the spare pool is; it is not guaranteed. 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.
  • ~ Estimated impact: the pool right before the wave could not be read reliably, so impact was calculated from the server's usual pool size (dashed square on the map).
  • Recovery time: from the start of the wave until the server's account pool is back to 95% of its pre-wave level. Scanning does not stop during recovery; it may only be slower until the pool is full again.
  • Recovered (no duration): the moment of recovery was not recorded; the pool later filled up again, or the wave is more than 14 days old. Recovery time is only measured within the first 14 days of a wave.
  • Median recovery time: the middle value of the shown 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.
  • ~ Estimated time: 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.