Why Are Mailgun Rate Limits Important for Deliverability?

You’ve built a high-performing campaign. Your list is clean, your copy is sharp, and the timing feels right. Then you hit a wall: emails stop going out. You check your logs—no error message, just silence. This isn’t a bug. It’s Mailgun enforcing your rate limits.

Rate limits aren’t just arbitrary caps. They're a core part of sender reputation and inbox placement. When you exceed them, Mailgun throttles your sends or temporarily blocks your account. This doesn’t just slow things down—it damages your long-term deliverability. Every burst too big, every spike too sharp, risks marking you as a potential spammer, even if you’re not. Understanding how Mailgun’s rate limits work isn’t optional for senders under load. It’s essential.

Key takeaways

  • Mailgun rate limits prevent abuse and protect sender reputation through time-based sending controls.
  • Exceeding rate limits triggers throttling or temporary blocks, which degrade inbox placement and sender health.
  • Planning around Mailgun’s tiered limits is mandatory for consistent delivery in high-volume campaigns.

What Are Mailgun’s Standard Rate Limits?

You’re capped at 300 emails per minute on every Mailgun account, no matter the tier. This limit applies to individual sends and bulk campaigns alike—sending faster triggers delays. If you regularly exceed this, upgrading to a higher tier is required for sustained throughput.

Burst Sending vs. Sustained Volume

Mailgun allows short bursts up to 300 emails per minute, but if your system sends consistently beyond that, messages get throttled. This isn’t just a soft limit—it’s enforced via SMTP and API-level rate checking, which means delayed or queued emails aren’t optional. Some senders experience backpressure during spikes, especially in automated workflows like onboarding or transactional sends.

For context, this 300-email-per-minute cap aligns with common industry standards for email delivery infrastructure. The RFC 5321 (SMTP) specification doesn’t define a universal rate limit, but most providers—including AWS SES, SendGrid, and Postmark—enforce similar constraints on shared infrastructure. You can think of it as a fairness mechanism that prevents one sender from monopolizing server resources.

When You Need to Upgrade

If you're sending more than 300 emails per minute on a regular basis—say, for marketing campaigns, transactional alerts, or user notifications—you’ll need to move up to a higher-tier plan. Tier upgrades unlock higher monthly sending quotas and increased per-minute limits, depending on the plan. Skipping an upgrade means your queue fills up, delays increase, and inbox placement drops.

It’s not uncommon for growth-stage apps to hit this ceiling in just a few weeks. You can check your sending patterns with tools like MailTester’s inbox placement tester or bulk email verification to pre-empt deliverability issues before scaling up. Cleaning lists early reduces the number of emails sent, easing strain on any rate-limiting system.

How Do Mailgun’s Account Tiers Affect Rate Limits?

You get higher sending capacity and larger hourly limits with Mailgun’s paid tiers—Free users are capped at 300 emails per hour, while Core, Pro, and Enterprise tiers scale up to thousands per hour. Per-minute limits stay at 300 across all plans, but sustained volume increases with your tier. Higher tiers also add dedicated IPs, better analytics, and priority support, all of which help keep your sender reputation strong over time.

Sending Capacity Scales with Your Plan

Let’s break it down: the Free tier allows 300 emails per hour. That’s enough for small senders testing the platform, but not for active campaigns. As you move to Core and beyond, those hourly caps increase significantly—though the 300 per-minute ceiling remains unchanged. This means you can send bursts of 300 in a minute, but over time, higher tiers give you more room to send consistently without hitting throttle limits.

Even if your sends don’t spike, the higher sustained volume of Pro and Enterprise plans prevents delivery bottlenecks during peak traffic. If you're syncing with a CRM or running automated workflows, steady throughput matters. For example, while a Free account might block after 2,000 emails per day, a Pro account can handle tens of thousands—depending on volume patterns and sending patterns.

Deliverability Benefits Go Beyond Just Numbers

It’s not just about sending more. Higher tiers unlock dedicated IPs, which help avoid the shared reputation risk of sending from common IP blocks. This is a known practice among high-volume senders to maintain inbox placement, especially in competitive industries like ecommerce or marketing.

Plus, advanced analytics and priority support can help you catch delivery issues early. Tools like MailTester’s inbox placement testing let you check actual inbox placement across providers before sending to full lists—helping you validate whether your Mailgun setup is optimized. Even if your email isn’t rejected, poor deliverability can kill engagement, so verifying list health before sending is essential.

Keep your sender reputation clean by managing volume and infrastructure. Mailgun’s tier model gives you room to scale while protecting your long-term message placement. For context, the Messaging, Malware, and Mobile Anti-Abuse Working Group (M3AAWG) emphasizes the importance of rate control and infrastructure choice in maintaining trust across messaging networks.

What Happens When You Hit Mailgun’s Rate Limits?

When you exceed Mailgun’s 300 emails per minute threshold, your requests return an HTTP 429 (Too Many Requests) error. Mailgun delays or queues your messages until the rate limit resets, causing delivery delays without a bounce. Repeated violations can lead to temporary IP-level throttling or damage to your sender reputation, especially if paired with low engagement or spam complaints.

HTTP 429 Errors and Message Queuing

If you send emails faster than 300 per minute, Mailgun blocks your request with a 429 response. This doesn’t mean the email failed—it means it’s waiting its turn. Unlike hard bounces, there’s no immediate feedback, but you’ll see delayed delivery in your logs. For high-volume senders, this can silently slow down campaigns or trigger timeouts in automated workflows.

Mailgun uses a token bucket algorithm to manage rate limits. Once the bucket empties, new requests are queued until tokens refill. This means short bursts are acceptable, but sustained sending above the limit triggers throttling. To avoid this, monitor your sending volume and distribute traffic evenly across the minute.

Long-Term Risks: Throttling and Reputation

Consistently hitting rate limits—even briefly—signals poor sending hygiene to Mailgun’s systems. While not an instant ban, repeated violations increase the chance of temporary IP-level throttling, especially if your emails also suffer from low open rates or high spam complaint ratios.

Reputation damage isn't just about sending behavior; it’s a combination of volume, velocity, and engagement. A high-volume sender with frequent 429s and low engagement is more likely to be flagged than a lower-volume sender with consistent, high-quality message delivery. This is why Mailgun’s system penalizes patterns that resemble spam behavior.

RFC 2821, the foundational email specification, defines delivery as a request-response system—timing and retry behavior matter. Mailgun’s rate limiting ensures compliance with this principle under real-world load.

If you're unsure whether your sending volume is safe, use a tool like MailTester’s bulk verification to scrub invalid or high-risk addresses before sending. This reduces the total number of emails you need to send, keeping you within Mailgun’s limits and improving engagement.

Even with proper rate limits, poor list quality can still degrade deliverability. If you’re sending regularly but seeing low inbox placement, check spam traps or bad sender reputation. Tools like MailTester’s inbox placement test can help identify whether your emails are being filtered.

How to Avoid Throttling When Using Mailgun

You stay under Mailgun’s rate limits by capping your send rate at 300 emails per minute, spreading high-volume sends across multiple time windows, and using exponential backoff to handle 429 errors without triggering a retry storm. Monitor your logs and dashboard to catch spikes early and adjust in real time. This keeps your outbound mail consistent and inbox-ready.

Stick to Sustainable Send Rates

  • Keep your send rate consistently below 300 emails per minute—Mailgun’s hard limit for most accounts.
  • If you’re sending more than 300, split the load across non-overlapping time windows (e.g., 200 emails every 30 seconds over 90 seconds).
  • Large campaigns should be batched into smaller chunks to avoid triggering throttling even if total volume is within limits.

Handle Errors Gracefully with Exponential Backoff

  • When Mailgun returns a 429 Too Many Requests error, don’t retry immediately—this causes retry storms and worsens throttling.
  • Use exponential backoff: wait 1 second after the first failure, then 2, 4, 8, etc., increasing delay each time until successful.
  • Refer to the RFC 6585 standard for HTTP status codes, including 429, which defines proper retry behavior for overloaded systems [RFC 6585].

Let’s be clear: throttling isn’t just a rate limit issue—it’s a reputation risk. Each 429 response can flag your IP or domain, especially if repeated. You can avoid that by building elasticity into your sending logic.

Rate limiting is not punishment. It’s a signal to adjust.

Use Mailgun’s real-time logs and dashboard to spot send spikes before they cause issues. Watch for sudden increases in requests or errors—especially during automated campaigns.

You can verify your email list ahead of sending to reduce errors, throttle risk, and improve deliverability. High-quality lists mean fewer failed deliveries and lower bounce rates. Try bulk verification to clean your list before deployment, or use our real-time verification API to validate on entry.

For full inbox placement insights, test your campaign content and structure with our inbox tester. This gives you a realistic preview of how your messages land, helping avoid reputation drops even if you’re under the rate limit.

Is There a Maximum Hourly Limit in Mailgun?

Mailgun doesn’t enforce a fixed hourly limit across all accounts. Instead, it uses dynamic rate management based on your IP reputation, sending history, and domain health. While you can technically send more than 15,000 emails per hour, doing so consistently—especially on lower-tier accounts—may trigger throttling or scrutiny. High-volume senders should prioritize consistent, well-reputed sending over short bursts.

How Rate Limits Adapt Over Time

Mailgun adjusts limits in real time. If your sending pattern shifts suddenly—say, from 500 to 15,000 emails in an hour—automated systems may flag it as abnormal, even if you’re under a published cap. This is standard across SMTP providers: reliability and consistency matter more than peak throughput.

For example, a sender with a solid reputation can sustain 10,000 to 15,000 emails per hour across multiple hours without issues. But new or unverified accounts often face stricter limits, especially when testing or warming up a domain. The system rewards steady, legitimate volume over spikes.

Why Consistency Beats Peak Volume

Even on higher-tier plans, Mailgun doesn’t guarantee a hard ceiling. What changes is the likelihood of throttling. You can send 20,000 emails an hour on a premium plan—but if your inbox placement drops, or you hit spam traps, you’ll still get hit with rate limits.

Industry best practices—like those outlined in RFC 5321—emphasize responsible sending. Tools like MailTester’s bulk verification help you avoid sending to invalid or risky addresses, reducing strain on your sending infrastructure and improving long-term deliverability.

Let’s be clear: there’s no “maximum” you can set and forget. Your actual limit depends on reputation, list hygiene, and sender authentication. A clean, well-verified list gives you far more flexibility than one full of dead or disposable addresses.

Pro tip: Test your sending capacity in stages. Start at 5,000 emails/hour, monitor bounce rates and delivery success, then scale gradually. Use inbox placement testing to validate real-world delivery before full rollout.

How to Monitor Your Sending Capacity in Real Time

You can monitor your Mailgun rate limits and sending capacity in real time by using SMTP API logging, Event Webhooks, and integration with monitoring tools. Set up webhooks to capture 429 throttling responses and spikes in send volume, then trigger alerts when thresholds are exceeded. This allows you to react before delivery degrades or your account gets throttled.

Track Sending Activity with API Logs and Webhooks

  • Enable SMTP API logging in your Mailgun dashboard to record every message sent, including timestamps, recipient counts, and response codes.
  • Use Mailgun’s Event Webhooks to capture real-time delivery events—delivered, bounced, blocked, or throttled—so you can detect rate limit issues as they happen.
  • Feed webhook data into tools like Datadog, Grafana, or Prometheus to visualize send volume trends and spot anomalies like sudden bursts.

Set Alerts for Throttling and High Volume

  • Configure custom alerts in your monitoring tool to trigger when you receive repeated 429 (Too Many Requests) responses—this indicates throttling due to exceeding your rate limits.
  • Set up thresholds for send volume per minute or hour based on your account tier (e.g., 200 sends/minute for a Free Tier) and trigger warnings when you approach or breach them.
  • Use webhooks to capture events like “throttled” or “blocked” and route them to Slack, PagerDuty, or email so your team can respond immediately.

Mailgun enforces rate limits on a per-domain basis, and exceeding them can lead to delays or blocked messages. According to RFC 6409, transient 429 responses are a standard indicator of rate-limiting in SMTP systems, making real-time detection critical. Ignoring throttling signals often results in delivery failure and reduced sender reputation.

Let’s say you’re sending transactional emails through Mailgun. If you're not tracking sends and responses in real time, you might miss a spike that triggers throttling—especially when users share links or campaigns go viral. That’s why integrating webhooks with your observability stack is not optional; it’s how you avoid sending delays.

You can also use MailTester to scrub your list before sending to reduce the risk of hitting limits due to invalid or high-volume domains. Bulk verification removes bounce-prone addresses, and inbox placement testing helps you validate delivery before scale. If you’re building a system that sends at scale, the verification API can help check individual addresses on-demand.

Ultimately, monitoring isn’t just about knowing when you hit a limit—it’s about preventing it. Use logs, webhooks, and alerts to stay ahead of capacity constraints and keep your delivery reliable. That’s how you maintain inbox placement and sender reputation over time.

What Role Does Email List Hygiene Play in Rate Limit Management?

You can stay within Mailgun’s send limits but still hit rate limits or throttling if your list includes invalid, disposable, or role-based emails. High bounce rates — even from a small number of bad addresses — signal poor sender health. This can trigger defensive measures from Mailgun even if your volume is under the threshold. Clean lists reduce bounces, maintain sender reputation, and keep your sending behavior sustainable.

Bounce Rates Are a Hidden Trigger

Mailgun’s systems monitor not just how many emails you send per second, but also the quality of those deliveries. Sending to addresses that don’t exist, are role-based (like admin@ or sales@), or belong to disposable domains results in hard or soft bounces. When these accumulate, even at low volumes, Mailgun’s algorithms may interpret your sending as risky. This can lead to throttling, rate limit enforcement, or temporary suspension — regardless of your send volume.

For example, a 2% bounce rate might seem low, but if those bounces come from outdated or low-quality email addresses, they harm your reputation. The Internet Society’s ISOC notes that consistent sending to invalid addresses is a hallmark of poor list hygiene and a red flag for email service providers.

Verification Is the Foundation of Sustainable Sending

Let’s be clear: you can’t manage rate limits effectively if your list isn’t clean. Before sending to any audience, verify those email addresses. Tools like MailTester check for validity, catch-all responses, disposable domains, and role-based accounts in real time. You can test your list in bulk via the bulk verification tool, use the API for real-time validation, or run inbox placement tests to simulate real-world delivery.

With MailTester’s 98.9% accuracy, you’ll catch invalid addresses before they send — reducing bounces, protecting your sender reputation, and avoiding unnecessary throttling. The same applies to the verification API, which you can embed in registration flows or upload pipelines. No more guessing. Just cleaner sending.

Sending more doesn’t mean sending better. Clean lists aren’t just about deliverability — they’re about staying within Mailgun’s thresholds without triggering defensive behavior. You’re not trying to game the system; you’re keeping your sending honest, which is the best way to stay out of trouble.

How MailTester Can Help You Stay Within Mailgun Limits

You can avoid Mailgun’s rate limits by catching invalid and risky emails before sending. MailTester’s bulk verification API checks thousands of addresses in minutes, filtering out bad ones upfront. This keeps your sending volume within safe thresholds and reduces bounce rates—key factors in maintaining sender reputation and avoiding throttling. Let’s look at how.

Pre-Send Cleanup with High Accuracy

MailTester’s bulk verification API processes large lists in minutes, identifying invalid, disposable, and catch-all emails before they hit your Mailgun send queue. With 98.9% accuracy, it helps you send only to addresses likely to receive your message, reducing bounces and preventing your sender reputation from degrading. A good reputation is essential—it affects how Mailgun treats your sending patterns, especially under strict rate limits.

High bounce rates trigger throttling or even suspension, but MailTester reduces that risk by filtering out addresses that don't exist or are otherwise unreliable. You’re not just saving bandwidth—you’re protecting your inbox placement. For instance, a 2022 report from Return Path noted that emails from senders with high bounce rates were more likely to land in spam folders or be blocked entirely.

Flexible, Non-Expiring Credits for Ongoing Maintenance

Start with 100 free verifications—no strings attached—then continue with credits that never expire. This makes it easy to verify new leads, clean up old lists, and maintain consistency without worrying about sudden overages or forced pauses. You can run regular checks using the real-time API at https://mailtester.com/api-email-checker, or schedule bulk runs via https://mailtester.com/email-list-verify.

It’s not just about avoiding limits—it’s about building a sustainable sending workflow. Tools like Mailgun apply throttling based on reputation metrics, and you can’t outspend trust. With MailTester, you’re investing in clean data, which directly improves deliverability. You can even test how your messages land in real inboxes through the inbox placement tool at https://mailtester.com/inbox-tester, ensuring compliance with standards from organizations like the Messaging, Malware, and Mobile Anti-Abuse Working Group (M3AAWG).

Whether you’re using Mailgun through integrations with HubSpot, Klaviyo, or SendGrid, or sending directly via API, clean lists are your best defense against rate limits. Start now with a free tier, and keep your sender profile strong with reliable verification at https://mailtester.com/pricing.

How to Scale Send Volumes Without Exceeding Limits

You can scale your email volume safely by batching sends (like 10,000 emails per hour), using connection pooling and async sending to avoid bursts, and upgrading to Pro or Enterprise tiers if you exceed 100,000 daily emails. This keeps you under 300 emails per minute, avoids throttling, and ensures consistent inbox placement.

Burn the Fuel Gradually: Batch Scheduling & Rate Control

  • Split large campaigns into batches no larger than 10,000 emails per hour, which keeps your rate below Mailgun’s 300 emails per minute default limit.
  • Use scheduled send times (e.g., every 20 minutes) to avoid bursts and maintain steady delivery pacing.
  • Monitor real-time delivery metrics in Mailgun’s dashboard — if you see throttling or delays, your batch size is still too high.

Optimize the Engine: Connection & Infrastructure

  • Enable SMTP connection pooling to reuse existing connections instead of opening new ones for every email — this reduces overhead and avoids connection spikes.
  • Send asynchronously (non-blocking) to prevent queue buildup when sending at scale. This allows your app to process other tasks while emails are in transit.
  • Use persistent connections with SMTP Keep-Alive settings to maintain stable throughput without hitting rate limits during high volume.

When sending over 100,000 emails per day, upgrading to Mailgun’s Pro or Enterprise tier gives you higher rate limits, dedicated IPs, priority support, and access to advanced delivery tools. These tiers are designed for volume, and they help maintain sender reputation at scale.

Before you send, verify your list. Invalid or risky addresses increase bounce rates and hurt deliverability. Use MailTester’s bulk verification to remove bad addresses before deployment — it checks for syntax, domain validity, and inbox responsiveness. This reduces the risk of hitting rate limits due to high bounce volume.

Real-time API checks help prevent bad sends during onboarding or registration flows. Run delivery tests with inbox placement testing to see how your messages land in real inboxes. These tools don’t just prevent bounces — they help you stay within safe sending patterns.

Consistent sending volume is more effective than short bursts. The goal isn't to send fast — it’s to send reliably.

For ongoing campaigns, consider integrating MailTester with your workflow via native integrations with Mailchimp, HubSpot, Klaviyo, or SendGrid. This ensures your list stays clean and your sending stays within Mailgun’s limits.

If you’re unsure what tier fits your volume, review MailTester’s pricing for a clear view of what’s included. The right infrastructure doesn’t just lift limits — it protects your sender reputation.

Final Thoughts on Maintaining Deliverability at Scale

Rate limits in Mailgun aren’t just technical boundaries—they’re part of a larger system designed to protect sender reputation. Exceeding them consistently can trigger throttling or blacklisting, even with valid content.

Deliverability at scale depends less on sending volume and more on sending behavior: clean lists, predictable patterns, and real-time monitoring of bounces and feedback loops. Automation that ignores these signals increases risk.

Tools like MailTester help you verify large lists in advance, flagging invalid, toxic, or non-reachable addresses before sending. This ensures you stay within Mailgun’s rate limits while maximizing inbox placement and protecting reputation.

Sources

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What is the default Mailgun rate limit?

The default rate limit is 300 emails per minute across all account tiers. Exceeding this triggers throttling or delays.

Does Mailgun have a daily sending limit?

Mailgun does not enforce a hard daily cap. However, sustained high volume without proper list hygiene may trigger rate throttling.

Can I increase my Mailgun rate limit?

Yes—upgrading to a higher-tier account (Pro or Enterprise) increases sending capacity and reduces throttling risk.

What does a 429 error mean in Mailgun?

A 429 error means you’ve exceeded the rate limit. Mailgun will delay or queue your messages until the threshold resets.

How does list hygiene affect Mailgun’s rate limits?

Sending to invalid or disposable addresses increases bounces, which can trigger throttling even if volume is within limits.

What is the best way to test if my sends stay within Mailgun limits?

Use Mailgun’s event logs and webhooks to monitor send volume and detect bursts. Combine with list hygiene tools like MailTester.

Does Mailgun throttle based on engagement or list quality?

Yes—poor engagement and high bounce rates can trigger stricter throttling, even if volume is within the per-minute cap.

How can I verify email lists before sending on Mailgun?

Use MailTester to verify addresses in bulk prior to sending. It filters out invalid, catch-all, and disposable emails with 98.9% accuracy.

Do Mailgun rate limits vary by domain or IP?

Yes—rate limits are applied per domain and IP. Sending from a new domain or IP may trigger temporary restrictions until reputation builds.

Can I send 100,000 emails in one hour with Mailgun?

It’s possible with a Pro or Enterprise tier, but only if the email list is clean and sending is distributed evenly to avoid 300-email/minute bursts.

What happens if I send too many emails too fast?

Mailgun returns a 429 error, delays messages, and may throttle your IP or domain if sending behavior is inconsistent or low quality.

Is there a way to monitor rate limits in real time?

Yes—use Mailgun’s event webhooks and dashboard logs to track send volume and detect spikes before they exceed thresholds.