Where does this status come from?

From Twilio SendGrid's own status page API at https://status.twilio.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Twilio SendGrid's words. Their page covers more than this page shows; it is narrowed to the parts that concern Twilio SendGrid.

How can my agent or app check Twilio SendGrid status?

Fetch https://upbutler.com/status/sendgrid/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"sendgrid"}, on https://upbutler.com/mcp/public.

Is Twilio SendGrid down?

Right now

No. Twilio SendGrid is operational.

No incidents reported.

Read from status.twilio.com 3 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/sendgrid/status.agent.json

MCP: upstream_status {"service":"sendgrid"}

Email API and marketing campaigns. SendGrid reports on the Twilio status page; this page shows only the email components.

What Twilio SendGrid reports

Operational

Taken as is from Twilio SendGrid's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns Twilio SendGrid.

Open status.twilio.com

UpButler's independent probe

There is no keyless endpoint of Twilio SendGrid that says anything useful, so UpButler does not probe it. To check your own Twilio SendGrid account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Twilio SendGrid

Marketing Campaigns Template Maintenancescheduled maintenance
Starts 2026-10-10 23:00 UTC · SendGrid Marketing Campaigns
To improve the reliability of our Marketing Campaign email templates, we are performing an emergency maintenance on our infrastructure on October 10, 2026 from 16:00 to 19:00 PDT. We do not expect any customer impact. In the unlikely event of an issue, customers may briefly be unable to save Marketing Campaigns templates. This does not impact mail send. Thank you for your patience during this maintenance.

Text written by Twilio SendGrid, shown unchanged.

Twilio SendGrid components

8 operational

SendGrid Marketing CampaignsOperational
SendGrid APIOperational
SendGrid WebsiteOperational
SendGrid StatisticsOperational
SendGrid Email ActivityOperational
SendGrid PartnersOperational
SendGrid BillingOperational
SendGrid Legacy Marketing CampaignsOperational

Twilio SendGrid incidents, last 90 days

No finished incidents on record yet since 2026-10-10. UpButler keeps what Twilio SendGrid publishes for 90 days from the day it starts tracking a service.

Tell your outage from Twilio SendGrid's

Declare that your project depends on Twilio SendGrid. When one of your monitors fails while Twilio SendGrid has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - sendgrid

Ask before you retry

curl -s https://upbutler.com/status/sendgrid/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "sendgrid",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Twilio SendGrid down right now?: No. As of 2026-10-10 05:08 UTC, Twilio SendGrid is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Twilio SendGrid's own status page API at https://status.twilio.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Twilio SendGrid's words. Their page covers more than this page shows; it is narrowed to the parts that concern Twilio SendGrid.
How can my agent or app check Twilio SendGrid status?: Fetch https://upbutler.com/status/sendgrid/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"sendgrid"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Twilio SendGrid's?: Add "sendgrid" to the dependencies of your UpButler workspace. When one of your monitors fails while Twilio SendGrid has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in email

UpButler is not affiliated with Twilio SendGrid. Status and incident text belong to Twilio SendGrid and are read from their public status source; the probe result is UpButler's own measurement.