What Is ISP Throttling and How to Handle It

How Throttling Works

When a mailbox provider decides to throttle your sending, they respond to your SMTP connection with temporary error codes (4xx series) instead of accepting the message. The most common throttling responses include messages like "421 Try again later," "452 Too many recipients," or provider-specific messages indicating that you have exceeded their rate limits.

Your SMTP provider automatically retries messages that receive temporary errors. The retries typically follow an exponential backoff schedule, waiting longer between each attempt. Most throttled messages eventually deliver, but the delay can be minutes to hours depending on how aggressively you are being throttled.

Throttling is different from blocking (5xx permanent errors) or spam filtering. A throttled message will usually be delivered once the provider is satisfied that you have slowed down. A blocked message is rejected permanently. A spam-filtered message is delivered but placed in the spam folder.

Why Providers Throttle

Mailbox providers throttle for several reasons, and understanding the cause helps you fix the problem:

Volume Spike

The most common trigger. If your normal daily volume is 5,000 emails and you suddenly send 50,000 in one burst, providers treat the spike as suspicious. Spammers and compromised accounts both generate sudden volume spikes, so throttling is the provider's way of slowing things down until they can evaluate whether your mail is legitimate.

Fix: Pace your sends to increase volume gradually. If you need to send at higher volume, ramp up over several days rather than jumping from 5,000 to 50,000 overnight.

Poor Engagement Signals

If a large percentage of your recent messages to a specific provider have gone unopened, unclicked, or deleted without reading, the provider may throttle you because your mail appears unwanted. Low engagement is a reputation signal that affects your priority in the provider's delivery queue.

Fix: Segment your list and focus on engaged subscribers. Remove or re-engage inactive contacts who are dragging down your engagement metrics.

New or Low Reputation Infrastructure

New IPs and domains have no established reputation, so providers are cautious about accepting large volumes from unknown senders. Throttling during the IP warming or domain warming period is normal and expected.

Fix: Follow a gradual warm-up schedule. Start with low volumes and increase by 25-50% per day. Send to your most engaged subscribers first to build positive reputation signals before scaling up.

Shared IP Reputation

If you send from shared IPs (common with most SMTP providers unless you pay for dedicated IPs), another sender on the same pool may have damaged the IP reputation. The provider throttles all traffic from that IP regardless of individual sender quality.

Fix: Contact your SMTP provider to report the issue. Consider upgrading to dedicated IPs if this happens frequently. See the provider selection guide for details on dedicated vs. shared IPs.

Provider-Specific Throttling Behavior

Gmail

Gmail is generally the most tolerant of the major providers. They throttle based on a combination of volume, reputation, and engagement. Gmail's throttling messages are relatively clear and often include a link to their postmaster support page. Setting up Google Postmaster Tools gives you visibility into your domain reputation and helps predict when throttling might occur.

Outlook and Hotmail

Microsoft is the most aggressive throttler. Outlook will throttle new senders very quickly and requires a slower ramp-up than Gmail. Their error messages are less specific, often just returning a generic "421 RP-001" or similar code. Microsoft's Smart Network Data Services (SNDS) provides some visibility into your sending reputation, but the data is less detailed than Google Postmaster Tools.

When throttled by Outlook, reduce your per-hour volume to that domain significantly, sometimes to as low as 100-200 per hour for new senders. Outlook is also more sensitive to complaints and will throttle at lower complaint rates than Gmail.

Yahoo

Yahoo throttles based on similar signals as Gmail but with somewhat lower tolerance for volume spikes. Their error messages typically include a reference URL where you can look up the specific reason for the deferral. Yahoo also provides a feedback loop that forwards spam complaint data to you, which helps you maintain list quality.

Diagnosing Throttling

Check your SMTP provider's delivery logs for 4xx error codes. Common indicators of throttling:

• Messages to one specific domain (like gmail.com or outlook.com) are being deferred while messages to other domains deliver normally
• Your delivery speed to a specific provider drops dramatically during a campaign
• You see retry attempts in your provider's logs for messages that eventually deliver after delays
• Your webhook data shows a spike in deferred events

Throttling is usually domain-specific. If Gmail is throttling you, your Outlook and Yahoo delivery may be fine, and vice versa. This is why ISP-level volume shaping is valuable, since it lets you set appropriate rates for each provider independently.

Preventing Throttling

• Pace your sends: Spread campaigns across time rather than sending everything at once. (Send pacing guide)
• Maintain consistent volume: Send regularly rather than in infrequent large bursts. Providers reward consistency.
• Keep your list clean: Remove bounced addresses and inactive subscribers so you are not wasting deliveries on addresses that generate no engagement. (List cleaning guide)
• Monitor reputation: Check Google Postmaster Tools and your provider's reputation dashboard regularly. Address declining reputation before it triggers throttling. (Monitoring guide)
• Authenticate properly: Complete SPF, DKIM, and DMARC setup. Authenticated senders get higher rate limits from most providers.