Mailgun vs SendGrid
Compare Mailgun 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) |
|---|---|---|---|---|
| 100M–500M | 5th of 10 → | 5 | 9 |
| 500M+ | 2nd of 10 → | 5 | 25 |
From March 24th to June 22nd, Knock routed 100M–500M messages through Mailgun and 500M+ through SendGrid. Mailgun reported 9 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: Mailgun averaged 133ms compared to 23ms for SendGrid. Mailgun's highest daily p50 was 149ms; SendGrid's was 25ms. SendGrid is 110ms 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 187ms compared to 77ms for SendGrid. The highest daily p90 was 829ms for Mailgun and 86ms for SendGrid. SendGrid handles these slower requests 110ms 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 483ms at p99 while SendGrid reached 346ms. The highest daily p99 was 3152ms for Mailgun 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.00% | Mar 24 | 91 | 0 |
| 0.00% | 0.04% | Mar 24 | 89 | 2 |
Averaged across the date range, Mailgun shows a 0.00% daily error rate compared to 0.00% for SendGrid. The highest single-day error rate was 0.00% for Mailgun 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 Mailgun incidents
Recent status page incidents for Mailgun
Started Jun 18, 2026 — Resolved Jun 18, 2026
Jun 18, 03:24 PDT Resolved - This incident has been resolved. Jun 18, 03:11 PDT Monitoring - A fix has been implemented and we are monitoring the results. Jun 18, 02:53 PDT Identified - The issue has been identified and a fix is being implemented. Jun 18, 02:11 PDT Update - We are continuing to investigate this issue. Jun 18, 01:34 PDT Investigating - Customers using the events/logs APIs or viewing logs in the customer portal may see delays in some events appearing. These delays are
Started Jun 16, 2026 — Resolved Jun 16, 2026
Jun 16, 10:34 PDT Resolved - This incident has been resolved. Jun 16, 09:16 PDT Monitoring - A fix has been implemented and we are monitoring the results. Jun 16, 08:48 PDT Update - We are continuing to investigate this issue. Jun 16, 08:08 PDT Update - We are continuing to investigate this issue. Jun 16, 07:28 PDT Investigating - Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating n
Started Jun 5, 2026 — Resolved Jun 5, 2026
Jun 5, 07:15 PDT Resolved - This incident has been resolved. Jun 5, 07:04 PDT Monitoring - A fix has been implemented and we are monitoring results. Outbound processing, inbound processing, and webhook delivery continue operating normally. Jun 5, 06:26 PDT Investigating - Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.
Started Jun 4, 2026 — Resolved Jun 4, 2026
Jun 4, 14:04 PDT Resolved - This incident has been resolved. Jun 4, 13:48 PDT Monitoring - Logs are flowing normally and engineers continue to monitor. Jun 4, 12:52 PDT Update - We are continuing to investigate this issue. Outbound processing, inbound processing, and webhook delivery continue to operate normally. Jun 4, 11:42 PDT Update - We are continuing to investigate this issue. Jun 4, 11:01 PDT Investigating - Logs are currently experiencing delays of 15 minutes in Mailgun
Started May 25, 2026 — Resolved May 25, 2026
May 25, 08:55 PDT Resolved - This incident has been resolved. May 25, 08:45 PDT Monitoring - A fix has been implemented and we are monitoring the results. May 25, 08:35 PDT Update - We are continuing to work on a fix for this issue. May 25, 07:46 PDT Identified - The issue has been identified and a fix is being implemented. May 25, 07:10 PDT Update - We are continuing to investigate this issue. May 25, 06:38 PDT Investigating - We are currently investigating this issue. May 25,
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
Mailgun
SendGrid
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
- 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
- Requires familiarity with email protocols and API integrations
- Pricing tiers can be confusing
- Email template features are basic without the Mailjet editor
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 Mailgun and SendGrid?
Mailgun is a developer-focused email API platform owned by Sinch, known for flexible sending and receiving capabilities. SendGrid is a cloud-based email delivery platform owned by Twilio, known for high-volume transactional and marketing email. Mailgun is best suited for developer-focused sending + receiving, while SendGrid is geared toward high-volume transactional + marketing.
Which is cheaper, Mailgun or SendGrid?
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 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, Mailgun or SendGrid?
Based on real-world data from Knock, Mailgun has a median API response time (p50) of 133ms compared to 23ms for SendGrid.
Which is more reliable, Mailgun or SendGrid?
From March 24th to June 22nd, Mailgun 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, Mailgun or SendGrid?
On the Knock platform, Mailgun handled 100M–500M messages from March 24th to June 22nd compared to 500M+ for SendGrid. Mailgun volume has remained stable, while SendGrid volume has remained stable.
Can I use both Mailgun and SendGrid together?
Yes. Knock enables you to integrate multiple email providers into a single notification workflow. You can use Mailgun 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 Mailgun vs SendGrid?
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. 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, Mailgun drawbacks include requires familiarity with email protocols and api integrations, while SendGrid drawbacks include extended email activity history requires a paid add-on.
Use either provider with Knock
Knock enables you to integrate Mailgun, 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.