Istoricul incidentelor Sparkpost

1. 27 august 2026 la 16:51 UTCidentified

   Începând cu 2026-08-26 în jurul orei 23:00 UTC, observăm o creștere semnificativă a salturilor dure pentru mesajele trimise beneficiarilor la privaterelay. Appleid.com, domeniul releu folosit de Sign in with Apple. Mesajele afectate sunt respinse de serverele de poștă ale Apple cu răspunsul SMTP 550 5.1.1 utilizatorul nu a fost găsit. Investigaţia noastră confirmă că acest lucru provine din amonte de la furnizorul de căsuţe poştale primitoare, nu din interiorul platformei noastre. Livrarea către toate celelalte domenii, inclusiv icloud.com, me.com și mac.com, rămâne neafectată și funcționează normal. O parte semnificativă a adreselor afectate a fost livrată cu succes în 2026-08-26, indicând faptul că respingerile nu reflectă beneficiarii cu adevărat nevalabili. Impact: Deoarece acestea sunt bounces dure, adresele destinatare afectate pot fi adăugate automat pe lista de suprimare, care va preveni trimiterea în viitor către acei destinatari chiar și după rezolvarea problemei subiacente. Acțiune necesară: Niciuna în acest moment. Vă recomandăm să nu încercați să curățați manual sau să reimportați intrările de suprimare afectate în timp ce problema este în curs de desfășurare. Lucrăm direct cu Apple la o rezoluţie. Odată rezolvate, vom elimina intrările de suprimare create de acest eveniment și vom confirma domeniul de aplicare și calendarul într-o actualizare follow-up. Vom posta următoarea actualizare în 4 ore sau mai devreme dacă situaţia se schimbă.

2. 27 august 2026 la 18:03 UTCidentified

   Noi continuăm să vedem ridicat 550 5.1.1 utilizator nu a găsit hard bounces de la Releu privat Apple. Odată rezolvate pe partea furnizorului, vom elimina automat Apple Relay intrări suprimare creat de acest eveniment.

3. 27 august 2026 la 19:10 UTCidentified

   Am început să vedem recuperarea domeniului de releu privat Apple. Vom continua monitorizarea pentru următoarele 60 de minute pentru a confirma recuperarea completă. Echipa noastră lucrează activ la eliminarea automată a oricăror suprimari care au fost create de acest eveniment. Anticipăm că curăţenia va fi terminată între 4-6 PM EDT.

4. 27 august 2026 la 19:28 UTCmonitoring

   Am văzut recuperarea domeniului Releu privat Apple la nivele de salt pre-eveniment. Echipa noastră lucrează activ la eliminarea automată a oricăror suprimari care au fost create de acest eveniment. Anticipăm curăţenia care va fi terminată la 6 PM EDT.

5. 27 august 2026 la 22:56 UTCresolved

   Nivelele de salt Apple s-au menţinut la nivelele anterioare incidentului în timpul fazei noastre de monitorizare. Curățarea noastră de suprimarea rele a terminat. Acest incident este rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 19 august 2026 la 18:52 UTCinvestigating

   Investigăm o creştere a latenţei de livrare pentru nişte mesaje depăşite. Acest lucru nu afectează clienții noștri găzduiți în SUA.)

2. 19 august 2026 la 19:44 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 19 august 2026 la 19:58 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 24 iulie 2026 la 11:14 UTCinvestigating

   Investigăm problemele de livrare cauzate de o pană de curent continuu a regiunii US West 2. Clienții pot experimenta întârzieri în timp ce noi evaluăm impactul asupra serviciului nostru. Monitorizăm în mod activ situația și vom furniza actualizări pe măsură ce devin disponibile mai multe informații.

2. 24 iulie 2026 la 11:53 UTCidentified

   Livrarea de e-mail outbound este blocat pentru regiunea noastră de Vest SUA. Lucrăm cu vânzătorul nostru rezolva problema. Continuăm să acceptăm e-mailurile şi să le stăm la coadă pe plan intern. Vom transmite mesajele imediat ce problema este rezolvată.

3. 24 iulie 2026 la 12:08 UTCmonitoring

   Începem să livrăm scrisori în regiunea noastră de Vest. Lucrăm prin mesajele cozii. Continuăm să monitorizăm problema și să continuăm să acceptăm e-mailurile.

4. 24 iulie 2026 la 13:16 UTCmonitoring

   Încă lucrăm la mesajele din coadă. Continuăm să monitorizăm problema și să continuăm să acceptăm e-mailurile.

5. 24 iulie 2026 la 17:29 UTCmonitoring

   Am implementat tuning suplimentar pentru a gestiona afluxul semnificativ de mail din cauza întreruperii rețelei AWS și vedem îmbunătățirea ratelor de livrare Vedem o recuperare semnificativă şi ne aşteptăm ca majoritatea scrisorilor să fie livrate complet în următoarele 30-35 de minute. Timpul estimat pentru recuperarea completă este de 80-90 minute. Continuăm să căutăm optimizări suplimentare și să monitorizăm problema.

6. 24 iulie 2026 la 18:44 UTCresolved

   This incident has been resolved.

Traducere automată din actualizarea oficială a incidentului.

1. 29 iunie 2026 la 15:58 UTCinvestigating

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

2. 29 iunie 2026 la 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 iunie 2026 la 16:46 UTCresolved

   This incident has been resolved.

1. 12 mai 2026 la 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 mai 2026 la 13:10 UTCmonitoring

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

3. 12 mai 2026 la 13:38 UTCresolved

   This incident has been resolved.

1. 11 mai 2026 la 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 mai 2026 la 19:46 UTCmonitoring

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

3. 11 mai 2026 la 20:02 UTCresolved

   This incident has been resolved.

1. 9 mai 2026 la 21:39 UTCinvestigating

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

2. 9 mai 2026 la 21:50 UTCidentified

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

3. 9 mai 2026 la 22:05 UTCmonitoring

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

4. 9 mai 2026 la 22:17 UTCresolved

   This incident has been resolved.

1. 7 mai 2026 la 09:31 UTCinvestigating

   We are currently investigating this issue.

2. 7 mai 2026 la 10:49 UTCmonitoring

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

3. 8 mai 2026 la 11:31 UTCresolved

   This incident has been resolved.

1. 5 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 18:27 UTCmonitoring

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

4. 5 aprilie 2026 la 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 martie 2026 la 06:51 UTCinvestigating

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

2. 12 martie 2026 la 07:48 UTCmonitoring

   System is fully recovered and under monitoring.

3. 12 martie 2026 la 08:00 UTCinvestigating

   Email delivery in US is impacted, experiencing elevated delays.

4. 12 martie 2026 la 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 martie 2026 la 11:25 UTCresolved

   This incident has been resolved.

1. 5 martie 2026 la 00:51 UTCinvestigating

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

2. 5 martie 2026 la 01:00 UTCmonitoring

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

3. 5 martie 2026 la 01:24 UTCresolved

   This incident has been resolved.

1. 26 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 19:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 februarie 2026 la 19:25 UTCinvestigating

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

4. 24 februarie 2026 la 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 februarie 2026 la 19:38 UTCmonitoring

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

6. 24 februarie 2026 la 19:41 UTCresolved

   This incident has been resolved.

1. 24 februarie 2026 la 15:01 UTCinvestigating

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

2. 24 februarie 2026 la 17:19 UTCidentified

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

3. 24 februarie 2026 la 17:34 UTCmonitoring

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

4. 24 februarie 2026 la 18:17 UTCresolved

   This incident has been resolved.

1. 20 februarie 2026 la 16:06 UTCinvestigating

   We are currently investigating this issue.

2. 20 februarie 2026 la 16:14 UTCmonitoring

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

3. 20 februarie 2026 la 16:15 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 20 februarie 2026 la 16:33 UTCresolved

   This incident has been resolved.

1. 18 februarie 2026 la 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 februarie 2026 la 15:02 UTCidentified

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

3. 18 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 16:15 UTCmonitoring

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

6. 18 februarie 2026 la 17:06 UTCresolved

   This incident has been resolved.

1. 27 ianuarie 2026 la 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 ianuarie 2026 la 16:41 UTCmonitoring

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

3. 5 februarie 2026 la 12:22 UTCresolved

   This incident has been resolved.

1. 15 ianuarie 2026 la 10:24 UTCinvestigating

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

2. 15 ianuarie 2026 la 11:06 UTCinvestigating

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

3. 15 ianuarie 2026 la 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 ianuarie 2026 la 11:50 UTCinvestigating

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

5. 15 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 decembrie 2025 la 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 decembrie 2025 la 22:18 UTCmonitoring

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

3. 11 decembrie 2025 la 22:28 UTCresolved

   This incident has been resolved.