Sparkpost 中断历史

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.

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 are currently investing reported delays when sending emails towards Microsoft email domains

Impact is currently scoped to EU region only. Investigation ongoing; tickets raised to Microsoft to further investigation.

We continue to work with Microsoft on full mitigation. They are currently experiencing infrastructure issues that is causing them to incorrectly block legitimate traffic from multiple Bird IP ranges. Our sending infrastructure and email traffic are operating normally. All other mailbox providers are receiving mail without issue. Microsoft is aware of the issue and is actively investigating. We are in contact with their team and monitoring for resolution. We expect this to be resolved once Microsoft completes their fix. Messages will retry automatically - no action needed from you

Microsoft continues to investigate the issue. We are actively in contact with their team.

We continue to work with Microsoft on these delays. We are in active contact with their delivery team and working towards full resolution.

We have started to receive reports from Microsoft that they are implementing mitigations within their environment. We continue to monitor and coordinate with them for full resolution.

We continue to see some delays at Microsoft domains and are working with Microsoft to remediate. At this time, Microsoft is aware and continues to investigate.

We have seen stabilization, but are still seeing Microsoft delays in rare cases. Our team is mitigating with Microsoft as those occur. We are going to keep the status page in Monitoring state through the weekend as we continue to monitor for a full recovery at Microsoft.

We continue to see improvement with Microsoft delivery, though isolated cases of delays persist. Microsoft's mitigations are largely effective, but we're still working with their team to address edge cases as they arise. We will continue to maintain heightened monitoring through the week to ensure complete stabilization. No action is required from senders - any affected messages will continue to retry automatically.

We continue to receive reports of outages at Microsoft, as well as delayed mail sending to Microsoft and their related properties. If you are experiencing delays or IP blocks in sending to Microsoft related properties, please open a ticket with your Technical Account Manager or email support@bird.com (or your dedicated support channel if applicable). For detals around the Microsoft 365 please reference Microsoft's Status Page at: https://status.cloud.microsoft/m365

We continue to receive sporadic reports of outages at Microsoft, as well as delayed mail sending to Microsoft and their related properties. But have seen recovery for most senders. If you are experiencing delays or IP blocks in sending to Microsoft related properties, please open a ticket with your Technical Account Manager or email support@bird.com (or your dedicated support channel if applicable).

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.