SendGrid favicon
SendGrid Status sendgrid.com

Is SendGrid down?

Sendgrid.com is currently experiencing an incident

An incident has been reported for SendGrid.

The other half

Is it SendGrid, or is it you?

This page answers half the question. It tells you about SendGrid. It cannot tell you whether your own site is experiencing an incident, and that is the part your users notice. UptimeRobot checks your websites, APIs and servers, and tells you when one of them does.

50 monitors for your own websites. No card.

Current status

Incident

Incident reported 2d 21h 56m ago


Last check

Checked every 5 minutes


Last 24 hours

100%

Checks on provider website have reported 0 incidents, 0m down

Response time

N/A

Average

N/A

Minimum

N/A

Maximum

The response-time chart above shows SendGrid's status over time, based on our automated checks. Each point on the chart represents the result of a check run every 5 minutes.

Last 7 days

100%

0 incidents, 0m down

Last 30 days

100%

0 incidents, 0m down


Last 365 days

41.197%

19 incidents, 3mo, 21d, 57m, 43s down

Latest incidents

Root cause
Duration

SendGrid: SMS Delivery Delays from a Subset of Twilio Short Codes to T-Mobile United States
2h 23m

SendGrid: Customers Cannot Load Marketplace Plugins From 1 Console
2h 3m

SendGrid: Conversation Intelligence V3 Results Are Not Currently Available
2h 17m

SendGrid: Voice Call Audio Quality Degradation between Twilio and Multiple Networks in United Kingdom
4h 28m

SendGrid: SMS Delivery Delays from Twilio to Telenor Pakistan
—

SendGrid: SMS Delivery Delays from Twilio to MTN/Libertis Congo
7h 57m

SendGrid: SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand
—

SendGrid: Silent Network Authentication (SNA) Missing Redirects in Philippines
16h 7m

SendGrid: SMS Delivery Failures from a Subset of Twilio Long Codes to Multiple Networks in Canada
4h 13m

SendGrid: Inbound MMS Errors
1h 34m

View 2026 SendGrid outage archive →

How our status checker works?

We continuously monitor SendGrid from our own infrastructure to give you an objective view of its status. Every every 5 minutes, we send a request to sendgrid.com from our primary location in the US and verify that the site responds correctly and within a normal time frame.

If the first check fails, we immediately repeat it from a second location to avoid false positives. When that second attempt also fails, we trigger a third confirmation check from a random global location. Only if all three checks confirm a problem, we mark SendGrid as having an issue or a major outage.

Frequently asked questions

An incident has been reported for SendGrid. See Latest incidents below for details.

An incident has been reported for SendGrid, so the problem may not be on your side.

Try opening sendgrid.com from another browser, device, or network (e.g., mobile hotspot). You can also disable your VPN, clear DNS cache, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed SendGrid outage.

We monitor sendgrid.com from our own infrastructure. When a check fails, we repeat the test from two other randomly chosen global locations to eliminate false positives. If these checks fail too, we mark SendGrid as down.

A SendGrid outage means our checks detected that sendgrid.com was not responding correctly after multiple checks from different global locations. This doesn't always mean every user is affected. Some outages are regional, some affect only certain features, and some appear as slow loading instead of a full failure.

Not exactly. UptimeRobot monitors sendgrid.com from the outside, so we can detect when something is wrong and show high-level symptoms such as connection timeouts, HTTP errors, or failed responses from specific regions.

However, we don't have visibility into internal systems, so we can't identify the exact root cause (like a failed deployment, database issue, or infrastructure problem).

What we can show you:

  • When the issue started and when it was resolved
  • How long the outage lasted
  • Which regions were affected
  • The type of error observed (for example, timeouts or HTTP status codes like 500 or 404)

For detailed root cause information and official updates, we recommend checking SendGrid's official status page.

Yes, UptimeRobot lets you set up your own monitors for sendgrid.com so you get alerted the moment something goes wrong, and before your users notice. Our free plan includes 50 monitors with 5-minute check intervals. You'll also get details that this public status page doesn't show, such as response headers, response body, region-level results, and a full activity log.

Create a free UptimeRobot account and set up a monitor for sendgrid.com. You'll receive alerts via email, SMS, Slack, webhooks, and other integrations as soon as we detect an issue, and again when it's resolved. Because we monitor independently from SendGrid's own infrastructure, you may be notified even before their official status page acknowledges the issue.

Alternatively, you can check whether SendGrid offers notifications on its official status page.

Over the last 5 years, the average resolved outage for SendGrid lasted 9h 43m. That average is the mean difference between created_at and resolved_at across 93 resolved incidents we track for this provider.

Over the last 5 years, SendGrid appears on our outage timeline 100 times. Comparable communication tools averaged 18.9 incidents in the same period, so SendGrid has more incidents than the average communication tool.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.