CheckUpstream measured SendGrid at 100.000% availability across 2830 independent checks (global · api). 25 incidents were recorded in the past 12 months; the most recent resolved 39 days ago after 11 hours. Status signals are polled from SendGrid's official Atlassian Statuspage status page, alongside independent probes and community reports. SendGrid publishes 1 product-level SLA uptime commitment (up to 99.95%), and service credits must be claimed within 30 days of a breach.
180 days measured availability how this is computed
100.000%
global · api · n=2830 · p95 572ms (30d)
Share of our own checks against SendGrid endpoints that returned SendGrid's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 17 incidents · 174 of 180 days with none posted · 19h 23m of declared impact
Fewer incidents in the last 30 days than 55% of 232 tracked services.
Share of each window with no impact declared by SendGrid
7d
100.000%
30d
100.000%
90d
100.000%
180d
99.551%
1y
99.779%
Downtime like this can be refundable
If you're a paying SendGrid customer, outages in these windows may count against SendGrid's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your SendGrid entitlement →Does SendGrid actually matter to you?
A SendGrid outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 17 incidents SendGrid published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long SendGrid takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Jul 24, 01:40 UTC · resolved in 10h 35m · Resolved
Jul 15, 18:11 UTC · resolved in 1d · Resolved
Jul 13, 16:13 UTC · resolved in 1h 6m · Resolved
1signal across 1 source
Synthetic probes 1
All of these are CheckUpstream's own probes. Nobody else has reported SendGrid in this window, so nothing here is corroboration.
Live SendGrid status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/sendgrid)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
SendGrid is currently Operational. CheckUpstream tracks SendGrid in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
SendGrid's last resolved incident started 39 days ago and lasted 10h 35m (degraded performance).
Looking for the live "is SendGrid down" view? See the SendGrid Live status page.
Jul 11, 18:19 UTC · resolved in 2h 20m · Resolved
May 12, 16:31 UTC · resolved in 1h 48m · Resolved
May 8, 02:04 UTC · resolved in 6h 5m · Resolved
May 6, 17:34 UTC · resolved in 5h 55m · Resolved
Apr 30, 18:50 UTC · resolved in 4d 21h · Resolved
Apr 22, 16:32 UTC · resolved in 1d 4h · Resolved
Apr 6, 15:08 UTC · resolved in 6h 52m · Resolved
Apr 6, 13:23 UTC · resolved in 1d 5h · Resolved
SendGrid's 30-day measured availability is 100.000%, from CheckUpstream's own probes against SendGrid endpoints. It is the share of checks that returned the expected response, not a figure taken from SendGrid's status page.
Sign up to CheckUpstream and add SendGrid to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll SendGrid's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.