Sparkpost driftsforstyrrelser

1. 27. august 2026 kl. 16.51 UTCidentified

   Begyndelsen 2026-08-26 omkring 23: 00 UTC, vi observerer en betydelig stigning i hårde hoppesteder for meddelelser sendt til modtagere på privatrelæ. appleid.com, relædomænet brugt af Log ind med Apple. Berørte meddelelser afvises af Apples mail servere med SMTP svar 550 5.1.1 bruger ikke fundet. Vores undersøgelse bekræfter dette stammer opstrøms på den modtagende postkasse udbyder, ikke inden for vores platform. Levering til alle andre domæner, herunder ichalat.com, me.com og mac.com, forbliver upåvirket og udfører normalt. En betydelig del af de berørte adresser leveret med succes så sent som 2026- 08- 26, angiver afslag ikke afspejler ægte ugyldige modtagere. Impact: Fordi disse er hårde bounces, berørte modtager adresser kan automatisk tilføjes til din undertrykkelse liste, som vil forhindre fremtiden sender til disse modtagere, selv efter at det underliggende problem er løst. Påkrævet handling: Ingen på nuværende tidspunkt. Vi anbefaler, at du ikke forsøger at manuelt rense eller re- import berørte undertrykkelse poster, mens problemet er i gang. Vi arbejder direkte med Apple om en beslutning. Når løst, vil vi fjerne undertrykkelse indgange skabt af denne begivenhed og vil bekræfte omfanget og timing i en opfølgning opdatering. Vi vil sende vores næste opdatering inden for 4 timer eller før, hvis situationen ændrer sig.

2. 27. august 2026 kl. 18.03 UTCidentified

   Vi fortsætter med at se forhøjet 550 5.1.1 bruger ikke fundet hårde hopper fra Apple private relæ. Når det er løst på udbyderens side, vil vi automatisk fjerne Apple Private Relay undertrykkelse poster skabt af denne begivenhed.

3. 27. august 2026 kl. 19.10 UTCidentified

   Vi er begyndt at se inddrivelse af Apple private relæ domæne. Vi vil fortsætte overvågningen i de næste 60 minutter for at bekræfte fuld bedring. Vores team arbejder aktivt på automatisk at fjerne enhver undertrykkelse, der blev skabt af denne begivenhed. Vi forventer, at oprydningen bliver afsluttet mellem kl. 16.00.

4. 27. august 2026 kl. 19.28 UTCmonitoring

   Vi har set inddrivelse af Apple private relæ domæne til pre-event bounce niveauer. Vores team arbejder aktivt på automatisk at fjerne enhver undertrykkelse, der blev skabt af denne begivenhed. Vi forventer, at oprydningen afsluttes kl. 18.00.

5. 27. august 2026 kl. 22.56 UTCresolved

   Apple bounce niveauer har opretholdt på præ hændelse niveauer i vores overvågning fase. Vores oprydning af de dårlige depressioner er slut. Denne hændelse er løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 19. august 2026 kl. 18.52 UTCinvestigating

   Vi undersøger en stigning i leveringsforsinkelse for nogle udgående beskeder. (BEMÆRK: Dette påvirker ikke vores kunder hostet i USA.)

2. 19. august 2026 kl. 19.44 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 19. august 2026 kl. 19.58 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 11.14 UTCinvestigating

   Vi undersøger leveringsproblemer forårsaget af en igangværende AWS US West 2 region afbrydelse. Kunderne kan opleve forsinkelser, mens vi vurderer virkningen på vores service. Vi overvåger situationen aktivt og vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 24. juli 2026 kl. 11.53 UTCidentified

   Udgående e-mail levering er blokeret for vores US West region. Vi arbejder med vores leverandør løse problemet. Vi fortsætter med at acceptere e-mails og kø dem internt. Vi vil levere meddelelserne, så snart problemet er løst.

3. 24. juli 2026 kl. 12.08 UTCmonitoring

   Vi begynder at levere mails i vores US West region. Vi arbejder gennem beskeder i køen. Vi overvåger fortsat spørgsmålet og accepterer fortsat e-mails.

4. 24. juli 2026 kl. 13.16 UTCmonitoring

   Vi arbejder stadig med beskeder i kø. Vi overvåger fortsat spørgsmålet og accepterer fortsat e-mails.

5. 24. juli 2026 kl. 17.29 UTCmonitoring

   Vi har gennemført yderligere tuning for at håndtere den betydelige tilstrømning af post på grund af AWS netværk afbrydelse, og vi ser forbedringer i leveringsrater Vi ser en betydelig bedring og forventer, at de fleste mail vil blive leveret fuldt ud i de næste 30-35 minutter. Anslået tid til fuld helbredelse er 80- 90 minutter. Vi fortsætter med at lede efter yderligere optimeringer og overvåge problemet.

6. 24. juli 2026 kl. 18.44 UTCresolved

   This incident has been resolved.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 29. juni 2026 kl. 15.58 UTCinvestigating

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

2. 29. juni 2026 kl. 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. juni 2026 kl. 16.46 UTCresolved

   This incident has been resolved.

1. 12. maj 2026 kl. 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. maj 2026 kl. 13.10 UTCmonitoring

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

3. 12. maj 2026 kl. 13.38 UTCresolved

   This incident has been resolved.

1. 11. maj 2026 kl. 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. maj 2026 kl. 19.46 UTCmonitoring

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

3. 11. maj 2026 kl. 20.02 UTCresolved

   This incident has been resolved.

1. 9. maj 2026 kl. 21.39 UTCinvestigating

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

2. 9. maj 2026 kl. 21.50 UTCidentified

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

3. 9. maj 2026 kl. 22.05 UTCmonitoring

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

4. 9. maj 2026 kl. 22.17 UTCresolved

   This incident has been resolved.

1. 7. maj 2026 kl. 09.31 UTCinvestigating

   We are currently investigating this issue.

2. 7. maj 2026 kl. 10.49 UTCmonitoring

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

3. 8. maj 2026 kl. 11.31 UTCresolved

   This incident has been resolved.

1. 5. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 18.27 UTCmonitoring

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

4. 5. april 2026 kl. 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. marts 2026 kl. 06.51 UTCinvestigating

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

2. 12. marts 2026 kl. 07.48 UTCmonitoring

   System is fully recovered and under monitoring.

3. 12. marts 2026 kl. 08.00 UTCinvestigating

   Email delivery in US is impacted, experiencing elevated delays.

4. 12. marts 2026 kl. 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. marts 2026 kl. 11.25 UTCresolved

   This incident has been resolved.

1. 5. marts 2026 kl. 00.51 UTCinvestigating

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

2. 5. marts 2026 kl. 01.00 UTCmonitoring

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

3. 5. marts 2026 kl. 01.24 UTCresolved

   This incident has been resolved.

1. 26. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 19.07 UTCinvestigating

   We are continuing to investigate this issue.

3. 24. februar 2026 kl. 19.25 UTCinvestigating

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

4. 24. februar 2026 kl. 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. februar 2026 kl. 19.38 UTCmonitoring

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

6. 24. februar 2026 kl. 19.41 UTCresolved

   This incident has been resolved.

1. 24. februar 2026 kl. 15.01 UTCinvestigating

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

2. 24. februar 2026 kl. 17.19 UTCidentified

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

3. 24. februar 2026 kl. 17.34 UTCmonitoring

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

4. 24. februar 2026 kl. 18.17 UTCresolved

   This incident has been resolved.

1. 20. februar 2026 kl. 16.06 UTCinvestigating

   We are currently investigating this issue.

2. 20. februar 2026 kl. 16.14 UTCmonitoring

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

3. 20. februar 2026 kl. 16.15 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 20. februar 2026 kl. 16.33 UTCresolved

   This incident has been resolved.

1. 18. februar 2026 kl. 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. februar 2026 kl. 15.02 UTCidentified

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

3. 18. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 16.15 UTCmonitoring

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

6. 18. februar 2026 kl. 17.06 UTCresolved

   This incident has been resolved.

1. 27. januar 2026 kl. 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. januar 2026 kl. 16.41 UTCmonitoring

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

3. 5. februar 2026 kl. 12.22 UTCresolved

   This incident has been resolved.

1. 15. januar 2026 kl. 10.24 UTCinvestigating

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

2. 15. januar 2026 kl. 11.06 UTCinvestigating

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

3. 15. januar 2026 kl. 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. januar 2026 kl. 11.50 UTCinvestigating

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

5. 15. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. december 2025 kl. 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. december 2025 kl. 22.18 UTCmonitoring

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

3. 11. december 2025 kl. 22.28 UTCresolved

   This incident has been resolved.