Skip to content
A2PCheck

Twilio Error 30022: A2P 10DLC Rate Limits Exceeded

Error 30022 is a throughput failure: you sent faster than your registered A2P 10DLC campaign's per-second limit allows, so the carrier rejected the overflow.

Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.

What Twilio error 30022 means

A downstream carrier rejected your US A2P 10DLC message because your traffic exceeded the rate (throughput) allowed for your registered campaign. It's a messages-per-second problem, not a daily-total problem.

Official Twilio name: 30022: US A2P 10DLC - Rate Limits Exceeded A2P 10DLC-specific

Why error 30022 happens

You sent faster than the carrier permits for your campaign type, combined traffic across several numbers exceeded the campaign's throughput, or you sent many messages to the same recipient in a short window. Campaign throughput (MPS) is tied to your brand's trust score and campaign type.

How to fix error 30022

  1. Reduce your sending rate to stay within your campaign's throughput (MPS) limit.
  2. Spread message bursts over time instead of firing them simultaneously.
  3. Avoid rapid repeat sends to the same recipient.
  4. If your use case genuinely needs higher MPS, review your campaign type and throughput tier and register accordingly.

Related error codes

Official reference

For the authoritative definition and any changes to this code, see the Twilioerror catalog. A2PCheck is an independent pre-scan layer for the campaign packet you submit — it can't change carrier behavior.

Twilio error 30022 documentation

Frequently asked questions

What's the difference between error 30022 and 30023?

30022 is a per-second throughput (rate) limit — you sent too fast. 30023 is a daily message cap — you hit the total number of messages your brand can send to the carrier that day. Fix 30022 by slowing down; fix 30023 by waiting for the daily reset or raising your trust score.

Free — no signup required

Catch the campaign issue behind this error before you resend

Many of these errors trace back to an unregistered, mis-scoped, or non-compliant A2P 10DLC campaign. Paste your campaign details for a free readiness scan — no signup.

Independent pre-submission check
No Twilio or TCR submission
Use campaign metadata, not customer PII

Use representative templates and public URLs only. Do not paste real customer phone numbers, customer records, API keys, or internal/signed URLs.

New here? Try a realistic example

Load a complete, carrier-friendly campaign to scan in one click — then tweak it for your own.

01

Campaign Info

Basic details about your messaging campaign.

0 characters — Too short — describe who opts in, what you send, and how often.

02

Sample Messages

Provide at least 2 example messages you'll send.

STOP foundHELP foundchecked across your keywords & messages
03

Opt-In / Message Flow

How users consent to receive your messages.

Consent evidence readiness

Describe where and how subscribers consent — name the opt-in location and the consent language they agree to.

  • Name the opt-in location (web form, checkout, keyword, QR code, paper form, etc.).
  • Spell out the consent language — what the subscriber explicitly agrees to.
  • State the message frequency (e.g. recurring, varies, msgs/month).
  • Include a "Message and data rates may apply" disclosure.
  • Link a privacy policy describing how you handle subscriber data.
  • Clarify that consent isn't a condition of purchase, where that applies.
  • Capture and retain opt-in evidence (timestamp, source URL, exact consent text/screenshot) for each subscriber.

Guidance only — consent requirements can vary by use case and jurisdiction.

or sign up to run a Full scan
Scan my campaign for this issueAll A2P 10DLC error codes