Dedicated IPs

When and how to migrate from shared IPs to dedicated. Includes warmup schedule.

When you need them

Generally not until you're sending 100k+ emails/month consistently. Below that volume:

• Shared IPs benefit from collective good reputation.
• Low volume on a dedicated IP looks like a spammer (no track record).
• Dedicated IPs cost $24.95/mo each.

Reasons to switch to dedicated:

• Volume warrants reputation isolation.
• Regulated industries needing source IP attestation.
• You've been hit by another tenant's bad behavior.

AWS setup

1. SES console → Dedicated IPs → Standard (or Managed).
2. Create a pool: tx-pool.
3. Assign the new IP to the pool.
4. Create a configuration set: tx-prod.
5. Attach the pool: configuration set → Delivery → Sending pool → tx-pool.

Mailgrid setup

curl -X POST https://api.mailgrid.space/api/ips \
  -H "Authorization: Bearer $KEY" \
  -d '{
    "ipAddress": "54.240.7.123",
    "poolName":  "tx-pool",
    "configSet": "tx-prod"
  }'

Warmup schedule

A cold IP sending high volume looks like a spammer. Ramp slowly:

Tracking warmup

curl -X PUT https://api.mailgrid.space/api/ips/$IP_ID/status \
  -H "Authorization: Bearer $KEY" \
  -d '{ "status": "warming", "warmupPct": 25 }'

When warmupPct reaches 100, flip status to active.