Histórico de interrupções do Sparkpost

1. 27 Eost 2026 da 16:51 UTCidentified

   A partir de 2026-08-26 por volta das 23:00 UTC, estamos observando um aumento significativo de saltos rígidos para mensagens enviadas aos destinatários no privaterelay. appleid.com, o domínio relé usado pelo Sign-in com a Apple. Mensagens afetadas são rejeitadas pelos servidores de e-mail da Apple com a resposta SMTP 550 5.1.1 usuário não encontrado. A nossa investigação confirma que isto se origina a montante na caixa de correio receptora, não na nossa plataforma. Entrega para todos os outros domínios, incluindo icloud.com, me.com e mac.com, permanecem inalterados e estão atuando normalmente. Uma parte substancial dos endereços afetados entregues com sucesso tão recentemente como 2026-08-26, indicando que as rejeições não refletem destinatários genuínos inválidos. Impacto: Como estes são saltos rígidos, endereços de destinatários afetados podem ser automaticamente adicionados à sua lista de supressão, o que impedirá futuros envios para esses destinatários mesmo após o problema subjacente ser resolvido. Ação necessária: Nenhuma neste momento. Recomendamos que você não tente limpar manualmente ou re-importar entradas de supressão afetadas enquanto o problema está em curso. Estamos trabalhando diretamente com a Apple em uma resolução. Uma vez resolvido, removeremos as entradas de supressão criadas por este evento e confirmaremos o escopo e o tempo em uma atualização de seguimento. Publicaremos nossa próxima atualização dentro de 4 horas ou mais cedo se a situação mudar.

2. 27 Eost 2026 da 18:03 UTCidentified

   Nós continuamos a ver elevado 550 5.1.1 usuário não encontrou saltos rígidos do relé privado Apple. Uma vez resolvido do lado do provedor, removeremos automaticamente as entradas de supressão Apple Private Relay criadas por este evento.

3. 27 Eost 2026 da 19:10 UTCidentified

   Começamos a ver a recuperação do domínio privado do relé da Apple. Continuaremos a monitorizar os próximos 60 minutos para confirmar a recuperação total. Nossa equipe está trabalhando ativamente em remover automaticamente quaisquer supressões que foram criadas por este evento. Prevemos que a limpeza esteja concluída entre as 4 e as 6 da tarde.

4. 27 Eost 2026 da 19:28 UTCmonitoring

   Vimos a recuperação do domínio privado do relé da Apple para níveis de rejeição pré-evento. Nossa equipe está trabalhando ativamente em remover automaticamente quaisquer supressões que foram criadas por este evento. Prevemos que a limpeza seja concluída até às 18h.

5. 27 Eost 2026 da 22:56 UTCresolved

   Os níveis de rejeição da Apple mantiveram-se em níveis pré-incidentes durante a nossa fase de monitorização. A nossa limpeza das más supressões acabou. Este incidente está resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Eost 2026 da 18:52 UTCinvestigating

   Estamos investigando um aumento na latência da entrega para algumas mensagens de saída. (NOTA: Isso não afeta nossos clientes hospedados nos EUA.)

2. 19 Eost 2026 da 19:44 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 19 Eost 2026 da 19:58 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 11:14 UTCinvestigating

   Estamos investigando os problemas de entrega causados por uma interrupção contínua da região AWS West 2. Os clientes podem sofrer atrasos enquanto avaliamos o impacto no nosso serviço. Estamos monitorando ativamente a situação e forneceremos atualizações à medida que mais informações ficam disponíveis.

2. 24 Gouere 2026 da 11:53 UTCidentified

   Entrega de e-mail de saída está bloqueada para a nossa região oeste dos EUA. Estamos trabalhando com o nosso fornecedor resolver o problema. Estamos continuando a aceitar e-mails e fila-los internamente. Entregaremos as mensagens assim que o problema estiver resolvido.

3. 24 Gouere 2026 da 12:08 UTCmonitoring

   Estamos começando a entregar e-mails em nossa região oeste dos EUA. Estamos a trabalhar através das mensagens na fila. Continuamos a monitorar o problema e a aceitar e-mails.

4. 24 Gouere 2026 da 13:16 UTCmonitoring

   Ainda estamos trabalhando através das mensagens em fila de espera. Continuamos a monitorar o problema e a aceitar e-mails.

5. 24 Gouere 2026 da 17:29 UTCmonitoring

   Implementamos ajustes adicionais para lidar com o afluxo significativo de correio devido à falha da rede AWS e estamos vendo melhoria nas taxas de entrega Estamos vendo uma recuperação significativa e esperamos que a maioria do correio seja totalmente entregue nos próximos 30-35 minutos. O tempo estimado para recuperação total é de 80-90 minutos. Continuamos procurando por otimizações adicionais e monitorando o problema.

6. 24 Gouere 2026 da 18:44 UTCresolved

   This incident has been resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Mezheven 2026 da 15:58 UTCinvestigating

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

2. 29 Mezheven 2026 da 16:05 UTCmonitoring

   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. 29 Mezheven 2026 da 16:46 UTCresolved

   This incident has been resolved.

1. 12 Mae 2026 da 12:48 UTCidentified

   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. 12 Mae 2026 da 13:10 UTCmonitoring

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

3. 12 Mae 2026 da 13:38 UTCresolved

   This incident has been resolved.

1. 11 Mae 2026 da 18:55 UTCidentified

   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. 11 Mae 2026 da 19:46 UTCmonitoring

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

3. 11 Mae 2026 da 20:02 UTCresolved

   This incident has been resolved.

1. 9 Mae 2026 da 21:39 UTCinvestigating

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

2. 9 Mae 2026 da 21:50 UTCidentified

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

3. 9 Mae 2026 da 22:05 UTCmonitoring

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

4. 9 Mae 2026 da 22:17 UTCresolved

   This incident has been resolved.

1. 7 Mae 2026 da 09:31 UTCinvestigating

   We are currently investigating this issue.

2. 7 Mae 2026 da 10:49 UTCmonitoring

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

3. 8 Mae 2026 da 11:31 UTCresolved

   This incident has been resolved.

1. 5 Ebrel 2026 da 17:02 UTCinvestigating

   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. 5 Ebrel 2026 da 17:58 UTCidentified

   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. 5 Ebrel 2026 da 18:27 UTCmonitoring

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

4. 5 Ebrel 2026 da 19:01 UTCresolved

   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. 12 Meurzh 2026 da 06:51 UTCinvestigating

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

2. 12 Meurzh 2026 da 07:48 UTCmonitoring

   System is fully recovered and under monitoring.

3. 12 Meurzh 2026 da 08:00 UTCinvestigating

   Email delivery in US is impacted, experiencing elevated delays.

4. 12 Meurzh 2026 da 10:03 UTCmonitoring

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

5. 12 Meurzh 2026 da 11:25 UTCresolved

   This incident has been resolved.

1. 5 Meurzh 2026 da 00:51 UTCinvestigating

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

2. 5 Meurzh 2026 da 01:00 UTCmonitoring

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

3. 5 Meurzh 2026 da 01:24 UTCresolved

   This incident has been resolved.

1. 26 Cʼhwevrer 2026 da 17:55 UTCmonitoring

   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. 27 Cʼhwevrer 2026 da 17:38 UTCresolved

   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. 24 Cʼhwevrer 2026 da 19:07 UTCinvestigating

   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. 24 Cʼhwevrer 2026 da 19:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 Cʼhwevrer 2026 da 19:25 UTCinvestigating

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

4. 24 Cʼhwevrer 2026 da 19:34 UTCidentified

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

5. 24 Cʼhwevrer 2026 da 19:38 UTCmonitoring

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

6. 24 Cʼhwevrer 2026 da 19:41 UTCresolved

   This incident has been resolved.

1. 24 Cʼhwevrer 2026 da 15:01 UTCinvestigating

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

2. 24 Cʼhwevrer 2026 da 17:19 UTCidentified

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

3. 24 Cʼhwevrer 2026 da 17:34 UTCmonitoring

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

4. 24 Cʼhwevrer 2026 da 18:17 UTCresolved

   This incident has been resolved.

1. 20 Cʼhwevrer 2026 da 16:06 UTCinvestigating

   We are currently investigating this issue.

2. 20 Cʼhwevrer 2026 da 16:14 UTCmonitoring

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

3. 20 Cʼhwevrer 2026 da 16:15 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 20 Cʼhwevrer 2026 da 16:33 UTCresolved

   This incident has been resolved.

1. 18 Cʼhwevrer 2026 da 14:51 UTCinvestigating

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

2. 18 Cʼhwevrer 2026 da 15:02 UTCidentified

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

3. 18 Cʼhwevrer 2026 da 15:15 UTCidentified

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

4. 18 Cʼhwevrer 2026 da 15:59 UTCmonitoring

   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. 18 Cʼhwevrer 2026 da 16:15 UTCmonitoring

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

6. 18 Cʼhwevrer 2026 da 17:06 UTCresolved

   This incident has been resolved.

1. 27 Genver 2026 da 16:39 UTCidentified

   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. 27 Genver 2026 da 16:41 UTCmonitoring

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

3. 5 Cʼhwevrer 2026 da 12:22 UTCresolved

   This incident has been resolved.

1. 15 Genver 2026 da 10:24 UTCinvestigating

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

2. 15 Genver 2026 da 11:06 UTCinvestigating

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

3. 15 Genver 2026 da 11:13 UTCinvestigating

   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. 15 Genver 2026 da 11:50 UTCinvestigating

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

5. 15 Genver 2026 da 13:25 UTCidentified

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

6. 15 Genver 2026 da 13:49 UTCidentified

   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. 16 Genver 2026 da 16:03 UTCidentified

   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. 17 Genver 2026 da 23:30 UTCmonitoring

   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. 19 Genver 2026 da 18:18 UTCmonitoring

   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. 23 Genver 2026 da 05:11 UTCmonitoring

    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. 27 Genver 2026 da 16:33 UTCresolved

    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. 14 Genver 2026 da 16:27 UTCresolved

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

1. 11 Kerzu 2025 da 18:36 UTCinvestigating

   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. 11 Kerzu 2025 da 22:18 UTCmonitoring

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

3. 11 Kerzu 2025 da 22:28 UTCresolved

   This incident has been resolved.