Live

Mail Settings Maintenance

MaintenanceOfficial update

In order to increase the stability and scalability of our systems, we are performing maintenance on our infrastructure on November 4, 2026 from 14:00 until 16:00 PST. During this time customers may be temporarily unable to manage Mail Settings (Address Allow List, Bounce Purge, Event Notification, Footer, Forward Bounce, Forward Spam or Legacy Email Template) or related Tracking Settings, Event Webhook and Inbound Parse settings. Reading existing settings will function as normally. This maintenance does not impact mail send. Thank you for your patience through this maintenance.

The latest update from SendGrid.

State

Scheduled

Starts

in 3 d

2026-11-04 22:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by SendGrid

Scheduled2026-11-01 17:18 UTC

In order to increase the stability and scalability of our systems, we are performing maintenance on our infrastructure on November 4, 2026 from 14:00 until 16:00 PST. During this time customers may be temporarily unable to manage Mail Settings (Address Allow List, Bounce Purge, Event Notification, Footer, Forward Bounce, Forward Spam or Legacy Email Template) or related Tracking Settings, Event Webhook and Inbound Parse settings. Reading existing settings will function as normally. This maintenance does not impact mail send. Thank you for your patience through this maintenance.

Affected components

5
Event WebhooksParse APISendGrid APISendGrid Webhooks - Event WebhooksSendGrid Webhooks - Parse API

SendGrid in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

51

Days with an incident

37

Median duration

9 h 43 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 9 h 43 min
90 days agoToday

Other SendGrid incidents

All incidents

Follow SendGrid

Your coding agent knows when SendGrid is down, and tells you when a failure is theirs, not yours. You can also get SendGrid incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sendgrid" and tell me if SendGrid has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=sendgrid
Slack
/feed subscribe https://outages.cc/feed.xml?providers=sendgrid

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane