Paubox driftsforstyrrelser

1. 21. oktober 2026 kl. 15.36 UTCinvestigating

   Vi undersøger et spørgsmål, hvor MFA-koder ikke modtages.

2. 21. oktober 2026 kl. 15.52 UTCidentified

   Vi har identificeret problemet og arbejder på et fix. Både TOTP (autentificeringsapps) og adgangstast muligheder er funktionelle som vi forfølger dette.

3. 21. oktober 2026 kl. 16.26 UTCresolved

   Omkring 133 koder sad fast i vores interne køer - de er blevet frigivet, og MFA-tjenesten fungerer nu som forventet. Bagenden bliver omskrevet i dette kvartal for at sikre, at problemet ikke kan gentage sig.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. september 2026 kl. 21.17 UTCmonitoring

   Nogle Outbound og Marketing kunder kan se ufuldstændige eller manglende oplysninger i Mail Log og Paubox Marketing områder af instrumentbrættet, og Marketing sider kan være langsom til at indlæse eller time ud. Email levering er ikke påvirket. Meddelelser sendes, modtages, filtreres og krypteres normalt hele vejen igennem. Ingen kundedata er gået tabt - dette påvirker kun, hvordan seneste aktivitet vises. Vi har identificeret årsagen til problemet med mailloggen og har et fix på plads. Vi undersøger stadig marketingspørgsmålet. Vi vil opdatere denne side som vi har mere.

2. 22. september 2026 kl. 00.23 UTCresolved

   Display problemer med udgående e-mail og marketing er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. august 2026 kl. 19.36 UTCidentified

   We have identified an issue blocking log in to our admin app and should have a fix in place shortly.

2. 14. august 2026 kl. 19.48 UTCmonitoring

   A fix has been implemented and we are monitoring the results - log in is confirmed functional again.

3. 14. august 2026 kl. 20.06 UTCresolved

   The incident has been resolved.

1. 22. juli 2026 kl. 20.08 UTCinvestigating

   Vi er ved at undersøge rapporter fra nogle Inbound Security kunder, at deres Inbound karantæne er tomme på trods af mail bliver markeret som karantæne i deres mail logs.

2. 22. juli 2026 kl. 21.06 UTCresolved

   Ingen fejl blev identificeret, ingen ændringer blev afsendt. To grunde til, at kunderne kan være stødt på dette: 1) Paubox er forsendelse forbedringer næsten dagligt - hvis noget er pludselig utilgængelig, kan du nødt til at logge ud / tilbage for at opdatere din adgang 2) For at den indgående karantæne kan vise resultater, skal der vælges "alle kategorier" eller mindst én kategori. Hvis ingen kategorier er valgt, viser siden ingen resultater.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 19.07 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 8. juli 2026 kl. 19.22 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 25. juni 2026 kl. 15.23 UTCidentified

   Kunderne rapporterer om, at karantænefrigivelse er ikke funktionel - et fix er i gang.

2. 25. juni 2026 kl. 17.11 UTCmonitoring

   Der er et fix på plads, og vi overvåger resultaterne.

3. 25. juni 2026 kl. 18.04 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. juni 2026 kl. 16.33 UTCidentified

   Beginning at 6AM UTC today, Microsoft began presenting an updated certificate on some of their hosted mail accounts, and our outbound servers' list of trusted authorities doesn't yet include the new one. As a result, a portion of outbound emails to recipients hosted on Microsoft 365 are currently being routed through the Paubox Secure Message Center instead of delivered directly to the recipient's inbox. Affected recipients receive a notification with a secure link to view the message in our portal. No emails have been lost and no data security has been compromised — the Secure Message Center fallback is operating as designed to protect message content when direct delivery cannot be verified. We are updating the certificate and should have a resolution shortly.

2. 17. juni 2026 kl. 17.00 UTCmonitoring

   We are rolling out a new cert server by server and monitoring.

3. 17. juni 2026 kl. 18.20 UTCresolved

   Direct delivery to Microsoft 365 recipients has been restored. Messages sent during the incident were delivered securely via the Paubox Secure Message Center; no mail was lost. Thank you for your patience.

1. 12. maj 2026 kl. 19.52 UTCmonitoring

   Some customers using our hosted/webmail reported certificate issues blocking access on mobile devices. We have refreshed our certificates again - if you are still seeing an error, please clear your cookies and cache. If this does not resolve your issue, take a screenshot and email [email protected] so we can isolate your specific issue.

2. 13. maj 2026 kl. 23.02 UTCresolved

   This incident has been resolved.

1. 8. april 2026 kl. 15.32 UTCmonitoring

   We have had a few calls from some Google Workspace customers report inbound & outbound delays on internal emails which Down Dectector corroborates - see https://downdetector.com/status/gmail/ - we will continue to monitor this.

2. 8. april 2026 kl. 17.56 UTCmonitoring

   Google has updated this site with more details: https://support.cloud.google.com/portal/system-status?product=WORKSPACE&cssp=true We will continue to monitor.

3. 8. april 2026 kl. 20.52 UTCmonitoring

   Google has published this https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT We continue to monitor.

4. 8. april 2026 kl. 21.54 UTCmonitoring

   Google has been releasing backed up mail - we expect resolution by 3pm PDT (their resolution estimate).

5. 8. april 2026 kl. 23.34 UTCresolved

   Google has marked this issue resolved.

1. 7. april 2026 kl. 22.49 UTCinvestigating

   We are currently investigating outbound delays for Hosted mail & SMTP server solution customers. We have not observed issues for any other outbound customers at present.

2. 7. april 2026 kl. 23.06 UTCidentified

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

3. 7. april 2026 kl. 23.54 UTCmonitoring

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

4. 8. april 2026 kl. 00.20 UTCresolved

   Queues have recovered and delays as resolved.

1. 29. marts 2026 kl. 21.05 UTCinvestigating

   We are currently investigating inbound mail delays.

2. 29. marts 2026 kl. 21.18 UTCidentified

   We have identified a database issue and are implementing a fix.

3. 29. marts 2026 kl. 21.35 UTCmonitoring

   A fix is in place and we are monitoring results.

4. 29. marts 2026 kl. 22.09 UTCmonitoring

   We are continuing to monitor - the deferred mail queue has dropped ~60% from the highest spike and new mail is flowing. We anticipate full resolution within the hour.

5. 29. marts 2026 kl. 22.32 UTCresolved

   Inbound queues are healthy again. We'll complete an internal post mortem tomorrow and have an RCA available upon request.

1. 18. marts 2026 kl. 19.43 UTCinvestigating

   Customers using our hosted/webmail platform and smtp server solution have reported all their mail in logs is marked as queued. We are investigating.

2. 18. marts 2026 kl. 19.49 UTCidentified

   We have identified the cause and are implementing a fix.

3. 18. marts 2026 kl. 20.23 UTCmonitoring

   A fix has been implemented and we are monitoring results.

4. 18. marts 2026 kl. 22.48 UTCresolved

   We observed status updates universally, but we discovered 2 customers still experiencing too many "queued" emails. Because the larger issue is resolved, we'll close this incident - but we are working on a fix and will communicate directly with the affected parties.

1. 18. marts 2026 kl. 15.08 UTCinvestigating

   Outbound email customers are reporting delays in excess of 10 minutes. We are investigating.

2. 18. marts 2026 kl. 15.19 UTCidentified

   The issue has been identified and a fix is in progress.

3. 18. marts 2026 kl. 15.47 UTCmonitoring

   A fix has been implemented and we are monitoring results - current email testing is coming in under 5 minutes.

4. 18. marts 2026 kl. 16.29 UTCresolved

   This incident has been resolved. Queues have returned to normal and delayed mail is being delivered.

1. 3. marts 2026 kl. 22.40 UTCinvestigating

   We are investigating why users are unable to verify MFA codes and begin fresh sessions in our admin app. If you are already logged in, you can navigate as usual.

2. 3. marts 2026 kl. 23.17 UTCidentified

   The issue has been isolated and a fix is in progress.

3. 3. marts 2026 kl. 23.40 UTCmonitoring

   A fix has been implemented & we are monitoring results.

4. 4. marts 2026 kl. 00.05 UTCresolved

   The issue has been resolved.

1. 25. februar 2026 kl. 22.25 UTCmonitoring

   We are observing intermittent delivery delays affecting a limited subset of outbound messages to certain external domains (including hotmail.com and outlook.com). Our systems remain fully operational. We are actively monitoring and adjusting sending patterns as needed.

2. 26. februar 2026 kl. 19.38 UTCresolved

   We are no longer observing intermittent delays - all mail that was deferred yesterday has been delivered.

1. 23. februar 2026 kl. 17.45 UTCidentified

   Inbound email customers have reported a delay in their quarantine log propagation. Emails are marked quarantine in their mail log, but do not appear in quarantine until hours later. There is no mail flow or data loss issue, but we have identified a problem with timestamps and are working to correct it.

2. 23. februar 2026 kl. 21.56 UTCmonitoring

   We have shipped a correction and are monitoring the results.

3. 24. februar 2026 kl. 02.17 UTCresolved

   This incident has been resolved.

1. 22. januar 2026 kl. 20.20 UTCidentified

   Microsoft365 outage reported on the Microsoft Service Health Status page

2. 23. januar 2026 kl. 14.19 UTCresolved

   This incident has been resolved. Microsoft Service Health Status - https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect

1. 3. december 2025 kl. 17.07 UTCinvestigating

   Some customers report outbound mail delays in excess of 10 min - we are investigating

2. 3. december 2025 kl. 17.17 UTCidentified

   We have identified the issue and are working on a fix.

3. 3. december 2025 kl. 19.30 UTCidentified

   We're continuing to work on the fix for this issue.

4. 3. december 2025 kl. 20.45 UTCmonitoring

   A fix is in place a new mail is flowing normally - we expect another 3-4 hours for the deferred queue to unspool. We'll continue to monitor and update you if anything changes.

5. 3. december 2025 kl. 22.13 UTCinvestigating

   Customers are reporting missing outbound mail log data - we are investigating.

6. 3. december 2025 kl. 23.27 UTCmonitoring

   Mail log data has been restored. We are continuing to monitor the deferred queue while it processes the backlog.

7. 4. december 2025 kl. 04.08 UTCresolved

   The deferral queue has cleared and outbound is functioning normally.

1. 28. november 2025 kl. 18.11 UTCmonitoring

   Some customers are reporting outbound deferrals from Yahoo & affiliates - we are keeping an eye on this.

2. 4. december 2025 kl. 04.08 UTCmonitoring

   We are continuing to monitor reports of Yahoo deferrals independent of today's incident.

3. 6. december 2025 kl. 02.17 UTCresolved

   Email to yahoo.com and affiliates (aol.com, verizon.net, att.net, sbcglobal.net, cox.net, etc) is delivering as normal.

1. 29. september 2025 kl. 19.37 UTCinvestigating

   We are investigating reports of HTTP response timeouts on Email API.

2. 29. september 2025 kl. 20.25 UTCidentified

   We have identified the issue and are working on a fix.

3. 29. september 2025 kl. 21.24 UTCmonitoring

   We have implemented a fix and are monitoring the results.

4. 29. september 2025 kl. 22.18 UTCresolved

   We have been unable to recreate timeout errors post update.