Geographic firewall blocks in @doublegram_captcha_bot are tracked separately from captcha timeouts and failures. The /stats report includes a firewall section for the last 30 days in your Telegram group.
Firewall section fields
- Total blocks — Users stopped by geo rules when opening the Mini App
- Top 5 countries — Country codes with flag emojis and block counts (e.g. 🇺🇸 US: 42)
Each block is logged when a user hits the firewall at Mini App open — before reCAPTCHA runs.
How to interpret spikes
| Pattern | Likely cause | Action |
|---|---|---|
| One country dominates | Raid from that region | Add to blacklist or tighten whitelist |
| Blocks rising, captcha flat | Firewall catching traffic early | Working as intended during geo attacks |
| Expected country in top blocks | VPN or wrong mode | Review whitelist/blacklist mode |
| Zero blocks | No geo rules or open policy | Normal if firewall unused |
Tune rules after reading stats
- Run
/statsweekly during active growth. - Note top blocked countries.
- Open
/firewall— add or remove countries or switch modes. - Enable Notifications in
/settingsfor real-time owner alerts on each block.
VPN effect: A member in Italy on a US VPN appears as US to Cloudflare — stats show the VPN country, not physical location.
Firewall blocks vs captcha failures
- Firewall block — Removed at Mini App open, never saw captcha
- Captcha failure — Counted in failed verifications (expired, failed reCAPTCHA, kicked)
Quick reference
- Source:
/statsfirewall section - Window: 30 days
- Shows: total + top 5 countries
- Tune:
/firewall
Related: use /debug when something is not working — see Troubleshoot @doublegram_captcha_bot with /debug.