Control Ban
Enter password to access Control Ban:
Control Ban
How banning works
Just browsing the map or searching for locations never counts against anyone — even if someone looks for a long time, comes back later, or never buys at all. Only requesting faster than a real person can click or type, OR requesting an unusually large total number of times (even slowly, spread out over a day or a month), is treated as suspicious.
| Trigger | Points | What happens |
|---|---|---|
| More than 20 requests inside 1 minute | +3 | — |
| More than 60 requests inside 5 minutes | +10 | — |
| More than 150 requests inside 1 hour (slow but steady) | +5 | — |
| these three add up into one running total, then… | ||
| 3 points reached (one burst already does it) | — | 5-minute ban — only this short-term counter resets to 0 after |
| 20 points added up over the last 24 hours | — | 24-hour ban — this counter keeps running, it is never cleared by a 5-minute ban above |
| 3 separate 24-hour bans within a month | — | 30-day ban |
| 60 points added up over a month | — | Permanent ban |
| three separate, independent rules — not points, raw counts | ||
| More than 200 requests inside 24 hours, at ANY pace | — | 24-hour ban the first time; 30-day ban if it happens again within a month |
| More than 600 requests inside 30 days, at ANY pace, only if no purchase in that time | — | 30-day ban the first time; permanent ban if it ever happens again |
| More than 1,000 requests EVER (no time limit at all), only if no purchase in the last 30 days | — | Permanent ban immediately — this is the absolute ceiling, for someone pacing themselves to stay just under every rule above, indefinitely |
Repeating the same fast trick still adds up: only the short-term counter behind the 5-minute ban resets each time. The 24-hour and 30-day point totals do not — they keep growing with every burst, so someone who repeats a fast burst around 7 times in a day gets escalated to a 24-hour ban, and around 20 times in a month gets a permanent ban.
For scale: a real customer clicking through the configurator by hand can generate at most about 12 requests/minute — well under the 20/minute line above, and nowhere near 150/hour, 200/day, 600/month, or 1,000-ever either. Only a script hitting the server directly can trigger any of these. A genuine purchase instantly wipes every ban-related counter clean for that customer, and also exempts them from the 30-day and lifetime volume rules while it's recent. Clicking Unban below also gives a full clean slate, not just a lifted ban — except the lifetime-request count itself, which (by design) never resets, so someone unbanned under that rule who still hasn't purchased will simply trip it again on their next request. A ban currently blocks only new map loads/searches — it does not block finishing a purchase already in progress.
Manual ban / unban
Blocked & tracked actors
| Key | Score | Points (30d) | Activity (1m/5m/1h/24h/30d) | Ban | First seen | Last seen | Total loads (lifetime) | Last purchase | Actions |
|---|
Daily traffic & conversion
One row per day, never cleared or purged — independent of the 30-day window the ban rules use. "Conversion" is purchases ÷ unique visitors that day; "Avg loads/visitor" is total loads ÷ unique visitors that day.
| Date | Day | Unique visitors | Total loads | New | Returning | Avg loads/visitor | Purchases | Conversion | Ban incidents |
|---|