Iterable Shared Amazon SES Pool Rate Limited, Bouncing Gmail Mail Since 13 November
Iterable says sends from its shared Amazon SES IP pool have been rate limited since 13 November, delaying mail and turning part of it into bounces, mostly at Gmail. Dedicated IPs are not affected.

Iterable customers who send through its shared Amazon SES IP pool have been seeing delayed sends and elevated bounce rates since 13 November 2026 at 17:55 UTC, according to an incident Iterable opened on its status page on 17 November. The company says sends from the shared pool are being temporarily rate limited, and that most of the resulting bounces are for Gmail addresses.
Iterable says some messages are accepted after a delay, while others that cannot be delivered within the retry window are recorded as bounces. Mail sent from dedicated IPs is not affected. Sends are still going out, bounce volumes have been falling since the first spike, but some customers still see high bounce rates and delayed sends. At the time of writing the incident was still under investigation, with no cause given.
Key facts
- Platform: Iterable (sends through its shared Amazon SES IP pool)
- Start: 13 November 2026, 17:55 UTC, according to Iterable
- Posted: 17 November 2026, 10:24 PST (18:24 UTC) on the Iterable status page
- Component: Global Campaign Sends
- Symptoms: temporary rate limiting, delayed sends, and messages recorded as bounces when they miss the retry window
- Most affected recipients: Gmail addresses; delays possible at other inbox providers
- Not affected: mail sent from dedicated sending IPs
- Status: Investigating; Iterable promised its next update by 11:30 PST (19:30 UTC)
What Iterable reported
The incident is titled "Elevated Bounce Rates for Customers Sending via SES Shared IP Pools". Iterable writes that since 13 November, sends from its shared SES IP pool are being temporarily rate limited. In practice that produces two outcomes for the same campaign: part of the mail is accepted late, and part of it is never delivered and ends up recorded as a bounce once Iterable's retry window runs out.
Iterable says the majority of those bounces are for Gmail addresses, but that sends to other inbox providers may also be delayed. The company is working with its email infrastructure partners to find the cause and restore normal delivery. The status page does not say who applies the rate limit, and SMTPedia has not seen an official explanation from Iterable, Amazon or Google.
A problem that started four days before the notice
The start time given by Iterable, 13 November at 17:55 UTC, is four days before the status page entry. Teams that noticed a jump in Gmail bounces in their Iterable reports since last Thursday now have a likely explanation. It also means bounce and engagement metrics for campaigns sent from the shared pool since that date are not a clean picture of list quality.
Why these bounces need care
These are bounces caused by a sending-side rate limit, not by bad addresses. If your workflows suppress contacts automatically after a bounce, valid Gmail subscribers may have been suppressed or flagged as undeliverable during the incident. Deferrals that turn into bounces after a retry window are explained in our guide to the 421 4.7.0 unexpected volume deferral.
What it means for senders
What changes
Iterable mail sent from its shared Amazon SES IP pool is being rate limited, so part of it arrives late and part of it bounces, mostly at Gmail. Bounce rates for those sends since 13 November do not reflect the real quality of your list.
Who is affected
Iterable customers who send through the shared SES IP pool, especially those with large Gmail audiences. Customers on dedicated sending IPs are not affected, according to Iterable.
When
Since 13 November 2026 at 17:55 UTC. The incident was still open on 17 November, with an update promised by 11:30 PST (19:30 UTC).
Action checklist
- Check your sending IP setup in Iterable to confirm whether your campaigns use the shared SES pool or dedicated IPs.
- Review Gmail bounces since 13 November and separate rate-limit bounces from real hard bounces before you clean your list.
- Restore wrongly suppressed contacts if your workflows suppressed Gmail addresses after a single bounce during the incident.
- Delay non-urgent Gmail-heavy campaigns from the shared pool until Iterable reports normal delivery.
- Read engagement data with caution for campaigns sent since 13 November, since late delivery lowers opens and clicks.
- Follow the status page for Iterable's next update and the final cause.
Sources
- Iterable Status: Elevated Bounce Rates for Customers Sending via SES Shared IP Pools, posted 17 November 2026 (primary source)
Related on SMTPedia
SMTPedia News follows our editorial standards. Spotted an error? See how we correct it.
Get SMTPedia news first on Google
Add us as a preferred source to see our stories in Top Stories and Discover.
Add as preferred sourceUseful story?
SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.
Buy SMTPedia a coffeeNewsletter