# OPS-124 — Unregistered and P2P-classified traffic has a hard per-number ceiling

> Traffic classified as P2P or unregistered is limited to roughly fifteen messages or segments per number per minute.

- **Rule ID:** OPS-124
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `per-number per-minute send rate`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** External record we cannot query — reported as a warning to verify
- **Fix type:** Wait on an external system or a required interval
- **Required by:** AT&T
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-124/

## Why this rule exists

The ceiling is low enough that any real campaign hits it immediately, which is the point: it is what makes registration the only viable path. Senders meet it while testing before their campaign is approved and conclude the platform is slow, then build a sending schedule around a limit that would have gone away.

## How to fix it

Do not size a programme against unregistered throughput. Wait for the campaign to be approved and provisioned before measuring what the number can do. Done when the rate you planned against is the registered one.

## Check this yourself

**Were the numbers you benchmarked throughput on attached to an approved campaign at the time?**

1. Check when the benchmark was taken against when the campaign was provisioned.
2. Unregistered and P2P-classified traffic is capped at roughly fifteen messages or segments per number per minute — low enough that any real campaign hits it immediately.
3. Re-measure after provisioning, and plan against that number.

*What wrong looks like:* A team tests before approval, concludes the platform is slow, and builds a sending schedule around a limit that would have gone away.

## Notes

A carrier-applied rate we cannot observe. What the user has to check is whether the numbers they benchmarked on were attached to an approved campaign at the time — benchmarks taken before provisioning are the usual source of a wrong plan.