A2P Watch · Registration health
Your Twilio brand is SUSPENDED
What a SUSPENDED brand actually stops, how it differs from FAILED, and what to put in the support ticket — including the evidence that decides whether you get reinstated.
What suspension stops
Every campaign under the brand stops covering its numbers, so application SMS from those numbers is blocked and returns error 30034. It happens without warning and without a message to the person sending — the first signal is usually a client saying their texts aren't arriving.
Suspension is a carrier-side judgement about messaging conduct, which is what makes it different from every other broken state in a Twilio account: nothing in your configuration is wrong, so there is nothing in your configuration to correct.
Reading the status
SUSPENDED is one of seven documented brand states
Two of them stop your messages and two more are easy to mistake for something benign.
SUSPENDED vs FAILED
Both block sending. Only one has instructions.
A FAILED brand comes with errors describing what didn't match, and Twilio documents how to correct and resubmit it. Fixing the data fixes the brand.
SUSPENDED has no equivalent path. Twilio's troubleshooting guide for brand registrations covers failures and does not address suspension at all — which is why searching for this mostly turns up forum threads rather than documentation.
Treat the two as different problems. Resubmitting data that was never the issue burns attempts and time.
It's the obvious instinct and it's worth thinking through first. A new brand submitted under the same EIN and legal name presents the same business identity to the same vetting system, so it is not obvious why it would be assessed differently.
We have not found documentation from Twilio or the Campaign Registry that states whether a replacement brand is permitted, blocked, or simply ineffective after a suspension. Anyone telling you confidently either way is probably repeating a forum post. Ask support directly before spending registration fees on it.
What is clear is that the underlying complaint follows the messaging, not the record. If the consent problem is unfixed, a fresh brand sending the same traffic invites the same outcome.
The ticket
What to gather before you contact support
Suspension follows complaints about unsolicited messaging. The case you are making is that recipients agreed to hear from you, so assemble the evidence for that before you open the ticket.
01
The brand SID
Starts with BN. Include it in the first line — without it the ticket gets a request for it and loses a day.
02
How consent was collected
The actual form, checkbox or keyword flow, and a link to the live page showing it. Screenshots of a page that no longer says that are worse than nothing.
03
Where the list came from
Be able to state plainly that no numbers were purchased, scraped, or imported from a previous owner of the business.
04
What you have changed
Suppressions applied, a list segment retired, a frequency reduced. A remedy already in place is a stronger position than a promise.
If you manage several accounts
A suspension on one client's brand is invisible from every other account, and the Twilio console shows one account at a time with no cross-account status view. On an agency setup that means the only reliable way to know is to look at each account deliberately.
It is also the finding most likely to be missed by a partial check: if the credentials you scan with can't read brand registrations, a suspended brand simply doesn't appear, and the report looks clean.
Check your own account
See this across every account you manage, in about a minute
One read-only scan lists every brand, campaign and number in your Twilio account and every subaccount under it, worst first. Free, no signup, and your credentials are destroyed when the scan finishes.
Verified 9 August 2026