Twilio SendGrid’s retirement of a group of legacy public IP addresses is still listed as in progress on its status page, ten days after the 31 August date set for permanent deprecation.
Twilio posted the notice on 19 August. Customers connecting to SendGrid’s API or SMTP service by IP address rather than by hostname were told to update their configurations. Three temporary disablement windows ran on 24, 25 and 27 August, with permanent removal scheduled for 9:00am Pacific on 31 August. The ticket moved to “in progress” on 24 August and has not been updated since.
Twilio has not said whether the addresses were withdrawn on 31 August. It has also never said which addresses are affected. The notice refers only to “legacy IP addresses” and tells customers to use smtp.sendgrid.net and api.sendgrid.com instead, or api.eu.sendgrid.com for EU regional subusers, as its documentation already instructs.
This is separate from dedicated sending IPs, which are outbound addresses assigned to customer accounts for reputation. The deprecation covers inbound connection endpoints only.
Anyone with a hard-coded SendGrid IP in an application, mail server, firewall or allowlist should replace it with the hostname. Anyone already using the hostname needs to do nothing. Whether the old addresses still answer is a question Twilio has not answered and we could not test without knowing what they are.
