Compare Resend against SendGrid API performance

Compare real-time performance, reliability, and uptime benchmarks for Resend and SendGrid, powered by proprietary data from billions of messages sent through Knock.

Share:

Live performance comparison

Real-world performance data from messages sent through Knock.

Aug 13, 2026 – Nov 11, 2026
Updated daily
ProviderMessage volumeGrowthStatus page updates (30d)Status page updates (90d)
Resend
Resend
10M–25M
1st of 10 →22
SendGrid
SendGrid
100M–500M
2nd of 10 →2525

From August 13th to November 11th, Knock routed 10M–25M messages through Resend and 100M–500M through SendGrid. Resend reported 2 status page updates over the last 90 days, while SendGrid reported 25.

Response time

Response time measures how long each provider takes to accept an API request from Knock, including connection overhead and any automatic retries. Lower values mean faster message hand-off.

ProviderMedian (p50)p90p95p99
Resend
Resend
70ms
102ms122ms304ms
SendGrid
SendGrid
14ms
33ms44ms99ms

The chart above shows each provider's daily median response time (p50) from August 13th to November 11th. The top-line number is an average of these daily values: Resend averaged 70ms compared to 14ms for SendGrid. Resend's highest daily p50 was 96ms; SendGrid's was 26ms. SendGrid is 56ms faster at the median, which can add up at high volumes.

The 90th percentile (p90) captures the slowest 10% of requests, revealing how each provider handles moderate stress. Averaged across all days, Resend has a p90 of 102ms compared to 33ms for SendGrid. The highest daily p90 was 146ms for Resend and 37ms for SendGrid. SendGrid handles these slower requests 69ms faster, suggesting more consistent performance across the board.

The 99th percentile (p99) represents the long tail — the slowest 1% of requests. Averaged across all days, Resend reached 304ms at p99 while SendGrid reached 99ms. The highest daily p99 was 1793ms for Resend and 138ms for SendGrid, indicating the worst-case response time during spikes or provider-side congestion. SendGrid shows a tighter tail, which may matter for time-sensitive notifications like one-time passwords or real-time alerts where even rare delays can impact user experience.

Error rate

Error rate tracks the ratio of 5xx responses and timeouts to total requests. Knock automatically retries failed requests, so transient provider errors rarely affect end-user delivery.

ProviderAvg. daily error rateHighest daily ratePeak error dateZero-error daysDays above 0.01%
Resend
Resend
0.00%
0.09%Oct 1892
SendGrid
SendGrid
0.00%
0.00%Aug 13910

Averaged across the date range, Resend shows a 0.00% daily error rate compared to 0.00% for SendGrid. The highest single-day error rate was 0.09% for Resend and 0.00% for SendGrid. Both providers show similar reliability levels, with error rates well within acceptable thresholds. Knock automatically retries failed requests to both providers, minimizing the impact of transient errors on end-user delivery.

About these metrics: Data represents messages sent through Knock during the specified period. Response time measures time from Knock to provider acceptance. Error rate includes only provider 5xx responses and timeouts.

Recent Resend incidents

Recent status page incidents for Resend

Started Oct 26, 2026 — Resolved Oct 26, 2026

Status: Resolved Email status updates are processing normally again. All delayed updates have been delivered, and no data was lost. Affected components Email Events (Operational)

Started Oct 23, 2026 — Resolved Oct 23, 2026

Status: Resolved We have resolved the underlying issue and service has been resumed. Affected components Single Email (Operational) Broadcast Emails (Operational) Batch Emails (Operational) Scheduled Emails (Operational)

Recent SendGrid incidents

Recent status page incidents for SendGrid

Ongoing since Dec 23, 2026

THIS IS A SCHEDULED EVENT Dec 22, 20:00 PST  -  Dec 23, 00:00 PST Nov 6, 10:27 PST Scheduled - Twilio is conducting a planned maintenance from 22 December 2026 at 20:00 PST until 23 December 2026 at 00:00 PST. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers.

Ongoing since Dec 17, 2026

THIS IS A SCHEDULED EVENT Dec 16, 20:00 PST  -  Dec 17, 00:00 PST Nov 6, 10:27 PST Scheduled - Twilio is conducting a planned maintenance from 16 December 2026 at 20:00 PST until 17 December 2026 at 00:00 PST. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers.

Ongoing since Dec 10, 2026

THIS IS A SCHEDULED EVENT Dec 9, 20:00 PST  -  Dec 10, 00:00 PST Nov 6, 10:26 PST Scheduled - Twilio is conducting a planned maintenance from 09 December 2026 at 20:00 PST until 10 December 2026 at 00:00 PST. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers.

Ongoing since Dec 3, 2026

THIS IS A SCHEDULED EVENT Dec 2, 20:00 PST  -  Dec 3, 00:00 PST Nov 6, 10:26 PST Scheduled - Twilio is conducting a planned maintenance from 02 December 2026 at 20:00 PST until 03 December 2026 at 00:00 PST. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers.

Ongoing since Nov 29, 2026

THIS IS A SCHEDULED EVENT Nov 29, 11:00 - 13:00 PST Oct 29, 03:34 PDT Scheduled - The Globe Telecom network in the Philippines is conducting a planned maintenance from 29 November 2026 at 11:00 PST until 29 November 2026 at 13:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Globe Telecom Philippines handsets.

Pros and cons

Compare the strengths and tradeoffs between Resend and SendGrid.

Resend

Pros

  • Beautiful documentation with attention to detail and great developer experience
  • Created and maintain React Email, the go-to framework for building email templates in React
  • Minimalist, developer-optimized platform that avoids bloat with a focused UI
  • Transparent observability with real-time visibility into sends, failures, and engagement

Cons

  • Newer and less battle-tested compared to incumbents like Mailgun or SendGrid
  • Fewer enterprise features than established providers
  • Limited marketing email capabilities

SendGrid

Pros

  • Comprehensive documentation with SDKs for most major languages
  • Rich analytics tools with programmatic API access to engagement data
  • Strong focus on deliverability with AI-powered intelligent delivery
  • Trusted by Uber, Booking.com, and Yelp for high-volume sending

Cons

  • Extended email activity history requires a paid add-on
  • Pricing can become complex at higher volumes
  • Support response times vary by plan tier

Pricing comparison

Compare Resend and SendGrid as your email volume grows.

Frequently asked questions

Resend is a modern email API built for developers, with React Email support and a focus on simplicity. SendGrid is a cloud-based email delivery platform owned by Twilio, known for high-volume transactional and marketing email. Resend is best suited for developer-first, react teams, while SendGrid is geared toward high-volume transactional + marketing.

Free tier includes 3,000 emails per month and 100 emails per day. Paid plans start at $20/month for 50,000 emails with overages at $0.90/1K on Pro, scaling down to $0.46/1K on Scale 2.5M. Free tier includes up to 100 emails per day for 60 days. Paid plans start at $19.95/month for 50,000 emails on the Essentials plan, with an Essentials 100K tier at $34.95/month. Pro plans with dedicated IPs start at $249/month for 300,000 emails. The best value depends on your sending volume. Use the pricing calculator above to compare costs at your expected volume.

Based on real-world data from Knock, Resend has a median API response time (p50) of 70ms compared to 14ms for SendGrid.

From August 13th to November 11th, Resend showed an error rate of 0.00% while SendGrid showed 0.00%. Both rates are within acceptable thresholds for production email delivery, and Knock automatically retries failed requests to minimize the impact of transient errors.

On the Knock platform, Resend handled 10M–25M messages from August 13th to November 11th compared to 100M–500M for SendGrid. Resend volume has remained stable, while SendGrid volume has remained stable.

Yes. Knock enables you to integrate multiple email providers into a single notification workflow. You can use Resend and SendGrid side by side, route traffic between them, or migrate from one to the other without changing your application code.

Resend strengths include beautiful documentation with attention to detail and great developer experience and created and maintain react email, the go-to framework for building email templates in react. SendGrid strengths include comprehensive documentation with sdks for most major languages and rich analytics tools with programmatic api access to engagement data. On the other hand, Resend drawbacks include newer and less battle-tested compared to incumbents like mailgun or sendgrid, while SendGrid drawbacks include extended email activity history requires a paid add-on.