Skip to content
A2PCheck

A2P 10DLC & Twilio error codes — what they mean and how to fix them

Got a messaging error code after submitting or sending an A2P 10DLC campaign? Find it below for a plain-English explanation, why it fires in the 10DLC context, and the concrete fix. Many of these trace back to registration, campaign scope, or content that a pre-scan can catch first.

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

A2P 10DLC & toll-free registration

Twilio error 30034: US A2P 10DLC - Message from an Unregistered NumberTwilio blocked the message because you sent to a US number from a +1 10DLC (long-code) number that is not associated with an approved A2P 10DLC campaign. Since US carriers require registration, unregistered long-code traffic to US handsets is rejected outright.Twilio error 30035: US A2P 10DLC - Message from a Number Still Being ConfiguredThe sending number can't transmit because it is still in configuration for US A2P 10DLC — its registration with downstream ecosystem partners hasn't finished. The number typically shows a PENDING_REGISTRATION (or PENDING_DEREGISTRATION) status.Twilio error 30024: Numeric Sender ID Not Provisioned on CarrierThe destination carrier requires a pre-registered numeric sender, and the sender you used isn't provisioned on that carrier. The carrier rejects the message rather than delivering from an unrecognized sender.Twilio error 30032: Toll-Free Number Has Not Been VerifiedYou tried to send from a toll-free number to a US or Canadian mobile subscriber, but the number hasn't been verified. As of January 31, 2024, traffic from toll-free numbers in Restricted or Pending status is blocked.Twilio error 30455: Toll-Free phone number verification rejection - Disallowed: SHAFT - HateTwilio rejected your toll-free verification request because the submission indicates a forbidden SHAFT category related to hate. This is a content/use-case rejection, not a formatting or timing issue.

Carrier filtering & content blocks

Twilio error 30007: Message FilteredYour message was filtered (blocked) by Twilio or by the carrier. Registration alone doesn't exempt content from spam filtering — carriers still block traffic they read as spam, phishing, or fraud.Twilio error 30004: Message BlockedThe destination number is blocked from receiving the message. This can be a recipient-level block (they replied STOP), a carrier or Twilio compliance filter, or a line that simply can't receive SMS.Twilio error 30019: Content Size Exceeds Carrier LimitThe message failed because the size of its content exceeded the carrier's limit. The message is simply too large for the carrier to transmit as sent.

Throughput & daily caps

Twilio error 30022: US A2P 10DLC - Rate Limits ExceededA 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.Twilio error 30023: US A2P 10DLC - Daily Message Cap ReachedYou've sent the maximum allowable daily messages for your brand to the carrier. The daily limit depends on your brand's trust score and resets at midnight Pacific Time.Twilio error 30001: Queue OverflowYour outbound queue exceeded capacity. Twilio queues messages according to the sending rate of the sender or account, and messages can only sit in the queue for up to a limited window before they automatically fail.

Delivery & handset failures

Twilio error 30003: Unreachable Destination HandsetThe destination handset is unavailable on the carrier network. This usually happens when the device is powered off, has no service, cannot receive SMS, or is otherwise temporarily unreachable.Twilio error 30005: Unknown Destination HandsetThe destination number is unknown and may no longer exist. Twilio receives this status from carrier partners and returns it to you.Twilio error 30006: Landline or Unreachable CarrierThe destination number cannot receive your message. Twilio returns 30006 when the destination is a landline, or when a short code cannot reach the destination carrier.Twilio error 30008: Unknown ErrorTwilio received a generic delivery failure from a carrier or downstream provider and didn't get enough detail to classify it more specifically. The real cause is one of several common issues hiding behind an unlabeled failure.Twilio error 30410: Provider Timeout ErrorThe provider used may be experiencing disruptions that result in errors or request timeouts. It's an upstream/downstream availability problem rather than something wrong with your message.

Account, billing & fraud protection

Twilio error 30002: Account SuspendedTwilio accepted the message for queueing, but your account was suspended before it could be sent. Nothing about the individual message is wrong — the account itself is blocked.Twilio error 30450: Message Delivery BlockedTwilio blocked delivery to the destination number because SMS Pumping Protection identified the request as suspicious. The block is temporary and exists to reduce SMS pumping fraud.

Frequently asked questions

Why did my texts start failing right after A2P 10DLC launched?

The most common cause is error 30034 — sending from a +1 10DLC number that isn't tied to an approved A2P 10DLC campaign. US carriers block unregistered long-code traffic. Complete brand and campaign registration, add the number to the right Messaging Service Sender Pool, and confirm the campaign is approved.

Do these error codes mean my campaign was rejected?

Not always. Some codes (30034, 30035, 30024, 30032, 30455) are about registration or verification status; others (30007, 30004, 30019) are content or carrier filtering; and some (30022, 30023, 30001) are throughput and daily caps. Match the specific code to its category to know what to fix.

Is A2PCheck affiliated with Twilio?

No. A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier. We link to the official Twilio error catalog for each code and provide an independent pre-scan of the campaign packet you submit.

Free — no signup required

Pre-scan the campaign behind the error

A registered, compliant campaign avoids most 30xxx blocks. 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 campaignRejection reasons