SendGrid reported "Degraded performance" on its status page at 2026-11-14 05:54 UTC. SendGrid reports degraded performance on the Mailsend Comms API component. SendGrid is investigating the issue.

SendGrid lists these components: Mailsend: Comms API.

When did the incident start and end?

It started at 2026-11-14 05:54 UTC. This page shows the end time when SendGrid marks it resolved.

How do I get alerts for SendGrid?

Subscribe to the SendGrid live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of SendGrid. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

SendGridIncident ·

Degraded performance

DegradedOfficial update

SendGrid reports degraded performance on the Mailsend Comms API component. SendGrid is investigating the issue.

State

Components degraded

Started

Ongoing for

59 min

Worst impact

Degraded

Timeline

1 update

05:5406:0906:2306:3806:53

DegradedUpdate postedTimes in UTC

Components degraded

59 min 100%

Updates

Times in UTC

As posted by SendGrid

Components degraded

Affected components

Mailsend: Comms API

SendGrid in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

8 h 26 min

This incident

88% shorter than the median

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

33 days

median 8 h 26 min

90 days agoToday

Other SendGrid incidents

All incidents

SendGrid·Degraded performance

SendGrid reported degraded performance on Mailsend: Comms API, API v3, SMTP, and API v2. SendGrid reports that this incident is resolved. The incident lasted 66 minutes.

Resolved

SendGrid·Degraded performance

SendGrid reported degraded performance on Mailsend: Comms API, API v3, SMTP, and API v2. SendGrid reports that the incident is resolved. The incident lasted 3 minutes.

Resolved

SendGrid·Email Delivery Delays to Microsoft Inboxes

SendGrid reported delayed email delivery to Microsoft inboxes. The problem affected API v3, SMTP, and API v2. SendGrid resolved the issue on 14 November 2026. The incident lasted about 34 hours.

Resolved

SendGrid·Email Template Editor Issues

SendGrid Marketing Campaigns had a problem with the email template editor. HTML entities changed to spaces, links changed, and some template content did not render after save or preview. SendGrid reports the incident resolved. It lasted 106 minutes.

Resolved

SendGrid·Delayed Email Validation History

SendGrid reported delayed Email Validation history and statistics in the SendGrid UI. The Logs and TWILIO EMAIL - Logs components were degraded. SendGrid resolved the incident on 4 November 2026 after 168 minutes.

Resolved

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.live/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.live/feed.xml?providers=sendgrid

Slack

/feed subscribe https://outages.live/feed.xml?providers=sendgrid

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane