Amazon SES vs Mailgun
Compare Amazon SES and Mailgun 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) |
|---|---|---|---|---|
| 25M–100M | 3rd of 10 → | 0 | 0 |
| 100M–500M | 5th of 10 → | 5 | 14 |
From June 3rd to September 1st, Knock routed 25M–100M messages through Amazon SES and 100M–500M through Mailgun. Amazon SES reported 0 status page updates over the last 90 days, while Mailgun reported 14.
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.
| Provider | Median (p50) | p90 | p95 | p99 |
|---|---|---|---|---|
| 160ms | 227ms | 291ms | 408ms |
| 119ms | 170ms | 186ms | 216ms |
The chart above shows each provider's daily median response time (p50) from June 3rd to September 1st. The top-line number is an average of these daily values: Amazon SES averaged 160ms compared to 119ms for Mailgun. Amazon SES's highest daily p50 was 216ms; Mailgun's was 130ms. Mailgun is 41ms 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, Amazon SES has a p90 of 227ms compared to 170ms for Mailgun. The highest daily p90 was 312ms for Amazon SES and 197ms for Mailgun. Mailgun handles these slower requests 57ms 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, Amazon SES reached 408ms at p99 while Mailgun reached 216ms. The highest daily p99 was 491ms for Amazon SES and 432ms for Mailgun, 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.25% | Jun 28 | 88 | 3 |
| 0.00% | 0.01% | Aug 27 | 90 | 0 |
Averaged across the date range, Amazon SES shows a 0.00% daily error rate compared to 0.00% for Mailgun. The highest single-day error rate was 0.25% for Amazon SES and 0.01% for Mailgun. 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 Amazon SES incidents
Recent status page incidents for Amazon SES
No incidents reported in the last 90 days
Recent Mailgun incidents
Recent status page incidents for Mailgun
Started Aug 31, 2026 — Resolved Aug 31, 2026
Aug 31, 15:01 PDT Resolved - Event queues have caught up and events are processing normally. Aug 31, 14:28 PDT Update - The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery. We expect all delays to be resolved within the hour. Aug 31, 13:43 PDT Update - The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery. Aug 31, 13:13 PDT Update - The event processing backlog is steadily decreasing, and we’re co
Started Aug 27, 2026 — Resolved Aug 27, 2026
Aug 27, 14:16 PDT Resolved - This incident has been resolved. Aug 27, 14:00 PDT Monitoring - A fix has been implemented and we are monitoring the results. Aug 27, 13:45 PDT Identified - We have identified the issue and working on restoring service. Aug 27, 13:38 PDT Investigating - We are currently investigating an outage in our EU datacenter
Started Aug 20, 2026 — Resolved Aug 20, 2026
Aug 20, 10:31 PDT Resolved - This incident has been resolved. Aug 20, 10:09 PDT Update - GCP has put a mitigation in place, we are monitoring the results. At this time we are experiencing no impacts. All delayed webhooks and logs have been processed. Aug 20, 09:30 PDT Update - Outbound delivery is operating normally. Currently there are delays for event logs and some webhooks. Aug 20, 09:19 PDT Monitoring - Mailgun is monitoring service impacts in GCP's us-west1 region. We are routing
Started Aug 17, 2026 — Resolved Aug 17, 2026
Aug 17, 13:18 PDT Resolved - We have received confirmation that an external issue impacting email delivery to Microsoft 365 domains has been resolved. Impacted messages would have received an error stating "5.7.511 Access denied, banned sender" between Friday, August 14th and Monday, August 17th. Any failed messages will need to be resent. Information on retrying messages can be found in our Help Center here: https://help.mailgun.com/hc/en-us/articles/18596982041883-Resending-messages
Started Aug 11, 2026 — Resolved Aug 11, 2026
Aug 11, 00:07 PDT Resolved - This incident has been resolved. Aug 10, 23:54 PDT Monitoring - A fix has been implemented and we are monitoring the results. Aug 10, 22:32 PDT Identified - The issue has been identified and a fix is being implemented. Aug 10, 22:32 PDT Investigating - We are currently experiencing a denial of service attack against our click and open tracking servers in our US regions. Remediation work is underway. Some requests may time out or fail at this time.
Pros and cons
Amazon SES
Mailgun
Pros
- Delivers billions of emails per year for Netflix, Reddit, and Amazon
- Lowest cost per email among major providers with simple pay-as-you-go pricing
- Deep integration with the AWS ecosystem and SDKs in all major languages
- Highly scalable with no sending limits after warmup
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
Cons
- Setup is complex with documentation that can be difficult to navigate
- New accounts are sandboxed to 200 messages per 24-hour period
- Accessing analytics requires additional AWS services like SNS and Lambda
Cons
- Requires familiarity with email protocols and API integrations
- Pricing tiers can be confusing
- Email template features are basic without the Mailjet editor
Frequently asked questions
What is the difference between Amazon SES and Mailgun?
Amazon SES is a cost-effective, cloud-scale email service built on AWS infrastructure. Mailgun is a developer-focused email API platform owned by Sinch, known for flexible sending and receiving capabilities. Amazon SES is best suited for cost-sensitive, high-volume, while Mailgun is geared toward developer-focused sending + receiving.
Which is cheaper, Amazon SES or Mailgun?
3,000 free emails per month for the first 12 months. After that, $0.10 per 1,000 emails with additional charges for attachments and dedicated IPs. 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. The best value depends on your sending volume. Use the pricing calculator above to compare costs at your expected volume.
Which is faster, Amazon SES or Mailgun?
Based on real-world data from Knock, Amazon SES has a median API response time (p50) of 160ms compared to 119ms for Mailgun.
Which is more reliable, Amazon SES or Mailgun?
From June 3rd to September 1st, Amazon SES showed an error rate of 0.00% while Mailgun 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, Amazon SES or Mailgun?
On the Knock platform, Amazon SES handled 25M–100M messages from June 3rd to September 1st compared to 100M–500M for Mailgun. Amazon SES volume has remained stable, while Mailgun volume has remained stable.
Can I use both Amazon SES and Mailgun together?
Yes. Knock enables you to integrate multiple email providers into a single notification workflow. You can use Amazon SES and Mailgun 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 Amazon SES vs Mailgun?
Amazon SES strengths include delivers billions of emails per year for netflix, reddit, and amazon and lowest cost per email among major providers with simple pay-as-you-go pricing. 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. On the other hand, Amazon SES drawbacks include setup is complex with documentation that can be difficult to navigate, while Mailgun drawbacks include requires familiarity with email protocols and api integrations.
Use either provider with Knock
Knock enables you to integrate Amazon SES, Mailgun, or any combination of email providers into a single notification workflow. Manage templates, orchestrate cross-channel delivery, and switch providers without changing your code.