Skip to content

Outage tracker / SendGrid

Is SendGrid down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of SendGrid pass from all 10 regions we check.

As of Oct 22, 2026, 11:37 PM UTC, RealUptime's checks of SendGrid passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of SendGrid did not fail from two or more distant regions in the 61 days we have checked it (since Aug 22, 2026). This does not show SendGrid works for users.

our check readinglive · checked Oct 22, 2026, 11:37 PM UTC
US-East1229 msChecks passing
US-West851 msChecks passing
Europe475 msChecks passing
Asia-Pacific1333 msChecks passing
US-Central405 msChecks passing
Canada1059 msChecks passing
UK1562 msChecks passing
Southeast Asia1558 msChecks passing
Australia2073 msChecks passing
South America1968 msChecks passing
their status pagetheir claim, not our reading

SendGrid publishes no status feed we can read, so the only reading here is our check reading on the left.

SendGrid response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 946ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 806ms2026-09-26 UTC: p95 605ms2026-09-27 UTC: p95 585ms2026-09-28 UTC: p95 591ms2026-09-29 UTC: p95 599ms2026-09-30 UTC: p95 579ms2026-10-01 UTC: p95 339ms2026-10-02 UTC: p95 238ms2026-10-03 UTC: p95 282ms2026-10-04 UTC: p95 339ms2026-10-05 UTC: p95 350ms2026-10-06 UTC: p95 348ms2026-10-07 UTC: p95 342ms2026-10-08 UTC: p95 344ms2026-10-09 UTC: p95 392ms2026-10-10 UTC: p95 338ms2026-10-11 UTC: p95 393ms2026-10-12 UTC: p95 293ms2026-10-13 UTC: p95 364ms2026-10-14 UTC: p95 370ms2026-10-15 UTC: p95 441ms2026-10-16 UTC: p95 313ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
US-West
1.6sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 786ms2026-09-24 UTC: p95 912ms2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 955ms2026-09-29 UTC: p95 888ms2026-09-30 UTC: p95 878ms2026-10-01 UTC: p95 549ms2026-10-02 UTC: p95 432ms2026-10-03 UTC: p95 444ms2026-10-04 UTC: p95 350ms2026-10-05 UTC: p95 322ms2026-10-06 UTC: p95 410ms2026-10-07 UTC: p95 363ms2026-10-08 UTC: p95 335ms2026-10-09 UTC: p95 332ms2026-10-10 UTC: p95 438ms2026-10-11 UTC: p95 530ms2026-10-12 UTC: p95 484ms2026-10-13 UTC: p95 291ms2026-10-14 UTC: p95 446ms2026-10-15 UTC: p95 524ms2026-10-16 UTC: p95 518ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
Europe
913msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 717ms2026-09-24 UTC: p95 762ms2026-09-25 UTC: p95 724ms2026-09-26 UTC: p95 628ms2026-09-27 UTC: p95 638ms2026-09-28 UTC: p95 709ms2026-09-29 UTC: p95 585ms2026-09-30 UTC: p95 633ms2026-10-01 UTC: p95 307ms2026-10-02 UTC: p95 348ms2026-10-03 UTC: p95 300ms2026-10-04 UTC: p95 309ms2026-10-05 UTC: p95 313ms2026-10-06 UTC: p95 308ms2026-10-07 UTC: p95 344ms2026-10-08 UTC: p95 384ms2026-10-09 UTC: p95 349ms2026-10-10 UTC: p95 343ms2026-10-11 UTC: p95 291ms2026-10-12 UTC: p95 286ms2026-10-13 UTC: p95 237ms2026-10-14 UTC: p95 229ms2026-10-15 UTC: p95 359ms2026-10-16 UTC: p95 199ms2026-10-17 UTC: p95 540ms2026-10-18 UTC: p95 855ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 908ms2026-10-21 UTC: p95 904ms2026-10-22 UTC: p95 913ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.8sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.3s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 2.2s2026-09-28 UTC: p95 2.1s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 857ms2026-10-02 UTC: p95 816ms2026-10-03 UTC: p95 817ms2026-10-04 UTC: p95 674ms2026-10-05 UTC: p95 715ms2026-10-06 UTC: p95 698ms2026-10-07 UTC: p95 663ms2026-10-08 UTC: p95 677ms2026-10-09 UTC: p95 738ms2026-10-10 UTC: p95 686ms2026-10-11 UTC: p95 626ms2026-10-12 UTC: p95 650ms2026-10-13 UTC: p95 713ms2026-10-14 UTC: p95 883ms2026-10-15 UTC: p95 942ms2026-10-16 UTC: p95 898ms2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
US-Central
899msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 900ms2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 729ms2026-10-02 UTC: p95 739ms2026-10-03 UTC: p95 705ms2026-10-04 UTC: p95 679ms2026-10-05 UTC: p95 621ms2026-10-06 UTC: p95 675ms2026-10-07 UTC: p95 802ms2026-10-08 UTC: p95 798ms2026-10-09 UTC: p95 679ms2026-10-10 UTC: p95 647ms2026-10-11 UTC: p95 506ms2026-10-12 UTC: p95 492ms2026-10-13 UTC: p95 548ms2026-10-14 UTC: p95 570ms2026-10-15 UTC: p95 478ms2026-10-16 UTC: p95 468ms2026-10-17 UTC: p95 847ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 983ms2026-10-21 UTC: p95 856ms2026-10-22 UTC: p95 899ms
Sep 23Oct 7Oct 22
Canada
1.6sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 930ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 966ms2026-09-26 UTC: p95 878ms2026-09-27 UTC: p95 764ms2026-09-28 UTC: p95 756ms2026-09-29 UTC: p95 746ms2026-09-30 UTC: p95 804ms2026-10-01 UTC: p95 460ms2026-10-02 UTC: p95 421ms2026-10-03 UTC: p95 411ms2026-10-04 UTC: p95 418ms2026-10-05 UTC: p95 334ms2026-10-06 UTC: p95 328ms2026-10-07 UTC: p95 404ms2026-10-08 UTC: p95 430ms2026-10-09 UTC: p95 353ms2026-10-10 UTC: p95 331ms2026-10-11 UTC: p95 345ms2026-10-12 UTC: p95 360ms2026-10-13 UTC: p95 387ms2026-10-14 UTC: p95 410ms2026-10-15 UTC: p95 427ms2026-10-16 UTC: p95 432ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
UK
1.5sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 868ms2026-09-24 UTC: p95 866ms2026-09-25 UTC: p95 747ms2026-09-26 UTC: p95 951ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 933ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 827ms2026-10-01 UTC: p95 462ms2026-10-02 UTC: p95 276ms2026-10-03 UTC: p95 295ms2026-10-04 UTC: p95 285ms2026-10-05 UTC: p95 251ms2026-10-06 UTC: p95 356ms2026-10-07 UTC: p95 340ms2026-10-08 UTC: p95 265ms2026-10-09 UTC: p95 324ms2026-10-10 UTC: p95 447ms2026-10-11 UTC: p95 410ms2026-10-12 UTC: p95 448ms2026-10-13 UTC: p95 340ms2026-10-14 UTC: p95 337ms2026-10-15 UTC: p95 227ms2026-10-16 UTC: p95 282ms2026-10-17 UTC: p95 868ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.5s
Sep 23Oct 7Oct 22
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 3.6s2026-09-24 UTC: p95 3.5s2026-09-25 UTC: p95 3.7s2026-09-26 UTC: p95 3.1s2026-09-27 UTC: p95 2.6s2026-09-28 UTC: p95 2.3s2026-09-29 UTC: p95 2.4s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 994ms2026-10-02 UTC: p95 978ms2026-10-03 UTC: p95 766ms2026-10-04 UTC: p95 811ms2026-10-05 UTC: p95 990ms2026-10-06 UTC: p95 861ms2026-10-07 UTC: p95 809ms2026-10-08 UTC: p95 696ms2026-10-09 UTC: p95 774ms2026-10-10 UTC: p95 725ms2026-10-11 UTC: p95 675ms2026-10-12 UTC: p95 728ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.5s
Sep 23Oct 7Oct 22
Australia
2.3sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.3s2026-09-25 UTC: p95 2.3s2026-09-26 UTC: p95 2.5s2026-09-27 UTC: p95 2.4s2026-09-28 UTC: p95 2.4s2026-09-29 UTC: p95 2.5s2026-09-30 UTC: p95 2.7s2026-10-01 UTC: p95 816ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 971ms2026-10-04 UTC: p95 871ms2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 873ms2026-10-07 UTC: p95 906ms2026-10-08 UTC: p95 957ms2026-10-09 UTC: p95 985ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 978ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.9s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 3.1s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.3s
Sep 23Oct 7Oct 22
South America
2.4sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.9s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 2.0s2026-09-29 UTC: p95 2.5s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 848ms2026-10-02 UTC: p95 898ms2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 933ms2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 933ms2026-10-08 UTC: p95 983ms2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.9s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.4s
Sep 23Oct 7Oct 22

Check your own site while you wait on SendGrid

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not SendGrid. It cannot diagnose SendGrid's own systems.

What we measured, function by function

SendGrid answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of SendGrid fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of SendGrid fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not SendGrid's official status.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1229msstatus code: 401checked: Oct 22, 2026, 11:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach SendGrid normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 851msstatus code: 401checked: Oct 22, 2026, 11:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach SendGrid normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 405msstatus code: 401checked: Oct 22, 2026, 11:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach SendGrid normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1059msstatus code: 401checked: Oct 22, 2026, 11:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach SendGrid normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1968msstatus code: 401checked: Oct 22, 2026, 11:33 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach SendGrid normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 475msstatus code: 401checked: Oct 22, 2026, 11:30 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach SendGrid normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 1562msstatus code: 401checked: Oct 22, 2026, 11:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach SendGrid normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1333msstatus code: 401checked: Oct 22, 2026, 11:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach SendGrid normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1558msstatus code: 401checked: Oct 22, 2026, 11:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach SendGrid normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2073msstatus code: 401checked: Oct 22, 2026, 11:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach SendGrid normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using SendGrid, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for SendGrid yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for SendGrid.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring SendGrid since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for SendGrid covering any window you pick, with our check readings and SendGrid's own claim at the time, side by side.

Full check history for SendGrid: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

SendGrid uptime by RealUptime's checksLive, from this page's own readings.
[![SendGrid uptime by RealUptime's checks](https://realuptime.io/outages/sendgrid/badge.svg?days=30)](https://realuptime.io/outages/sendgrid)
<a href="https://realuptime.io/outages/sendgrid"><img src="https://realuptime.io/outages/sendgrid/badge.svg?days=30" alt="SendGrid uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is SendGrid down?", https://realuptime.io/outages/sendgrid. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with SendGrid's stated SLA

At or above your target

Our checks of SendGrid failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from SendGrid's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

secondary
https://sendgrid.com/en-us
primaryfunctional: live API
https://api.sendgrid.com/v3/user/account

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.sendgrid.com

RealUptime is not affiliated with SendGrid; the name identifies what we checked, and nothing here speaks for SendGrid's own team. We send a single web request to SendGrid from 10 regions on our own schedule and time the response. We do not see inside SendGrid's systems, do not use an account or real transaction, and are not the same signal SendGrid's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for SendGrid is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.