Sparkpost outage history

We are investigating an increase in delayed (deferred) messages in both our US and EU regions, beginning at approximately 14:40 UTC on October 11. A subset of our internal DNS resolvers are intermittently failing to resolve recipient domains, causing some delivery attempts to be temporarily deferred. Affected messages are not being dropped or bounced. Retries are succeeding as they are routed to healthy resolvers, so impacted messages are being delivered with additional latency. Customers may observe an elevated number of delay events in webhooks, event logs, and reporting during this time. We have identified the cause as a DNSSEC validation issue on a portion of our resolver fleet related to a scheduled update of the internet's root DNS signing key, and are applying a fix. No action is required from customers. We will provide an update within 60 minutes or as soon as we have more information.

We are continuing to rollout the new root signing keys from ICANN. We continue to see recovery across our global clusters.

We are continuing to work on a fix for this issue.

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

This incident has been resolved.

Some email deliveries are being delayed. The delays come and go, and queued messages are being delivered once each one clears. Our team is investigating the cause and working on a fix. We'll post an update here as soon as we know more. We apologize for the disruption.

We've made changes to address the intermittent delivery delays. Since then, email has been delivered without delay, including during peak sending periods that previously caused the slowdowns. We're watching closely to confirm the issue is fully resolved and will post an update here. Thank you for your patience.

This issue has been resolved. Since our changes went in, we've seen no further delivery delays, including through peak sending periods. Email is being delivered normally. We apologize for the disruption and thank you for your patience.

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

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

This incident has been resolved.

Health score and Cohort data is delayed.

We know what has caused the data delay and are working to get the data posted.

Data is reprocessed and loads are completing. Full data recovery expected in the next 30 minutes.

The data has all been posted. We apologize for the delay.

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 between 4-6PM 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 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.

We’re currently investigating an issue that prevented some customers from updating their payment details. The root cause has been identified, and a fix is being implemented.

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

This incident has been resolved.

We are experiencing an elevated level of errors and latency on the Suppression List API for some SparkPost customers. Please retry any 5xx error. Note: This issue does not impact SparkPost customers hosted in the EU.

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

This incident has been resolved.

We are looking into why some messages are seeing delayed delivery.

The issue has been identified and a fix is being implemented.

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

This incident has been resolved.

We are currently investigating this issue.

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

This incident has been resolved.

We are currently investigating reports of delayed or failed email deliveries to Apple-hosted domains. Messages to non-Apple domains are unaffected. We will provide updates as more information becomes available.

The issue was caused by an Apple iCloud Mail outage (https://www.apple.com/support/systemstatus/), which Apple has since marked as resolved. Bounce rates and delivery delays to Apple domains have returned to normal levels. We are currently reviewing our suppression lists to identify and remove any recipients that may have been incorrectly added during the incident.

Apple has implemented a fix and we are monitoring the results.

Delivery rates to Apple domains have returned to normal with no further elevated delays or bounces. We will perform any necessary post-incident cleanup of suppression lists to ensure no recipients were incorrectly suppressed during the outage. NOTE: As of Monday April 5th at 9PM EDT the cleanup has been completed. All recipient addresses to Apple or Apple Private Relay domains that were suppressed during Apple's incident window were removed.

We are currently investigating issues with delivery of email impacting US region.

System is fully recovered and under monitoring.

Email delivery in US is impacted, experiencing elevated delays.

System functionality has been fully restored and all emails are being transmitted correctly without added latencies; we are actively monitoring.

This incident has been resolved.

We are investigating an increase in delivery latency for some outbound messages.

We are observing recovery in email delivery performance and are actively monitoring.

This incident has been resolved.

We are currently seeing elevated temporary rejection rates for email delivered to Outlook.com, Hotmail, and other Microsoft-hosted addresses. Microsoft has acknowledged the issue and is actively investigating. This is a industry-wide issue and not isolated to any specific account. We will continue to monitor and update this page as we receive more information. Next update: When Microsoft posts a resolution or Bird observes delivery rates normalizing

Microsoft has confirmed that they made additional changes the night of Thursday, Feb 26th that should have remediated most IP rate limiting and rejection issues. If you are still seeing impacts, please reach out via your normal support channels and our team can investigate and escalate with Microsoft.

We are experiencing an elevated level of errors and latency on the Transmissions API (injection API) for some SparkPost customers. Please retry any 5xx error. Note: This issue does not impact SparkPost customers hosted in the EU.

We are continuing to investigate this issue.

We are continuing to investigate this issue. We still see 5xx errors on mail injections and degradation.

The team has identified the root cause. There is a core networking issue that has impacted sending across the clusters.

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

This incident has been resolved.

We are currently investigating this issue. No messages are lost.

The issue has been identified and a fix is being implemented.

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

This incident has been resolved.

We are currently investigating this issue.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We have begun to see improvements to outbound mail delivery delays. We anticipate full recovery in the next 30 minutes.

We continue to see strong recovery of the mail queues and message delivery. We expect all remaining delayed messages to be delivered in the next 5 minutes.

We have seen recovery. We will continue monitoring for the next 60 minutes to ensure message queues stay stable.

This incident has been resolved.