Sparkpost 中断历史

1. 2026年8月27日 UTC 16:51identified

   从2026-08-26 UTC凌晨23:00左右开始,我们观测到,通过私人转播发送给收件人的信息的硬反弹明显增加。 appid.com,Sign与苹果公司一起使用的接力域. 受影响消息被苹果的邮件服务器拒绝,SMTP响应550 5.1.1用户未找到. 我们的调查证实,这起源于接收信箱供应商的上游,而不是我们的平台。 交付到包括icloud. 最近于2026-08-26年成功发送了很大一部分受影响的地址,表明拒绝并不反映真正的无效接收者。 效果:由于这些是硬反弹,受影响的收件人地址可能会被自动添加到您的压制列表中,这将防止未来即使在根本问题解决后发送给这些收件人. 需要采取的行动:目前无。 我们建议您不要试图在问题持续期间手动清理或再进口受影响的抑制条目。 我们正在直接与苹果公司合作 研究一个解决方案。 一旦解决,我们将删除这一事件产生的压制条目,并在后续更新中确认范围和时间。 我们将在4小时内发布下一次更新,如果情况发生变化,则会提前发布.

2. 2026年8月27日 UTC 18:03identified

   我们继续看到提升550 5.1.1 用户没有从苹果私人中继找到硬反弹。 一旦在提供商一方解决,我们将自动去除由此事件所创建的Apple Private Relay President 条目.

3. 2026年8月27日 UTC 19:10identified

   我们已经开始看到苹果私人中继域的恢复. 我们将继续监测60分钟以证实全面恢复。 我们的小组正在积极努力,自动消除这一事件造成的任何压制。 我们预计清理工作将在4-6PM EDT之间完成.

4. 2026年8月27日 UTC 19:28monitoring

   我们看到苹果的私人中继域恢复到事前回弹的水平. 我们的小组正在积极努力,自动消除这一事件造成的任何压制。 我们预计清理工作将由6PM EDT完成.

5. 2026年8月27日 UTC 22:56resolved

   在我们的监测阶段,苹果弹跳水平保持在事发前的水平。 我们清除了不良的压制 已经结束。 此事已决.

自动翻译自官方事件更新。

1. 2026年8月19日 UTC 18:52investigating

   我们正在调查一些外出信息交付延迟增加的情况。 (注:这并不影响我们在美国的客户。 )

2. 2026年8月19日 UTC 19:44monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年8月19日 UTC 19:58resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月24日 UTC 11:14investigating

   我们正在调查AWS美国西部2区持续停运造成的运送问题。 在我们评估对服务的影响时,客户可能会遇到延误。 我们正在积极监测局势,并将在获得更多信息后提供最新情况.

2. 2026年7月24日 UTC 11:53identified

   外出邮件发送被封锁, 我们与我们的供应商合作解决这个问题。 我们继续接受电子邮件, 一旦问题得到解决,我们将立即传达信息.

3. 2026年7月24日 UTC 12:08monitoring

   我们开始在美国西部地区发送邮件。 我们正在通过排队的信息。 我们正在继续监测这一问题并继续接受电子邮件.

4. 2026年7月24日 UTC 13:16monitoring

   我们还在通过排队的信息。 我们正在继续监测这一问题并继续接受电子邮件.

5. 2026年7月24日 UTC 17:29monitoring

   我们进行了更多的调整,以处理由于AWS网络中断而大量涌入的邮件,我们看到交货率有所提高 我们正看到重大恢复,并期望大多数邮件在今后30至35分钟内全部交付。 估计完全恢复的时间为80-90分钟. 我们正在继续寻求进一步优化和监测这一问题.

6. 2026年7月24日 UTC 18:44resolved

   This incident has been resolved.

自动翻译自官方事件更新。

1. 2026年6月29日 UTC 15:58investigating

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

2. 2026年6月29日 UTC 16:05monitoring

   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.

3. 2026年6月29日 UTC 16:46resolved

   This incident has been resolved.

1. 2026年5月12日 UTC 12:48identified

   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.

2. 2026年5月12日 UTC 13:10monitoring

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

3. 2026年5月12日 UTC 13:38resolved

   This incident has been resolved.

1. 2026年5月11日 UTC 18:55identified

   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.

2. 2026年5月11日 UTC 19:46monitoring

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

3. 2026年5月11日 UTC 20:02resolved

   This incident has been resolved.

1. 2026年5月9日 UTC 21:39investigating

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

2. 2026年5月9日 UTC 21:50identified

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

3. 2026年5月9日 UTC 22:05monitoring

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

4. 2026年5月9日 UTC 22:17resolved

   This incident has been resolved.

1. 2026年5月7日 UTC 09:31investigating

   We are currently investigating this issue.

2. 2026年5月7日 UTC 10:49monitoring

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

3. 2026年5月8日 UTC 11:31resolved

   This incident has been resolved.

1. 2026年4月5日 UTC 17:02investigating

   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.

2. 2026年4月5日 UTC 17:58identified

   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.

3. 2026年4月5日 UTC 18:27monitoring

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

4. 2026年4月5日 UTC 19:01resolved

   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.

1. 2026年3月12日 UTC 06:51investigating

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

2. 2026年3月12日 UTC 07:48monitoring

   System is fully recovered and under monitoring.

3. 2026年3月12日 UTC 08:00investigating

   Email delivery in US is impacted, experiencing elevated delays.

4. 2026年3月12日 UTC 10:03monitoring

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

5. 2026年3月12日 UTC 11:25resolved

   This incident has been resolved.

1. 2026年3月5日 UTC 00:51investigating

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

2. 2026年3月5日 UTC 01:00monitoring

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

3. 2026年3月5日 UTC 01:24resolved

   This incident has been resolved.

1. 2026年2月26日 UTC 17:55monitoring

   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

2. 2026年2月27日 UTC 17:38resolved

   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.

1. 2026年2月24日 UTC 19:07investigating

   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.

2. 2026年2月24日 UTC 19:07investigating

   We are continuing to investigate this issue.

3. 2026年2月24日 UTC 19:25investigating

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

4. 2026年2月24日 UTC 19:34identified

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

5. 2026年2月24日 UTC 19:38monitoring

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

6. 2026年2月24日 UTC 19:41resolved

   This incident has been resolved.

1. 2026年2月24日 UTC 15:01investigating

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

2. 2026年2月24日 UTC 17:19identified

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

3. 2026年2月24日 UTC 17:34monitoring

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

4. 2026年2月24日 UTC 18:17resolved

   This incident has been resolved.

1. 2026年2月20日 UTC 16:06investigating

   We are currently investigating this issue.

2. 2026年2月20日 UTC 16:14monitoring

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

3. 2026年2月20日 UTC 16:15monitoring

   We are continuing to monitor for any further issues.

4. 2026年2月20日 UTC 16:33resolved

   This incident has been resolved.

1. 2026年2月18日 UTC 14:51investigating

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

2. 2026年2月18日 UTC 15:02identified

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

3. 2026年2月18日 UTC 15:15identified

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

4. 2026年2月18日 UTC 15:59monitoring

   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.

5. 2026年2月18日 UTC 16:15monitoring

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

6. 2026年2月18日 UTC 17:06resolved

   This incident has been resolved.

1. 2026年1月27日 UTC 16:39identified

   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.

2. 2026年1月27日 UTC 16:41monitoring

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

3. 2026年2月5日 UTC 12:22resolved

   This incident has been resolved.

1. 2026年1月15日 UTC 10:24investigating

   We are currently investing reported delays when sending emails towards Microsoft email domains

2. 2026年1月15日 UTC 11:06investigating

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

3. 2026年1月15日 UTC 11:13investigating

   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

4. 2026年1月15日 UTC 11:50investigating

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

5. 2026年1月15日 UTC 13:25identified

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

6. 2026年1月15日 UTC 13:49identified

   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.

7. 2026年1月16日 UTC 16:03identified

   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.

8. 2026年1月17日 UTC 23:30monitoring

   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.

9. 2026年1月19日 UTC 18:18monitoring

   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.

10. 2026年1月23日 UTC 05:11monitoring

    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 [email protected] (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

11. 2026年1月27日 UTC 16:33resolved

    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 [email protected] (or your dedicated support channel if applicable).

1. 2026年1月14日 UTC 16:27resolved

   We've experienced processing delays of up to 1h30min for sending emails to yahoo.com domain in the EU and US regions.

1. 2025年12月11日 UTC 18:36investigating

   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.

2. 2025年12月11日 UTC 22:18monitoring

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

3. 2025年12月11日 UTC 22:28resolved

   This incident has been resolved.