Skip to content
A2PCheck

Twilio Error 30034: Message from an Unregistered Number (A2P 10DLC)

Error 30034 is the classic "my texts stopped sending after A2P 10DLC went live" failure: a US long-code number sending without an approved campaign behind it.

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 30034 means

Twilio 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.

Official Twilio name: 30034: US A2P 10DLC - Message from an Unregistered Number A2P 10DLC-specific

Why error 30034 happens

The sending number's brand or campaign registration is incomplete or still failing, the number was never added to the Messaging Service Sender Pool that holds the approved campaign, or a Sole Proprietor campaign has more than the single 10DLC number it is allowed. Any of these leaves the number "unregistered" from the carrier's point of view.

How to fix error 30034

  1. Complete A2P 10DLC brand and campaign registration and confirm both show as approved before sending.
  2. Add the sending number to the Sender Pool of the Messaging Service that holds the approved campaign.
  3. Verify the number's registration/campaign association in Trust Hub, not just that the campaign exists.
  4. For a Sole Proprietor campaign, keep only one 10DLC number assigned — extra numbers trigger 30034.
  5. If you must send before registration finishes, route through a verified toll-free number or short code instead.

Related error codes

Twilio error 30035: US A2P 10DLC - Message from a Number Still Being ConfiguredA2P 10DLC & toll-free registrationTwilio error 30024: Numeric Sender ID Not Provisioned on CarrierA2P 10DLC & toll-free registrationTwilio error 30032: Toll-Free Number Has Not Been VerifiedA2P 10DLC & toll-free registration

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 30034 documentation

Frequently asked questions

Does 30034 mean my campaign was rejected?

Not necessarily. 30034 fires whenever the sending number isn't tied to an approved campaign — that includes registration still pending, a number missing from the Sender Pool, or a campaign that failed vetting. Check the campaign status in Trust Hub to see which case you're in.

How long after registering can I send without 30034?

Once the campaign is approved and the number is in the correct Messaging Service Sender Pool, sending should work almost immediately. If the number was just added or moved, allow provisioning to finish — a number still being configured returns error 30035 instead.

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