SparkPost had 29 outages in the last 2 years totaling 594h 17m of downtime — averaging 1.2 incidents per month.
There were 29 SparkPost outages since May 18, 2025 totaling 594h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 have identified an issue affecting Single Sign-On (SSO) logins. Users authenticating via SSO are unable to access their accounts. A fix has been deployed and we expect the issue to be resolved within the next few minutes. We apologize for the inconvenience and will provide an update shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We've experienced processing delays of up to 1h30min for sending emails to yahoo.com domain in the EU and US regions.
There is a delay in our events pipeline. This is causing metrics, events and webhooks to be delayed for a portion of data. Message sending is not effected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Messages that have failed initial delivery and are in a delayed state are taking longer than expected to resend. Only messages injected via SMTP and in a delayed state are effected.
The issue has been identified and the fix has been deployed.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently looking into a data delay. This is causing our metrics to be delayed. It is not effecting mail sending.
Our pipeline that was having issue has recovered. We are monitoring to ensure we stay in a good state. Very sorry for the inconvenience.
This incident has been resolved.
We are looking into increased error rates and high latency across our APIs. This could be related to a third party outage.
One of our third party providers is experiencing increased latency. This is causing a very small amount of the traffic hitting our APIs to error or have high latency. We are monitoring to ensure the latency and error rates don't increase while waiting for their team to resolve the issue.
This incident has been resolved.
Our data processing services are running behind; some customers may see a delay of data available via the: - SparkPost App (webUI): Signals Reports - Events API - Metrics API Message injection and outbound message delivery are not impacted - all messages are flowing as expected.
The issue has been identified and a fix is being implemented.
We have been able to catch up all data from the 5th and are working on the 6th now.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Our data processing services are running behind; some customers may see a delay of data available via the: - SparkPost App (webUI): Signals Reports - Events API - Metrics API Message injection and outbound message delivery are not impacted - all messages are flowing as expected.
The issue has been identified and a fix is being implemented.
Metrics API is fully caught up. We are continuing work to restore full data availability in the UI.
The incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident was resolved.
We are currently investigating this issue.
A mitigation was deployed and the error rate is subsiding
We have identified the issue and deployed a mitigation; all service functionality has been completely restored.
We are continuing to investigate this issue.
This incident has been resolved.
Our webhook data delivery services are running behind and some customers may see a delay in data streamed to their webhook endpoints. Message injection and outbound message delivery is not impacted - all messages are flowing as expected. Note: This issue does not impact our SparkPost customers hosted in the EU.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This issue has been resolved. We apologize for any inconvenience it may have cause.
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.
This incident impacted a limited batch of messages injected via SMTP API. We have quarantined the impacted the node and working on delivering the messages and isolating the root cause. The SMTP API is full operational
We are investigating an slight 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.