Mailgun vs Sparkpost
Compare Mailgun and Sparkpost 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 |
| <1M | 10th of 10 ↓ | 3 | 12 |
From February 10th to May 11th, Knock routed 100M–500M messages through Mailgun and <1M through Sparkpost. Mailgun reported 7 status page updates over the last 90 days, while Sparkpost reported 12.
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 282ms for Sparkpost. Mailgun's highest daily p50 was 147ms; Sparkpost's was 336ms. Mailgun is 152ms 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 347ms for Sparkpost. The highest daily p90 was 220ms for Mailgun and 549ms for Sparkpost. Mailgun handles these slower requests 162ms 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 Sparkpost reached 558ms. The highest daily p99 was 501ms for Mailgun and 31566ms for Sparkpost, indicating the worst-case response time during spikes or provider-side congestion. Mailgun 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.16% | 3.41% | Feb 24 | 89 | 2 |
Averaged across the date range, Mailgun shows a 0.00% daily error rate compared to 0.16% for Sparkpost. The highest single-day error rate was 0.03% for Mailgun and 3.41% for Sparkpost. 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 Sparkpost incidents
Recent status page incidents for Sparkpost
Started May 11, 2026 — Resolved May 11, 2026
May 11, 16:02 EDT Resolved - This incident has been resolved.May 11, 15:46 EDT Monitoring - A fix has been implemented and we are monitoring the results.May 11, 14:55 EDT Identified - We are experiencing an elevated level of errors and latency on the Suppression List API for some SparkPost customers. Please retry any 5xx error. Note: This issue does not impact SparkPost customers hosted in the EU.
Started May 9, 2026 — Resolved May 9, 2026
May 9, 18:17 EDT Resolved - This incident has been resolved.May 9, 18:05 EDT Monitoring - A fix has been implemented and we are monitoring the results.May 9, 17:50 EDT Identified - The issue has been identified and a fix is being implemented.May 9, 17:39 EDT Investigating - We are looking into why some messages are seeing delayed delivery.
Started May 8, 2026 — Resolved May 8, 2026
May 8, 07:31 EDT Resolved - This incident has been resolved.May 7, 06:49 EDT Monitoring - A fix has been implemented and we are monitoring the results.May 7, 05:31 EDT Investigating - We are currently investigating this issue.
Started Apr 5, 2026 — Resolved Apr 5, 2026
Apr 5, 15:01 EDT Resolved - Delivery rates to Apple domains have returned to normal with no further elevated delays or bounces. We will perform any necessary post-incident cleanup of suppression lists to ensure no recipients were incorrectly suppressed during the outage. NOTE: As of Monday April 5th at 9PM EDT the cleanup has been completed. All recipient addresses to Apple or Apple Private Relay domains that were suppressed during Apple's incident window were removed.Apr 5, 14:27 EDT Monito
Started Mar 16, 2026 — Resolved Mar 16, 2026
Mar 16, 19:00 EDT Completed - The scheduled maintenance has been completed.Mar 16, 16:45 EDT Update - Scheduled maintenance is still in progress, the maintenance window has been extend by one hour to allow the maintenance to finish. During the full duration of this maintenance all emails will continued to be accepted. This maintenance only impacts our EU sending infrastructure.Mar 16, 15:00 EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Pros and cons
Mailgun
Sparkpost
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
- Delivers nearly 40% of all commercial email worldwide
- Subaccount support for isolated sending streams under one billing account
- On-premise mail sending solution available for very high volume workloads
- Great analytics tools with predictive health scores for email deliverability
Cons
- Requires familiarity with email protocols and API integrations
- Pricing tiers can be confusing
- Email template features are basic without the Mailjet editor
Cons
- Documentation can be hard to navigate with less beginner-friendly getting started content
- Higher price point than basic providers
- Now part of Bird (formerly MessageBird), which may affect product direction
Frequently asked questions
What is the difference between Mailgun and Sparkpost?
Mailgun is a developer-focused email API platform owned by Sinch, known for flexible sending and receiving capabilities. SparkPost is a data-driven email delivery platform with advanced analytics and predictive tools for high-volume senders. Mailgun is best suited for developer-focused sending + receiving, while Sparkpost is geared toward data-driven, high-volume.
Which is cheaper, Mailgun or Sparkpost?
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 500 emails per month with community support. Paid plans start at $20/month for 50,000 emails with premium deliverability features. 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 Sparkpost?
Based on real-world data from Knock, Mailgun has a median API response time (p50) of 130ms compared to 282ms for Sparkpost.
Which is more reliable, Mailgun or Sparkpost?
From February 10th to May 11th, Mailgun showed an error rate of 0.00% while Sparkpost showed 0.16%. 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 Sparkpost?
On the Knock platform, Mailgun handled 100M–500M messages from February 10th to May 11th compared to <1M for Sparkpost. Mailgun volume has remained stable, while Sparkpost is seeing declining volume.
Can I use both Mailgun and Sparkpost together?
Yes. Knock enables you to integrate multiple email providers into a single notification workflow. You can use Mailgun and Sparkpost 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 Sparkpost?
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. Sparkpost strengths include delivers nearly 40% of all commercial email worldwide and subaccount support for isolated sending streams under one billing account. On the other hand, Mailgun drawbacks include requires familiarity with email protocols and api integrations, while Sparkpost drawbacks include documentation can be hard to navigate with less beginner-friendly getting started content.
Use either provider with Knock
Knock enables you to integrate Mailgun, Sparkpost, or any combination of email providers into a single notification workflow. Manage templates, orchestrate cross-channel delivery, and switch providers without changing your code.