400 Error on Plan Downgrades and Cancellations for Accounts with Dedicated IPs

What to do

• Check whether your product depends on Twilio. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 24m it lasted.

  Anything that failed between 2026-08-10 16:21 UTC and 2026-08-10 17:45 UTC may need a replay.

• Subscribe to Twilio's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Twilio 3

1. identifiedAug 10, 2026, 4:21 PM UTC

   Our engineers have identified the issue (identified at 9:58 AM PDT) and are working toward a fix. Customers attempting to cancel or downgrade a SendGrid plan that has a dedicated IP are currently receiving a 400 error. If you need to downgrade or cancel, the current workaround is to reach out to Support to request an IP removal. We will provide another update in 1 hour or as soon as more information becomes available. Mail sending is not impacted, and any downgrades or cancellations currently in progress remain unaffected.

   provider

2. monitoringAug 10, 2026, 5:04 PM UTC

   Our engineers have implemented a fix and are monitoring system performance. Customers with a dedicated IP should now be able to successfully cancel or downgrade their plan without encountering a 400 error. We will provide another update in 1 hour or as soon as more information becomes available.

   provider

3. resolvedAug 10, 2026, 5:45 PM UTC

   Our engineers have monitored the fix and confirmed the issue with plan downgrades and cancellations for accounts with dedicated IPs has been resolved. All services are now operating normally at this time.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.