Skip to main content

Resend vs SendGrid

Front door check counts, what each vendor’s status page recorded and SLA terms for these vendors.

30-day window ending

Front door checks

Every 15 minutes we send a request to a documented endpoint for each vendor from a single CheckUpstream location and count the answers. A reachable front door does not confirm that a customer action worked.

Front door check counts: Resend and SendGrid
Last 30 daysResendSendGrid
Front door reachableOut of checks with a clear answer
  • 2,257 of 2,257

    checks to api.resend.com

  • 2,258 of 2,258

    checks to api.sendgrid.com

Checks 15 minutes apart cannot see disruptions shorter than that. Each vendor is checked at its own endpoints, so the counts cover different things.

Resend · check scope

  • api.resend.comapi · No vendor region

    Front door reachable in 2,257 of 2,257 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    1 more check gave no clear answer and is not counted.

    First check in this window
    Latest clear answer
View Resend record

SendGrid · check scope

  • api.sendgrid.comapi · No vendor region

    Front door reachable in 2,258 of 2,258 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    First check in this window
    Latest clear answer
View SendGrid record

What each vendor’s status page says

Recorded starts in the same 30-day window, excluding maintenance. Vendors report incidents differently; fewer posts don’t prove better reliability.

Recorded incidents: Resend and SendGrid
Last 30 daysResendSendGrid
Incidents recorded

4

4

Recorded incident durationMedian

Too few dated records

4 valid durations

Too few dated records

4 valid durations

Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded, as are records posted with one time for start and resolution. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not mean an outage is ongoing.

Resend says

  • API logs are delayed

    Started
    Closed in record
    Source incident
  • Microsoft 365 Incident

    Started
    Closed in record
    Source incident
  • Delayed email status updates

    Started
    Closed in record
    Source incident

SendGrid says

  • Transactional Email Delays in AP

    Started
    Closed in record
    Source incident
  • Twilio Email Send API Message Delivery Delays to Microsoft Inboxes

    Started
    Closed in record
    Source incident
  • Email Template Editor Issues

    Started
    Closed in record
    Source incident

Check the terms for your plan

An SLA applies to specific products and plans. Credit eligibility also depends on exclusions, evidence and filing deadlines.

Resend

No public terms recorded here.

Review Resend SLA guide

SendGrid

1 public term record.

Product not specified

Review SendGrid SLA guide