KEY TAKEAWAYS
- Live and dead are definitive; error is temporary and never charged.
- Error share reflects provider conditions, not the card list.
- Aggregated from 278 checks over the last 90 days.
What does a real card-checking workload actually look like? This page aggregates outcomes from 278 checks run through the platform over the last 90 days.
Overall distribution
- Live: 24.5%
- Dead: 64.4%
- Error: 11.2% — not charged and retryable
Error share is a property of the moment, not the card list: provider congestion and timeouts move it up or down. Classified checks (100% of total) always resolve to live or dead.
Per gateway
| Gateway | Checks | Live | Dead | Error |
|---|---|---|---|---|
| Fast Checker | 84 | 26.2% | 72.6% | 1.2% |
| Pre-Auth Gateway 2 | 61 | 27.9% | 60.7% | 11.5% |
| Gate3 Charged | 42 | 28.6% | 21.4% | 50% |
| Pre-Auth Gateway | 91 | 18.7% | 79.1% | 2.2% |
Different gateways see different card pools, so percentages are not directly comparable between them — a gateway used mostly for one card type will look different. Compare gateways on classification quality and latency instead. See choosing a checker gateway.
What the numbers mean
A high live share means the card pool and the gateway are well matched; a high dead share usually means the list has already been worked through elsewhere. Error share is the figure to watch operationally: it is the only outcome that costs time without producing an answer, so a rising error rate on an otherwise stable list points at provider health rather than at the cards themselves. Because classified outcomes are always final and never need a re-run, the live and dead columns are the only ones worth exporting; error rows are the ones to retry later, ideally after the gateway has recovered.
Methodology
Outcomes are recorded per check and aggregated over the last 90 days; gateways with fewer than 10 checks are excluded. No customer data is used or published.