Error code · 30034
Twilio Error 30034 — Message from an Unregistered Number
Error 30034 fires when Twilio blocks a message because the +1 10DLC long code sending it is not associated with an approved A2P 10DLC campaign. Until the number is part of an approved campaign, US messages will continue to be blocked.
Why this happens
US carriers require all Application-to-Person (A2P) traffic on standard 10-digit long codes (10DLC) to be associated with a registered Brand and an approved Campaign through The Campaign Registry. Any +1 number sending traffic without that association is filtered.
Three possible states behind 30034
- Brand not registered. You haven't completed Brand registration in the Twilio Console.
- Campaign not approved. Your Brand is registered but no campaign covers this number, or the campaign is still pending review or was rejected.
- Number not assigned to a campaign. The campaign exists and is approved, but the specific +1 number is not yet attached to it.
Step-by-step fix
- Verify Brand status in the Twilio Console under Trust Hub.
- Verify the campaign exists for the use case you actually send.
- Confirm the campaign status is Approved, not Pending or Rejected.
- Attach the +1 number(s) to the approved campaign.
- Wait a few minutes for downstream carriers to register the association, then resend.
If your campaign is rejected
Most 30034 errors are downstream of a rejected campaign. Run our free decoder on the rejection text to identify exactly which fields to fix, then generate a compliant packet and resubmit.
Got a rejection email? Decode it for free.
The free decoder gives you the diagnosis. The $199 Approval Packet gives you every paste-ready field, screenshot checklist, and submission step. No demos. No calls.
Related errors
- 30032 — toll-free number not verified.
- 30038 — message blocked due to phone number provisioning issue.
- 30007 — carrier filtered (often A2P-related).