A SendGrid suspension almost always traces to one of three things: a spam complaint rate over roughly 0.1%, a bounce rate over 5%, or a policy breach such as cold outreach on a plan that bans it. The notice names a category but not the campaign. Before you reply to anything, pull your last 7 days of stats and work out which of the three you actually hit, because the right response is different for each.
Step one: read what the notice actually says
SendGrid uses a few standard phrasings, and they map to different outcomes.
| Notice wording | What it means | Realistic outcome |
|---|---|---|
| "Under review" / "temporarily paused" | Automated trigger, human has not looked yet | Often resolves in 24-72 hrs |
| "Violation of our Terms" | A human reviewed and decided | Appeal rarely works |
| "Suspicious activity" | Login or payment anomaly, not sending | Usually fixable |
| "Sending patterns inconsistent with..." | List quality, complaints or bounces | Fixable if you can show the cause |
The distinction that matters: a review hold is a pause, a terms violation is a decision. People waste days appealing the second as if it were the first.
Step two: find the actual cause
Pull these four numbers for the 7 days before the suspension:
| Metric | Danger threshold | What it points to |
|---|---|---|
| Complaint rate | over 0.10% | almost certainly the cause |
| Bounce rate | over 5% | list quality, bought or stale |
| Unsubscribe rate | over 0.5% | targeting or frequency problem |
| Volume change | 3x+ jump | triggered an automated review |
Complaint rate is the usual culprit and the one receiving networks care about most. Gmail's own threshold is 0.3%, but SendGrid acts earlier because your behaviour affects every other customer on the same shared IP pool. That is the part people miss: on shared infrastructure you are not judged on your own terms, you are judged on the risk you pose to everyone else on the IP.
If all four look normal, it is a policy issue, not a metrics issue. Check whether you sent cold outreach, affiliate offers, or anything in a restricted category on a plan that does not allow it.
What the thresholds actually are
Knowing the numbers tells you how much room you had and how far you have to come back.
| Signal | Where the line sits | Source |
|---|---|---|
| Gmail spam complaints | 0.3% hard limit, 0.1% target | Google sender guidelines |
| SendGrid internal review | triggers below Gmail's line | shared pool protection |
| Hard bounce rate | 5% is the usual trigger | list provenance signal |
| Authentication | SPF, DKIM and DMARC all required | Gmail and Yahoo, since 2024 |
Google publishes its bulk sender requirements openly, and the 0.3% complaint threshold is the number every receiving network effectively works to. SendGrid acts earlier than 0.3% because your complaints land on IPs shared with their other customers, so their tolerance is necessarily tighter than Gmail's.
That gap is the single most useful thing to understand about shared infrastructure. You are not judged against the receiving network's limit. You are judged against the risk you pose to everyone else on your IP, and that line is set by the provider, not published, and can move.
What the suspension does to your domain
The suspension pauses your sending. It does not undo the reputation damage that caused it, and that damage is attached to your domain, not to SendGrid.
Gmail and Microsoft score sending domains independently of which provider carries the mail. So a complaint rate that triggered a SendGrid suspension has already been recorded against your domain at every major receiver, and it follows you to your next provider.
Check this before assuming a clean start:
- Open Google Postmaster Tools for your sending domain.
- Look at Domain Reputation and IP Reputation separately.
- If domain reputation is Low or Bad, changing provider will not fix delivery on its own.
If you have never set Postmaster Tools up, do it now. It is free, takes a DNS TXT record, and it is the only direct view you get of how Gmail rates you. Our Google Postmaster Tools guide covers the setup and how to read the graphs.
Step three: decide whether to appeal
Appeal when you can answer all three of these concretely:
- Which segment caused it. "Our 2023 webinar list" beats "some old contacts".
- What you did about it. Removed, suppressed, and how many addresses.
- What stops a repeat. A hygiene process with a schedule, not an intention.
Do not bother appealing if the list was bought or scraped, if this is a second suspension, or if your use case is one the plan bans outright. In those cases the appeal costs you a week and the answer is already no.
Keep the appeal short and factual. One message, the three answers above, no argument about fairness. Multiple tickets slow it down.
Step four: get sending again
You need a path that does not depend on the appeal, because most sending recoveries take longer than the business can wait.
If the cause was list quality, fix it before you move anywhere. Every provider suspends for the same behaviour, so migrating a bad list just moves the problem and burns a second reputation. Run the list through proper cleaning first, suppress everything that hard bounced, and drop anyone who has not engaged in 12 months.
If the cause was policy, meaning your sending is legitimate but not allowed on shared infrastructure, the fix is different. Cold outreach, affiliate marketing and several other categories are banned on shared pools not because they are illegal but because they raise complaint rates for everyone else on the IP. On dedicated IPs that objection disappears, because the only reputation at risk is your own.
Either way, expect to warm up again. New infrastructure starts cold regardless of your history elsewhere. Four to eight weeks to full volume, ramping roughly 30% every two days per IP. There is no shortcut, and rushing it is how people end up suspended twice.
The 30-day recovery plan
Assume the appeal fails and work this regardless. If the appeal succeeds you are ahead.
Days 1-3: contain and measure. Export everything from SendGrid while you still have access: suppression lists, bounce logs, campaign reports. Identify the segment that caused the spike from the bounce log sorted by recipient domain. Set up Google Postmaster Tools if it is not already running.
Days 4-7: clean. Remove every hard bounce permanently. Remove anyone with no open or click in 12 months. On a typical list this takes 20 to 30% of the addresses out, and those are the addresses that were generating your complaints and bounces. See email list cleaning for the process.
Days 8-14: rebuild infrastructure.
Set up the new sending path on a subdomain, not your root domain, so future problems stay contained. Publish SPF, DKIM and DMARC, start DMARC at p=none and read the reports for two weeks before enforcing. Confirm the PTR record matches your HELO hostname.
Days 15-45: warm up. Start at a few hundred a day per IP to your most engaged segment only. Ramp roughly 30% every two days. Watch deferrals, not opens: a rising 4xx rate means you are moving too fast.
Ongoing: monitor weekly. Complaint rate per campaign, bounce rate per campaign, Postmaster Tools domain reputation. Fifteen minutes a week prevents the next suspension.
What a suspension costs, realistically
Worth being concrete, because it changes how you weigh infrastructure decisions.
| Cost | Typical scale |
|---|---|
| Sending down | 1-6 weeks |
| Revenue from paused campaigns | your normal email revenue, gone |
| Re-warm to full volume | 4-8 weeks after that |
| Engineering and admin time | 20-40 hours |
| Domain reputation recovery | months, if it dropped |
The pattern people miss is that the two clocks run in sequence, not in parallel. A one-week suspension followed by a six-week warm-up is seven weeks before you are back at full volume.
What not to do
- Do not open a replacement account. SendGrid links by payment method, domain and sending pattern. It gets closed, and it damages any future appeal.
- Do not switch to another shared relay with the same list. Same behaviour, same outcome, two weeks later.
- Do not resume at your old volume on new infrastructure. Cold IPs sending 50,000 a day get throttled immediately.
- Do not skip the post-mortem. If you never identify the segment that caused it, you will repeat it.
The honest read on shared infrastructure
Suspension risk is the price of shared IP pools. You get cheap per-email pricing and near-instant setup, and in exchange the provider has to police you aggressively, because your complaint rate lands on their other customers. That trade is fine below roughly 50,000 emails a month. Above that, the suspension risk and the per-email cost both start working against you. There is a full cost comparison in what 100,000 emails a month costs, and SendGrid alternatives covers the like-for-like options.
How BulkEmailSetup helps
We build dedicated SMTP infrastructure you own: your own server, your own IPs, full SPF/DKIM/DMARC/PTR configuration, MTA tuning, bounce handling and a warm-up plan. Because the IPs are yours alone, there is no shared pool to protect and no policy team deciding whether your legitimate use case is too risky for other customers.
Basic starts at $549 one-time, covering 1 SMTP server, 3 dedicated IPs, 25,000 emails/day and unlimited contacts. Higher tiers scale to 15 IPs and 200,000 emails/day. See pricing, or read SendGrid vs a dedicated SMTP server for the direct comparison.
Frequently asked questions
Why did SendGrid suspend my account?
The three common causes are a spam complaint rate above roughly 0.1%, a bounce rate above 5% signalling a bought or stale list, and a policy breach such as sending cold outreach or affiliate offers on a plan that does not permit them. The suspension email names a category but rarely the specific campaign, so check your last 7 days of stats before replying.
Can I get a suspended SendGrid account back?
Sometimes, if the cause was a one-off spike you can explain and fix. Appeals succeed most often when you can show the specific list segment that caused it, that it has been removed, and what process change prevents a repeat. Appeals almost never succeed for bought lists, repeat suspensions, or content categories the plan bans outright.
How long does a SendGrid suspension last?
A review hold typically resolves in 24 to 72 hours. A confirmed policy suspension is usually permanent for that account. There is no fixed clock, and opening multiple support tickets does not speed it up. Plan as if your sending is down for at least a week.
Can I just open a new SendGrid account?
No. SendGrid links accounts by payment method, domain, and sending patterns, and a replacement account created after a suspension is normally closed quickly. It also puts your sending domain on record twice, which makes any future appeal harder. Move to different infrastructure instead.
What should I move to after a SendGrid suspension?
If the cause was list quality, fix that first, because any provider will suspend you for the same behaviour. If the cause was policy, meaning your legitimate use case is not allowed on shared infrastructure, a dedicated SMTP server with your own IPs removes the policy conflict entirely, since you are not sharing reputation with anyone.
Will a SendGrid suspension damage my domain reputation?
The suspension itself does not, but whatever caused it already has. Gmail and Microsoft score your sending domain independently of which provider carries the mail, so a complaint rate above 0.3% at Gmail follows you to your next provider. Check Google Postmaster Tools for your domain reputation before assuming a clean start elsewhere.
How long before I can send at full volume again?
Plan for 4 to 8 weeks. New infrastructure starts with cold IPs regardless of your sending history elsewhere, so you ramp roughly 30% every two days per IP. Attempting your previous daily volume immediately produces deferrals at every major receiver and can burn the new IPs within a week.
