Mailgun vs Resend
Compare Mailgun and Resend 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) |
|---|---|---|---|---|
| 100M–500M | 5th of 10 → | 3 | 7 |
| 10M–25M | 1st of 10 → | 7 | 26 |
From February 10th to May 11th, Knock routed 100M–500M messages through Mailgun and 10M–25M through Resend. Mailgun reported 7 status page updates over the last 90 days, while Resend reported 26.
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 February 10th to May 11th. The top-line number is an average of these daily values: Mailgun averaged 130ms compared to 81ms for Resend. Mailgun's highest daily p50 was 147ms; Resend's was 118ms. Resend is 49ms 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, Mailgun has a p90 of 185ms compared to 133ms for Resend. The highest daily p90 was 220ms for Mailgun and 171ms for Resend. Resend handles these slower requests 52ms 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, Mailgun reached 392ms at p99 while Resend reached 353ms. The highest daily p99 was 501ms for Mailgun and 10020ms for Resend, indicating the worst-case response time during spikes or provider-side congestion. Resend 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.03% | Mar 17 | 90 | 1 |
| 0.07% | 2.45% | Feb 15 | 82 | 5 |
Averaged across the date range, Mailgun shows a 0.00% daily error rate compared to 0.07% for Resend. The highest single-day error rate was 0.03% for Mailgun and 2.45% for Resend. Mailgun demonstrates a lower error rate, indicating slightly more consistent availability during this period. 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 Mailgun incidents
Recent status page incidents for Mailgun
Started May 7, 2026 — Resolved May 7, 2026
May 7, 11:42 PDT Resolved - This incident has been resolved.May 7, 05:40 PDT Monitoring - A fix has been implemented and we are monitoring the results.May 6, 12:46 PDT Update - We are continuing to work on a fix for this issue.May 6, 08:40 PDT Identified - Customers creating domains with Automatic Sender Security may have CNAME records with no corresponding TXT records reflecting DKIM keys. A fix for this issue is being prepared.
Started Apr 17, 2026 — Resolved Apr 17, 2026
Apr 17, 10:15 PDT Resolved - This incident has been resolved.Apr 17, 10:05 PDT Update - We are continuing to monitor for any further issues.Apr 17, 10:05 PDT Monitoring - A fix has been implemented and we are monitoring the results.Apr 17, 09:45 PDT Identified - The issue has been identified and a fix is being implemented.
Started Apr 15, 2026 — Resolved Apr 15, 2026
Apr 15, 08:34 PDT Resolved - This incident has been resolved.Apr 15, 07:02 PDT Monitoring - A fix has been implemented and we are monitoring the results.Apr 15, 06:42 PDT Identified - The issue has been identified and a fix is being implemented.Apr 15, 06:40 PDT Investigating - We are currently investigating an issue where customers making HTTPS requests to our API without Server Name Indication (SNI) enabled are being presented with an expired SSL/TLS certificate. This results in certificate va
Started Apr 7, 2026 — Resolved Apr 7, 2026
Apr 7, 10:42 PDT Resolved - This incident has been resolved. Elevated 500 errors beginning at 17:25 UTC resolved at 17:30 UTCApr 7, 10:32 PDT Monitoring - A fix has been implemented and we are monitoring the results.Apr 7, 10:30 PDT Identified - The issue has been identified and a fix is being implemented.
Started Mar 19, 2026 — Resolved Mar 19, 2026
Mar 19, 11:53 PDT Resolved - A fix has been deployed and systems are back to normal.Mar 19, 11:43 PDT Identified - Some requests may be incorrectly failing with 401 error codes in our US region.
Recent Resend incidents
Recent status page incidents for Resend
Started May 6, 2026 — Resolved May 6, 2026
Status: Resolved This incident is resolved. All failed provisioning requests have been reprocessed, and custom tracking domain creation is operating normally.
Started May 5, 2026 — Resolved May 5, 2026
Status: Complete We've successfully completed our maintenance, and the logs page is now behaving normally. Affected components Dashboard (Operational)
Started Apr 28, 2026 — Resolved Apr 28, 2026
Status: Resolved This incident is resolved. Webhook deliveries and metrics page updates have been stable since our fix was deployed. Sending and receiving were unaffected throughout. Thanks for your patience. Affected components Email Events (Operational)
Started Apr 27, 2026 — Resolved Apr 27, 2026
Status: Resolved This incident is resolved. Email events are updating in real time and have been stable since our fix was deployed. Sending and delivery were unaffected throughout. Thank you for your patience. Affected components Email Events (Operational)
Started Apr 24, 2026 — Resolved Apr 24, 2026
Status: Resolved The processing backlog is fully cleared. All systems are operational. Affected components Email Events (Operational)
Pros and cons
Mailgun
Resend
Pros
- Well-written documentation with comprehensive guides and best practices for deliverability
- Robust deliverability support with optional expert pairing to optimize sending
- Powerful inbound email processing with customizable routing rules
- Trusted by Lyft, American Express, and Wikipedia since 2010
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
- Requires familiarity with email protocols and API integrations
- Pricing tiers can be confusing
- Email template features are basic without the Mailjet editor
Cons
- Newer and less battle-tested compared to incumbents like Mailgun or SendGrid
- Fewer enterprise features than established providers
- Limited marketing email capabilities
Frequently asked questions
What is the difference between Mailgun and Resend?
Mailgun is a developer-focused email API platform owned by Sinch, known for flexible sending and receiving capabilities. Resend is a modern email API built for developers, with React Email support and a focus on simplicity. Mailgun is best suited for developer-focused sending + receiving, while Resend is geared toward developer-first, react teams.
Which is cheaper, Mailgun or Resend?
Free tier includes 100 emails per day with no expiration. Paid plans start at $15/month for 10,000 emails with overages at $1.80/1K. 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. The best value depends on your sending volume. Use the pricing calculator above to compare costs at your expected volume.
Which is faster, Mailgun or Resend?
Based on real-world data from Knock, Mailgun has a median API response time (p50) of 130ms compared to 81ms for Resend.
Which is more reliable, Mailgun or Resend?
From February 10th to May 11th, Mailgun showed an error rate of 0.00% while Resend showed 0.07%. 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, Mailgun or Resend?
On the Knock platform, Mailgun handled 100M–500M messages from February 10th to May 11th compared to 10M–25M for Resend. Mailgun volume has remained stable, while Resend volume has remained stable.
Can I use both Mailgun and Resend together?
Yes. Knock enables you to integrate multiple email providers into a single notification workflow. You can use Mailgun and Resend 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 Mailgun vs Resend?
Mailgun strengths include well-written documentation with comprehensive guides and best practices for deliverability and robust deliverability support with optional expert pairing to optimize sending. 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. On the other hand, Mailgun drawbacks include requires familiarity with email protocols and api integrations, while Resend drawbacks include newer and less battle-tested compared to incumbents like mailgun or sendgrid.
Use either provider with Knock
Knock enables you to integrate Mailgun, Resend, or any combination of email providers into a single notification workflow. Manage templates, orchestrate cross-channel delivery, and switch providers without changing your code.