Historial de interrupciones de Sparkpost

1. August 27, 2026 at 4:51 PM UTCidentified

   A partir de 2026-08-26 alrededor de las 23:00 UTC, estamos observando un aumento significativo en los rebotes duros para los mensajes enviados a los destinatarios en privaterelay. appleid.com, el dominio relé utilizado por Inicia sesión con Apple. Los mensajes afectados son rechazados por los servidores de correo de Apple con la respuesta SMTP 550 5.1.1 usuario no encontrado. Nuestra investigación confirma que esto se origina en el proveedor de correos recibidos, no dentro de nuestra plataforma. La entrega a todos los demás dominios, incluyendo icloud.com, me.com y mac.com, no se ve afectada y se realiza normalmente. Una parte sustancial de las direcciones afectadas entregadas con éxito tan recientemente como 2026-08-26, indicando que los rechazos no reflejan verdaderos receptores inválidos. Impacto: Debido a que estos son rebotes duros, las direcciones receptoras afectadas se pueden agregar automáticamente a su lista de supresión, lo que impedirá que los futuros enviados a aquellos receptores incluso después de que se resuelva el problema subyacente. Acción requerida: Ninguna en este momento. Le recomendamos que no trate de limpiar manualmente o reimportar entradas de supresión afectadas mientras el problema está en curso. Trabajamos directamente con Apple en una resolución. Una vez resuelto, eliminaremos las entradas de supresión creadas por este evento y confirmaremos el alcance y el tiempo en una actualización de seguimiento. Publicaremos nuestra próxima actualización dentro de 4 horas o antes si la situación cambia.

2. August 27, 2026 at 6:03 PM UTCidentified

   Seguimos viendo elevado 550 5.1.1 usuario no encontró rebotes duros del relé privado de Apple. Una vez resuelto en el lado del proveedor, eliminaremos automáticamente las entradas de supresión de relé privado de Apple creadas por este evento.

3. August 27, 2026 at 7:10 PM UTCidentified

   Hemos empezado a ver la recuperación del dominio de relé privado de Apple. Continuaremos monitoreando durante los próximos 60 minutos para confirmar la recuperación completa. Nuestro equipo está trabajando activamente en la eliminación automática de las supresiones creadas por este evento. Prevemos que la limpieza se complete entre 4-6PM EDT.

4. August 27, 2026 at 7:28 PM UTCmonitoring

   Hemos visto la recuperación del dominio de relé privado de Apple a niveles de rebote pre-evento. Nuestro equipo está trabajando activamente en la eliminación automática de las supresiones creadas por este evento. Esperamos que la limpieza sea completada por 6PM EDT.

5. August 27, 2026 at 10:56 PM UTCresolved

   Los niveles de rebote de Apple se han mantenido en niveles previos a incidentes durante nuestra fase de monitoreo. Nuestra limpieza de las malas supresiones ha terminado. Este incidente está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 19, 2026 at 6:52 PM UTCinvestigating

   Estamos investigando un aumento de latencia de entrega para algunos mensajes externos. (NOTA: Esto no impacta a nuestros clientes hospedados en Estados Unidos.)

2. August 19, 2026 at 7:44 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. August 19, 2026 at 7:58 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 11:14 AM UTCinvestigating

   Estamos investigando los problemas de entrega causados por un desembolso de la región AWS US West 2. Los clientes pueden experimentar retrasos mientras evaluamos el impacto a nuestro servicio. Estamos monitoreando activamente la situación y proporcionaremos actualizaciones a medida que se disponga de más información.

2. July 24, 2026 at 11:53 AM UTCidentified

   La entrega de correo electrónico está bloqueada para nuestra región del Oeste de Estados Unidos. Trabajamos con nuestro proveedor para resolver el problema. Seguimos aceptando correos electrónicos y colarlos internamente. Entregaremos los mensajes tan pronto como se resuelva el problema.

3. July 24, 2026 at 12:08 PM UTCmonitoring

   Estamos empezando a entregar correos en nuestra región del Oeste de Estados Unidos. Estamos trabajando a través de los mensajes apagados. Continuamos monitoreando el problema y continuamos aceptando correos electrónicos.

4. July 24, 2026 at 1:16 PM UTCmonitoring

   Todavía estamos trabajando a través de los mensajes apagados. Continuamos monitoreando el problema y continuamos aceptando correos electrónicos.

5. July 24, 2026 at 5:29 PM UTCmonitoring

   Hemos implementado afinación adicional para manejar la significativa afluencia de correo debido a la salida de red AWS y estamos viendo mejoras en las tasas de entrega Estamos viendo una recuperación significativa y esperamos que la mayoría del correo sea entregado por completo en los próximos 30-35 minutos. El tiempo estimado para la recuperación completa es de 80-90 minutos. Continuamos buscando optimizaciones adicionales y monitoreamos el problema.

6. July 24, 2026 at 6:44 PM UTCresolved

   This incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 29, 2026 at 3:58 PM UTCinvestigating

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

2. June 29, 2026 at 4:05 PM 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. June 29, 2026 at 4:46 PM UTCresolved

   This incident has been resolved.

1. May 12, 2026 at 12:48 PM 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. May 12, 2026 at 1:10 PM UTCmonitoring

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

3. May 12, 2026 at 1:38 PM UTCresolved

   This incident has been resolved.

1. May 11, 2026 at 6:55 PM 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. May 11, 2026 at 7:46 PM UTCmonitoring

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

3. May 11, 2026 at 8:02 PM UTCresolved

   This incident has been resolved.

1. May 9, 2026 at 9:39 PM UTCinvestigating

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

2. May 9, 2026 at 9:50 PM UTCidentified

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

3. May 9, 2026 at 10:05 PM UTCmonitoring

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

4. May 9, 2026 at 10:17 PM UTCresolved

   This incident has been resolved.

1. May 7, 2026 at 9:31 AM UTCinvestigating

   We are currently investigating this issue.

2. May 7, 2026 at 10:49 AM UTCmonitoring

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

3. May 8, 2026 at 11:31 AM UTCresolved

   This incident has been resolved.

1. April 5, 2026 at 5:02 PM 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. April 5, 2026 at 5:58 PM 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. April 5, 2026 at 6:27 PM UTCmonitoring

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

4. April 5, 2026 at 7:01 PM 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. March 12, 2026 at 6:51 AM UTCinvestigating

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

2. March 12, 2026 at 7:48 AM UTCmonitoring

   System is fully recovered and under monitoring.

3. March 12, 2026 at 8:00 AM UTCinvestigating

   Email delivery in US is impacted, experiencing elevated delays.

4. March 12, 2026 at 10:03 AM UTCmonitoring

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

5. March 12, 2026 at 11:25 AM UTCresolved

   This incident has been resolved.

1. March 5, 2026 at 12:51 AM UTCinvestigating

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

2. March 5, 2026 at 1:00 AM UTCmonitoring

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

3. March 5, 2026 at 1:24 AM UTCresolved

   This incident has been resolved.

1. February 26, 2026 at 5:55 PM 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. February 27, 2026 at 5:38 PM 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. February 24, 2026 at 7:07 PM 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. February 24, 2026 at 7:07 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 24, 2026 at 7:25 PM UTCinvestigating

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

4. February 24, 2026 at 7:34 PM UTCidentified

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

5. February 24, 2026 at 7:38 PM UTCmonitoring

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

6. February 24, 2026 at 7:41 PM UTCresolved

   This incident has been resolved.

1. February 24, 2026 at 3:01 PM UTCinvestigating

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

2. February 24, 2026 at 5:19 PM UTCidentified

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

3. February 24, 2026 at 5:34 PM UTCmonitoring

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

4. February 24, 2026 at 6:17 PM UTCresolved

   This incident has been resolved.

1. February 20, 2026 at 4:06 PM UTCinvestigating

   We are currently investigating this issue.

2. February 20, 2026 at 4:14 PM UTCmonitoring

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

3. February 20, 2026 at 4:15 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. February 20, 2026 at 4:33 PM UTCresolved

   This incident has been resolved.

1. February 18, 2026 at 2:51 PM 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. February 18, 2026 at 3:02 PM UTCidentified

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

3. February 18, 2026 at 3:15 PM UTCidentified

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

4. February 18, 2026 at 3:59 PM 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. February 18, 2026 at 4:15 PM UTCmonitoring

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

6. February 18, 2026 at 5:06 PM UTCresolved

   This incident has been resolved.

1. January 27, 2026 at 4:39 PM 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. January 27, 2026 at 4:41 PM UTCmonitoring

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

3. February 5, 2026 at 12:22 PM UTCresolved

   This incident has been resolved.

1. January 15, 2026 at 10:24 AM UTCinvestigating

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

2. January 15, 2026 at 11:06 AM UTCinvestigating

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

3. January 15, 2026 at 11:13 AM 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. January 15, 2026 at 11:50 AM UTCinvestigating

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

5. January 15, 2026 at 1:25 PM 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. January 15, 2026 at 1:49 PM 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. January 16, 2026 at 4:03 PM 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. January 17, 2026 at 11:30 PM 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. January 19, 2026 at 6:18 PM 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. January 23, 2026 at 5:11 AM 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. January 27, 2026 at 4:33 PM 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. January 14, 2026 at 4:27 PM UTCresolved

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

1. December 11, 2025 at 6:36 PM 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. December 11, 2025 at 10:18 PM UTCmonitoring

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

3. December 11, 2025 at 10:28 PM UTCresolved

   This incident has been resolved.