Sunsetting Inbound West Coast Servers
Incident
Report for SendGrid
Resolved
We are spinning down the old West Coast datacenter, as our new datacenter has been active for over a week. If you connect to smtp.sendgrid.net, you will see no issues, as you began connecting to the new datacenter last week.
However, if you have your integration configured to connect to specific SendGrid IPs, you will soon begin experiencing connection failures. If this happens, please update your connection to connect to smtp.sendgrid.net.
This will impact inbound SMTP connections, inbound Parse configurations that point to an IP instead of mx.sendgrid.net.
If you have an IP hard-coded for firewall purposes, we strongly recommend that you do not use a defined IP, as these can and will change without notice. You should instead have your Firewall configured to allow outbound-initiated connections only, on the SMTP Port that you're sending on: https://sendgrid.com/docs/Classroom/Basics/smtp_ports.html
However, if you have your integration configured to connect to specific SendGrid IPs, you will soon begin experiencing connection failures. If this happens, please update your connection to connect to smtp.sendgrid.net.
This will impact inbound SMTP connections, inbound Parse configurations that point to an IP instead of mx.sendgrid.net.
If you have an IP hard-coded for firewall purposes, we strongly recommend that you do not use a defined IP, as these can and will change without notice. You should instead have your Firewall configured to allow outbound-initiated connections only, on the SMTP Port that you're sending on: https://sendgrid.com/docs/Classroom/Basics/smtp_ports.html