Suped

Why were there delays to Apple domains in January 2024 and have they been resolved?

Summary

In January 2024, many email senders reported significant delays and timeout errors when delivering emails to Apple domains, including iCloud, me.com, and mac.com. This widespread disruption, initially observed around January 16, 2024, sparked concerns across the email deliverability community. While initial reports indicated potential issues on senders' sides, further investigation and collective observations quickly pointed towards a systemic problem within Apple's mail infrastructure. The incident highlighted the fragility of email delivery and the critical need for constant monitoring, especially when dealing with major mailbox providers. Thankfully, the issue appeared to be largely resolved within a few days.

What email marketers say

When sudden email delivery delays hit major domains like Apple, email marketers are often on the front lines, observing the initial impacts. In January 2024, many marketers quickly noticed a slowdown in emails reaching Apple users, leading to discussions about whether the issue was isolated to their own sending infrastructure or part of a larger, systemic problem. Their collective experiences and dashboard observations provided crucial real-time insights into the nature and scope of the disruption, highlighting the importance of shared knowledge within the deliverability community.

Marketer view

Marketer from Email Geeks observed immediate delays to Apple domains, noting timeout-type events affecting multiple customers starting January 16, 2024. These issues seemed widespread, impacting various customer accounts.

18 Jan 2024 - Email Geeks

Marketer view

Marketer from Email Geeks reported hearing other accounts of Apple domain delays, suggesting a wider issue beyond their own operations. This kind of corroboration is valuable for understanding the scope of a problem.

17 Jan 2024 - Email Geeks

What the experts say

Email deliverability experts possess the technical acumen to diagnose complex issues like the January 2024 Apple domain delays. Their insights often delve into specific IP addresses, server behaviors, and the underlying mechanisms of mail routing. During this incident, experts quickly moved beyond anecdotal evidence to pinpoint precise indicators, such as shifts in Apple's Mail Exchange (MX) IPs and changes in connection rejection patterns, offering a more definitive understanding of the problem's root cause and eventual resolution.

Expert view

Expert from Email Geeks confirmed widespread connection rejections from specific Apple MX IPs, including 17.57.154.33, 17.57.156.30, and 17.42.251.62, over a two-day period. This detailed IP-level analysis provided crucial technical evidence of the problem.

17 Jan 2024 - Email Geeks

Expert view

Expert from Email Geeks observed a drop in rejections and a spike in accepted messages on other Apple MX IPs (17.56.9.29, 17.57.155.34), indicating a rotation. This observation was key to understanding that Apple was actively addressing the issue internally.

17 Jan 2024 - Email Geeks

What the documentation says

Official documentation from various sources, including Apple's own policies and general email standards, provides the foundational rules governing email delivery. While these documents rarely address specific, transient outages, they offer crucial context for understanding why delays or rejections might occur. They outline the expected behaviors of mail servers, authentication protocols, and reputation management, all of which play a role when a major incident like the January 2024 Apple delays unfolds.

Technical article

Documentation from Apple's Mail Policy states that 'delivery to iCloud Mail may be deferred or rejected if the sending IP address or domain has a poor reputation'. This highlights the critical role of sender reputation in Apple's email ecosystem. It indicates that reputation is a primary filter for incoming mail.

15 Jan 2024 - Apple Mail Policy

Technical article

Documentation from RFC 5321 (SMTP) outlines that a '4xx' SMTP response code indicates a transient failure, suggesting that the sending server should attempt re-delivery at a later time. This standard behavior is essential for handling temporary network or server issues.

10 Jan 2024 - RFC 5321 (SMTP)

5 resources

Start improving your email deliverability today

Get started