Skip to main content
SendGrid (Twilio) logo

Is SendGrid (Twilio) Down?

No — SendGrid (Twilio) is up

Reachable from all 18 checked regions

Average response time: 336ms

Last checked · checks run every 30 minutes

Official status page: https://status.sendgrid.com

Errors Impacting Real-Time Transcriptions, Conversation Relay, <Gather> Voice TwiML

minor identified

Our engineering team has observed an increase in error rates affecting our Real-Time Transcriptions, Conversation Relay, and <Gather> Voice TwiML products using the Deepgram model. Customers experiencing issues should use the Google model as a workaround. We will provide another update in 1 hour or as soon as more information becomes available.

Components the vendor reports as affected: SMTP Under Maintenance API v2 Under Maintenance Bulk Export Degraded Performance Voice, APAC Degraded Performance Speech Recognition (Gather Speech) US1 Degraded Performance MMS, APAC Degraded Performance SMS, Europe Degraded Performance Verify Silent Network Auth Under Maintenance Lookup Identity Match Under Maintenance Lookup Line Type Intelligence [Legacy API] Degraded Performance Lookup SIM Swap Under Maintenance Legacy Identity MatchAndAttributes Under Maintenance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw SendGrid (Twilio) fail from enough regions to rule out probe noise.

SendGrid (Twilio) uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
336ms
Avg response, 30 days

Measured from multiple regions every 30 minutes. Percentages count only checks that returned an availability answer — 49 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

38-day clean streak
Aug 14: 100.00% uptime, 880 checks
Aug 15: 100.00% uptime, 872 checks
Aug 16: 100.00% uptime, 877 checks
Aug 17: 100.00% uptime, 895 checks
Aug 18: 100.00% uptime, 936 checks
Aug 19: 100.00% uptime, 933 checks
Aug 20: 100.00% uptime, 863 checks
Aug 21: 100.00% uptime, 829 checks
Aug 22: 100.00% uptime, 861 checks
Aug 23: 100.00% uptime, 810 checks
Aug 24: 100.00% uptime, 864 checks
Aug 25: 100.00% uptime, 882 checks
Aug 26: 100.00% uptime, 863 checks
Aug 27: 100.00% uptime, 882 checks
Aug 28: 100.00% uptime, 863 checks
Aug 29: 100.00% uptime, 864 checks
Aug 30: 100.00% uptime, 863 checks
Aug 31: 100.00% uptime, 880 checks
Sep 1: 100.00% uptime, 864 checks
Sep 2: 100.00% uptime, 842 checks
Sep 3: 100.00% uptime, 713 checks
Sep 4: 100.00% uptime, 710 checks
Sep 5: 100.00% uptime, 748 checks
Sep 6: 100.00% uptime, 746 checks
Sep 7: 100.00% uptime, 763 checks
Sep 8: 100.00% uptime, 890 checks
Sep 9: 100.00% uptime, 915 checks
Sep 10: 100.00% uptime, 889 checks
Sep 11: 100.00% uptime, 873 checks
Sep 12: 100.00% uptime, 837 checks
Aug 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
350ms
DNS 2ms TCP 2ms TLS 5ms TTFB 349ms
arn
387ms
DNS 0ms TCP 1ms TLS 6ms TTFB 386ms
bom
640ms
DNS 1ms TCP 2ms TLS 4ms TTFB 639ms
cdg
355ms
DNS 0ms TCP 1ms TLS 4ms TTFB 355ms
dfw
75ms
DNS 0ms TCP 1ms TLS 4ms TTFB 74ms
ewr
110ms
DNS 0ms TCP 2ms TLS 6ms TTFB 110ms
fra
339ms
DNS 0ms TCP 1ms TLS 4ms TTFB 338ms
gru
447ms
DNS 0ms TCP 1ms TLS 5ms TTFB 447ms
iad
110ms
DNS 1ms TCP 2ms TLS 4ms TTFB 110ms
jnb
513ms
DNS 1ms TCP 0ms TLS 5ms TTFB 513ms
lax
228ms
DNS 1ms TCP 2ms TLS 5ms TTFB 228ms
lhr
313ms
DNS 0ms TCP 2ms TLS 4ms TTFB 312ms
nrt
464ms
DNS 0ms TCP 2ms TLS 5ms TTFB 464ms
ord
62ms
DNS 0ms TCP 1ms TLS 4ms TTFB 62ms
sin
696ms
DNS 0ms TCP 1ms TLS 6ms TTFB 696ms
sjc
215ms
DNS 0ms TCP 1ms TLS 7ms TTFB 214ms
syd
618ms
DNS 1ms TCP 1ms TLS 6ms TTFB 617ms
yyz
135ms
DNS 0ms TCP 10ms TLS 11ms TTFB 134ms

What SendGrid (Twilio) does

SendGrid is a cloud-based email delivery platform owned by Twilio that handles transactional and marketing emails. It provides APIs for sending email, managing contact lists, designing email templates, and tracking delivery analytics. SendGrid delivers billions of emails per month for customers ranging from startups to large enterprises.

What an outage looks like

During a SendGrid outage, transactional emails like password resets, order confirmations, and welcome emails will fail to send or be severely delayed. Marketing campaigns may not be delivered on schedule. The SendGrid dashboard may become inaccessible, preventing you from checking delivery status or managing your account.

What to do about it

Check status.sendgrid.com for current incidents. SendGrid typically queues emails during partial outages and delivers them once service is restored. If you have time-sensitive transactional emails, consider having a backup email provider configured (like Amazon SES or Postmark) that can be activated during extended outages.

Is it down for everyone, or just you?

If this page says SendGrid (Twilio) is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

SendGrid (Twilio) outage FAQ

Will my emails be lost if SendGrid goes down?
Emails submitted to SendGrid's API before the outage will be queued and delivered when service is restored. Emails that your application tried to send during the outage and received an API error for will not be queued, so your application needs to handle retries for those messages.
How does a SendGrid outage affect password reset emails?
Users requesting password resets during a SendGrid outage will not receive their reset emails. The reset tokens are typically created in your application database but the delivery fails. Users can try again once email service is restored, or you can offer alternative account recovery methods.
Does SendGrid's outage affect emails I send through SMTP?
Yes, both SendGrid's API and SMTP relay services share the same delivery infrastructure. If SendGrid's delivery pipeline is down, emails sent via SMTP will also be affected. SMTP connections may time out or be rejected during the outage.
Can I switch email providers quickly during a SendGrid outage?
If you've pre-configured a backup email provider in your application, switching can be quick. However, if you need to change DNS records (SPF, DKIM) for the new provider, full email deliverability may take hours to establish. The best approach is to set up a backup provider before you need it.

How we measure this

  • We request SendGrid (Twilio)'s public endpoint every 30 minutes from Fly.io regions across six continents — the most recent check ran from 18 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where SendGrid (Twilio) publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when SendGrid (Twilio) goes down

This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required