## TL;DR

Symptom: rising deferrals, more spam-folder placement, or blocks, with unchanged content and lists. Authentication broke (DNS record changed, domain expired).

## Steps

1. Cause candidates:
1. Shared-IP neighbor damage. Confirm: check whether the sending IP's reputation signals dropped while your own engagement stayed flat.
2. Your own engagement decayed (stale list, frequency jump). Confirm: opens down and spamreports up on your campaigns.
3. Authentication broke (DNS record changed, domain expired). Confirm: re-validate domain auth.

2. Fix:
1. Rule out 2 and 3 first; they are cheaper than moving IPs.
2. If the IP is the problem and you send real volume, move to a dedicated IP. The doc recommends dedicated IPs for high volume and for control over who shares your reputation.
3. Warm the new IP gradually; do not cut all traffic over on day one. An IP idle or new gets evaluated by ISPs on volume and engagement.
4. Keep authentication, list hygiene, and engagement discipline on the new IP, or you will recreate the problem alone.

3. Verification: deferral rate falls and inbox placement recovers over the warmup period. If nothing changes, the cause was never the IP.

## When to use

You are seeing this: Shared-IP neighbor damage. Use this skill when you run into "SendGrid sudden deliverability drop on a shared IP".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.