How to Detect a Bad Number Pool Before You Scale
2026-08-28 · SMS-GO Research Team · 6 min read
Written by the team that operates SMS-GO. Figures reflect first-hand operation and an August 2026 audit of 16 providers\u2019 published price data. Pricing moves, so treat specific numbers as a snapshot.
The worst time to discover a provider’s numbers are bad is after you have run a hundred accounts through them. A bad pool is detectable with a small, careful test before you scale. Here is the protocol.
Test with a small sample first
Buy a handful of numbers for your actual platform — not a different one. Run them through real verification. What you learn from ten numbers tells you what a thousand will do.
Measure delivery rate
Count how many of the sample actually receive the code within the window. Below roughly 80% on a platform you care about is a warning. Below 60% is a pool you should not scale on.
Measure latency
How long between requesting the number and the code arriving? Seconds to a couple of minutes is normal. If codes routinely take five minutes or more, the hardware is overloaded and failures will climb at volume.
Check for reuse
A recycled number shows up as "this number is already in use" or gets flagged after signup. If you see that in the sample, the pool is turning over numbers that platforms have already seen.
Watch ban behavior over days
Some failures are delayed. Accounts that verify fine can get restricted days later if the number was recycled. Keep the test accounts alive and watch them for a week before scaling.
The go/no-go checklist
Scale only if the sample clears these.
- Delivery at or above ~80% on your platform.
- Code latency in the seconds-to-couple-of-minutes range.
- No "number already in use" or delayed flags.
- Test accounts still healthy after a week.
- A refund window that covers failures.
Questions, answered
How do I test a number pool before scaling?+
Buy a small sample for your actual platform, run real verifications, and measure delivery rate, latency, reuse, and delayed bans.
What delivery rate is acceptable?+
At or above about 80% for a platform you care about. Below 60% is a pool to avoid at scale.
Why watch the accounts for a week?+
Recycled numbers often fail with a delay. An account can verify fine and get restricted days later.
What protects me if the pool turns out bad?+
A refund window, plus the small-sample test before you commit volume.
Keep reading
Need a number now?
Rent a real US number up to 30 days. If no SMS arrives within 20 minutes, the charge refunds itself.
Open account