Is SparkPost down?

Beginning 2026-08-26 around 23:00 UTC, we are observing a significant increase in hard bounces for messages sent to recipients at privaterelay.appleid.com, the relay domain used by Sign in with Apple. Affected messages are rejected by Apple's mail servers with the SMTP response 550 5.1.1 user not found. Our investigation confirms this originates upstream at the receiving mailbox provider, not within our platform. Delivery to all other domains, including icloud.com, me.com, and mac.com, remain unaffected and are performing normally. A substantial share of the affected addresses delivered successfully as recently as 2026-08-26, indicating the rejections do not reflect genuine invalid recipients. Impact: Because these are hard bounces, affected recipient addresses may be automatically added to your suppression list, which will prevent future sends to those recipients even after the underlying issue is resolved. Action required: None at this time. We recommend you do not attempt to manually clean or re-import affected suppression entries while the issue is ongoing. We are working directly with Apple on a resolution. Once resolved, we will remove suppression entries created by this event and will confirm the scope and timing in a follow-up update. We will post our next update within 4 hours or sooner if the situation changes.

We continue to see elevated 550 5.1.1 user not found hard bounces from Apple private relay. Once resolved on the provider's side, we will automatically remove Apple Private Relay suppression entries created by this event.

We have started to see recovery of the Apple private relay domain. We will continue monitoring for the next 60 minutes to confirm full recovery. Our team is actively working on automatically removing any suppressions that were created by this event. We anticipate the cleanup to be completed by 4PM EDT.

We have seen recovery of the Apple private relay domain to pre-event bounce levels. Our team is actively working on automatically removing any suppressions that were created by this event. We anticipate the cleanup to be completed by 6PM EDT.

The Apple bounce levels have maintained at pre incident levels during our monitoring phase. Our clean up of the bad suppressions has finished. This incident is resolved.

We are investigating an increase in delivery latency for some outbound messages. (NOTE: This does not impact our customers hosted in the US.)

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating delivery issues caused by an ongoing AWS US West 2 region outage. Customers may experience delays or failures while we assess the impact to our service. We are actively monitoring the situation and will provide updates as more information becomes available.

Outbound email delivery is blocked for our US West region. We working with our vendor resolve the issue. We are continuing to accept emails and queue them internally. We will deliver the messages as soon as the issue is resolved.

We are starting to deliver mails in our US West region. We are working through the queued messages. We are continuing to monitor the issue and continuing to accept emails.

We are still working through the queued messages. We are continuing to monitor the issue and continuing to accept emails.

We have implemented additional tuning to handle the significant influx of mail due to the AWS network outage and we are seeing improvement in delivery rates We are seeing significant recovery and expect most mail to be fully delivered in the next 30-35 minutes. Estimated time for full recovery is 80-90 minutes. We are continuing to look for additional optimizations and monitor the issue.

This incident has been resolved.

We are investigating the delay and the impact. We will post once we know more.

There was a combination of events that caused a short period of slowdown. That slowdown has already recovered and we are monitoring to ensure we do not see it again.

This incident has been resolved.