Mailgun vs Postmark
Compare Mailgun and Postmark 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 |
| 25M–100M | 4th of 10 → | 1 | 11 |
From February 10th to May 11th, Knock routed 100M–500M messages through Mailgun and 25M–100M through Postmark. Mailgun reported 7 status page updates over the last 90 days, while Postmark reported 11.
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 24ms for Postmark. Mailgun's highest daily p50 was 147ms; Postmark's was 57ms. Postmark is 106ms 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 87ms for Postmark. The highest daily p90 was 220ms for Mailgun and 143ms for Postmark. Postmark handles these slower requests 98ms 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 Postmark reached 230ms. The highest daily p99 was 501ms for Mailgun and 38235ms for Postmark, indicating the worst-case response time during spikes or provider-side congestion. Postmark 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.03% | 2.37% | Mar 27 | 86 | 2 |
Averaged across the date range, Mailgun shows a 0.00% daily error rate compared to 0.03% for Postmark. The highest single-day error rate was 0.03% for Mailgun and 2.37% for Postmark. 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 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 Postmark incidents
Recent status page incidents for Postmark
Started Apr 21, 2026 — Resolved Apr 21, 2026
Good news - this issue has been resolved and everything should be working normally now. We're continuing to monitor closely to make sure everything stays stable. Thank you so much for your patience while we worked through this.
Started Apr 8, 2026 — Resolved Apr 9, 2026
**[UPDATE]** We determined that yesterday's network instability was caused by a widespread Google (Gmail) outage. You can find more information on Google’s Status Dashboard here: https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT We will share an additional update regarding our internal action items later today.
Started Apr 2, 2026 — Resolved Apr 3, 2026
**[UPDATE]** On **April 2nd** starting at **~07:00pm UTC**, Postmark experienced an incident that resulted in delayed message delivery and webhook notifications for some customers. The issue was caused by an infrastructure configuration change that disrupted internal mail routing. While messages were safely queued in a "Processing" state, they were not delivered until the routing configuration was restored. Service was restored on **April 3rd at ~4:20am UTC** and the backlog of queued message
Started Mar 27, 2026 — Resolved Mar 28, 2026
We've resolved the incident. Thanks for your patience.
Started Mar 26, 2026 — Resolved Mar 26, 2026
The issue has been resolved.
Pros and cons
Mailgun
Postmark
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
- Excellent deliverability with separate infrastructure for transactional and bulk messages
- Publishes time-to-inbox data across major email providers for transparency
- Great documentation with official and community-supported SDKs for all major languages
- 45-day message and log retention on all plans
Cons
- Requires familiarity with email protocols and API integrations
- Pricing tiers can be confusing
- Email template features are basic without the Mailjet editor
Cons
- No visual drag-and-drop email editor
- Less suited for high-volume marketing email
- Smaller feature set compared to all-in-one platforms
Frequently asked questions
What is the difference between Mailgun and Postmark?
Mailgun is a developer-focused email API platform owned by Sinch, known for flexible sending and receiving capabilities. Postmark is a transactional email service focused on fast, reliable delivery with transparent pricing. Mailgun is best suited for developer-focused sending + receiving, while Postmark is geared toward transactional email.
Which is cheaper, Mailgun or Postmark?
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 100 emails per month. Paid plans start at $15/month for 10,000 emails with overages at $1.80/1K up to 125K, and $1.70/1K at 300K+. 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 Postmark?
Based on real-world data from Knock, Mailgun has a median API response time (p50) of 130ms compared to 24ms for Postmark.
Which is more reliable, Mailgun or Postmark?
From February 10th to May 11th, Mailgun showed an error rate of 0.00% while Postmark showed 0.03%. 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 Postmark?
On the Knock platform, Mailgun handled 100M–500M messages from February 10th to May 11th compared to 25M–100M for Postmark. Mailgun volume has remained stable, while Postmark volume has remained stable.
Can I use both Mailgun and Postmark together?
Yes. Knock enables you to integrate multiple email providers into a single notification workflow. You can use Mailgun and Postmark 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 Postmark?
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. Postmark strengths include excellent deliverability with separate infrastructure for transactional and bulk messages and publishes time-to-inbox data across major email providers for transparency. On the other hand, Mailgun drawbacks include requires familiarity with email protocols and api integrations, while Postmark drawbacks include no visual drag-and-drop email editor.
Use either provider with Knock
Knock enables you to integrate Mailgun, Postmark, or any combination of email providers into a single notification workflow. Manage templates, orchestrate cross-channel delivery, and switch providers without changing your code.