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.

Calm — last wave 5 days ago

No wave is still recovering. This page only shows waves that have ended.

Last wave
2026-09-24 12:10 (UTC+3)
5 days ago
In the last 30 days
12 waves
Median recovery time (typical)
~6 min
from 15 server waves · all estimated from logs

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.

September 2026 · 12 waves · heaviest 53%
  1. Light 3.9%1 of 4 serversrecovered in ~6 min (estimated)
    • Multi Node Server 1impact 3.9%recovery ~6 min (estimated)
  2. Light ~2.3% (estimated)1 of 4 serversrecovered
    • Multi Node Server 3impact ~2.3% (estimated)recovery complete
  3. Light ~0.8% (estimated)1 of 4 serversrecovered
    • Multi Node Server 1impact ~0.8% (estimated)recovery complete
  4. 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)
  5. 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)
  6. 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)
  7. 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
  8. 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)
  9. 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)
  10. 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)
  11. Light ~2.3% (estimated)1 of 4 serversrecovered
    • Multi Node Server 4impact ~2.3% (estimated)recovery complete
  12. 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.