Resend vs SendGrid
Compare Resend and SendGrid based on observed API performance, features, and pricing
Live performance comparison
Real-world performance data from messages sent through Knock
| Provider | Message volume | Growth | Status page updates (30d) | Status page updates (90d) |
|---|---|---|---|---|
| 10M–25M | 1st of 10 → | 4 | 19 |
| 500M+ | 2nd of 10 → | 5 | 25 |
From March 24th to June 22nd, Knock routed 10M–25M messages through Resend and 500M+ through SendGrid. Resend reported 19 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.
The chart above shows each provider's daily median response time (p50) from March 24th to June 22nd. The top-line number is an average of these daily values: Resend averaged 93ms compared to 23ms for SendGrid. Resend's highest daily p50 was 122ms; SendGrid's was 25ms. SendGrid is 70ms 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 158ms compared to 77ms for SendGrid. The highest daily p90 was 221ms for Resend and 86ms for SendGrid. SendGrid handles these slower requests 81ms 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 408ms at p99 while SendGrid reached 346ms. The highest daily p99 was 1807ms for Resend and 2501ms 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.
| Provider | Avg. daily error rate | Highest daily rate | Peak error date | Zero-error days | Days above 0.01% |
|---|---|---|---|---|---|
| 0.00% | 0.12% | Apr 3 | 83 | 4 |
| 0.00% | 0.04% | Mar 24 | 89 | 2 |
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.12% for Resend and 0.04% 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 Jun 17, 2026 — Resolved Jun 17, 2026
Status: Resolved We have resolved the underlying issue and service has been resumed. Affected components Single Email (Operational) Email Events (Operational) SMTP (Operational) Broadcast Emails (Operational) Batch Emails (Operational) Webhooks (Operational) Website (Operational) Automations (Operational) Dashboard (Operational) General API (Operational)
Started Jun 15, 2026 — Resolved Jun 15, 2026
Status: Resolved We have resolved the underlying issue and service has been resumed. Affected components General API (Operational)
Started Jun 3, 2026 — Resolved Jun 3, 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)
Started May 26, 2026 — Resolved May 26, 2026
Status: Resolved We have resolved the underlying issue and service has been resumed. Affected components Single Email (Operational) Dashboard (Operational) SMTP (Operational) Broadcast Emails (Operational) General API (Operational) Webhooks (Operational) Website (Operational) Email Events (Operational) Batch Emails (Operational)
Started May 20, 2026 — Resolved May 20, 2026
Status: Complete We've completed our Email Events maintenance, and they are now showing the up-to-date status. Affected components Email Events (Operational)
Recent SendGrid incidents
Recent status page incidents for SendGrid
Started Jun 14, 2026 — Resolved Jun 14, 2026
Jun 14, 14:00 PDT Resolved - Twilio-Sendgrid mail delivery was degraded for approximately 16 minutes between 3:18 PM and 3:34 PM Pacific Time on 06/14/2026. During this period of time customers may have experienced delays affecting a subset of users. User experience was degraded with delayed mail delivery during this window, though the scope was limited to affected users rather than a system-wide outage. The issue has now been resolved.
Started Jun 14, 2026 — Resolved Jun 14, 2026
Jun 14, 12:23 PDT Resolved - Our engineers have monitored the fix and confirmed the issue with high latency and 5xx errors has been resolved. All services are now operating normally at this time. Jun 14, 11:11 PDT Monitoring - Our engineers have implemented a fix and are monitoring system performance. We will continue to observe the platform for the next hour to ensure full stability, and will mark this incident as resolved if no further issues are seen. We will provide another update in 1 h
Started Jun 11, 2026 — Resolved Jun 11, 2026
Jun 11, 10:05 PDT Resolved - Twilio-Sengrid mail delivery was degraded for approximately 9 minutes between 9:18 AM and 9:27AM Pacific Time on 06/11/2026. During this period of time customers may have experienced delays affecting a subset of users. User experience was degraded with delayed mail delivery during this window, though the scope was limited to affected users rather than system-wide outage. The issue has now been resolved.
Started Jun 10, 2026 — Resolved Jun 10, 2026
Jun 10, 01:49 PDT Resolved - Our engineers have monitored the fix and confirmed the issue with email deferrals has been resolved. All services are now operating normally at this time. Jun 9, 22:51 PDT Monitoring - Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available. Jun 9, 22:07 PDT Investigating - Starting around 9:25 AM GMT+8 on June 10, 2026, our engineers began investig
Started May 29, 2026 — Resolved May 29, 2026
May 29, 07:30 PDT Resolved - Customers have experienced elevated latency occurring in US East region from 6:30 AM to 8:58 AM Pacific time. Our engineers have investigated and resolved the issue. All impacted services are operating normally.
Pros and cons
Resend
SendGrid
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
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
- Newer and less battle-tested compared to incumbents like Mailgun or SendGrid
- Fewer enterprise features than established providers
- Limited marketing email capabilities
Cons
- Extended email activity history requires a paid add-on
- Pricing can become complex at higher volumes
- Support response times vary by plan tier
Frequently asked questions
What is the difference between Resend and SendGrid?
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.
Which is cheaper, Resend or SendGrid?
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.
Which is faster, Resend or SendGrid?
Based on real-world data from Knock, Resend has a median API response time (p50) of 93ms compared to 23ms for SendGrid.
Which is more reliable, Resend or SendGrid?
From March 24th to June 22nd, 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.
Which is more popular, Resend or SendGrid?
On the Knock platform, Resend handled 10M–25M messages from March 24th to June 22nd compared to 500M+ for SendGrid. Resend volume has remained stable, while SendGrid volume has remained stable.
Can I use both Resend and SendGrid together?
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.
What are the main pros and cons of Resend vs SendGrid?
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.
Use either provider with Knock
Knock enables you to integrate Resend, SendGrid, or any combination of email providers into a single notification workflow. Manage templates, orchestrate cross-channel delivery, and switch providers without changing your code.