Skip to content
A2PCheck

Twilio Error 30004: Message Blocked

Error 30004 means the destination is blocked from receiving the message — often an opt-out, carrier block, or a number that can't receive SMS.

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

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

Official Twilio name: 30004: Message Blocked

Why error 30004 happens

The recipient previously opted out (STOP), the device is off or out of coverage, the number is a landline or otherwise can't receive SMS, carrier/Twilio filtering blocked the content, or — for India — DND/DLT rules apply. On A2P traffic it frequently traces back to a prior opt-out or content that tripped filtering.

How to fix error 30004

  1. Check whether the recipient opted out; if so, they must text START or UNSTOP to resubscribe — you cannot force re-delivery.
  2. Send a fresh test with shorter, plainer content and confirm the device can receive SMS from other senders.
  3. Review content against Twilio's Messaging Policy in case filtering is the cause.
  4. For India delivery, confirm DLT registration is complete and the correct route is selected.
  5. Collect recent Message SIDs and contact Twilio Support if compliant traffic keeps returning 30004.

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

Frequently asked questions

Does 30004 mean the user blocked me?

Sometimes. 30004 covers several block types: a recipient opt-out (STOP), a carrier or compliance filter, or a line that can't receive SMS. If it's an opt-out, only the recipient can resubscribe with START/UNSTOP — resending won't get through.

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