Geo-targeted Gmail pools becoming unreliable?

Hello! How are you guys dealing with Gmail pools lately?

From what I’ve seen, a lot of accounts seem extremely unstable now. Even with careful handling, proper warmup, and low activity, many of them get flagged or suspended pretty quickly.

Is this happening to everyone recently or are there specific setups/methods that work better?

I’m especially curious about:

• geo-targeted accounts
• aged accounts
• account longevity
• suspension rates
• recovery stability

Would like to hear some real experiences from people working with larger pools.

Lately, Gmail pools seem far less stable than before, especially when using fresh accounts or heavy automation. From what I have tested, older accounts connected to stable residential IPs and warmed up slowly tend to last much longer. Keeping login locations consistent and avoiding large bursts of activity also helps reduce suspensions, although account recovery has become much harder compared to previous years.

Google rolled out a stricter abuse-detection model around Q1 2026 — the change is that "low activity" itself now reads as suspicious for accounts created in obvious farming patterns (sequential creation, same proxy subnet, same browser fingerprint cluster). Aged Gmails (5+ years) still hold, fresh-creates are getting hit at like 60% in 14-day window. What's working: stop creating pools, instead buy individually aged Gmails from sellers who used real device farms (more expensive but actually survive), or pivot to Outlook/ProtonMail for non-Google-critical workflows.