Störungsverlauf von Paubox

1. 21. Oktober 2026 um 15:36 UTCinvestigating

   Wir untersuchen ein Problem, bei dem MFA-Codes nicht erhalten werden.

2. 21. Oktober 2026 um 15:52 UTCidentified

   Wir haben das Problem erkannt und arbeiten an einer Lösung. Sowohl TOTP (Authentifizierungs-Apps) als auch Passkey-Optionen sind funktional, wenn wir dies verfolgen.

3. 21. Oktober 2026 um 16:26 UTCresolved

   Ungefähr 133 Codes sind in unseren internen Warteschlangen stecken geblieben - sie wurden veröffentlicht und der MFA-Service funktioniert jetzt wie erwartet. Das Backend wird in diesem Quartal neu geschrieben, um sicherzustellen, dass das Problem nicht wieder auftreten kann.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. September 2026 um 21:17 UTCmonitoring

   Einige Outbound- und Marketing-Kunden sehen möglicherweise unvollständige oder fehlende Informationen in den Bereichen Mail Log und Paubox Marketing des Dashboards, und Marketing-Seiten können langsam geladen oder ausgeschaltet werden. E-Mail-Zustellung ist nicht betroffen. Nachrichten werden normalerweise gesendet, empfangen, gefiltert und verschlüsselt. Es sind keine Kundendaten verloren gegangen – dies wirkt sich nur darauf aus, wie die aktuelle Aktivität angezeigt wird. Wir haben die Ursache des Mail Log-Problems identifiziert und eine Lösung gefunden. Wir untersuchen immer noch das Marketing-Problem. Wir werden diese Seite aktualisieren, da wir mehr haben.

2. 22. September 2026 um 00:23 UTCresolved

   Anzeigeprobleme mit Outbound E-Mail und Marketing wurden behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. August 2026 um 19:36 UTCidentified

   Wir haben ein problem identifiziert, das die anmeldung in unserer admin-app blockiert, und sollten in kürze eine lösung haben.

2. 14. August 2026 um 19:48 UTCmonitoring

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

3. 14. August 2026 um 20:06 UTCresolved

   The incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 20:08 UTCinvestigating

   Wir untersuchen Berichte von einigen Inbound Security-Kunden, dass ihre Inbound-Quarantänien leer sind, obwohl Post in ihren Mail-Logs als unter Quarantäne gestellt gekennzeichnet ist.

2. 22. Juli 2026 um 21:06 UTCresolved

   Es wurde kein Defekt festgestellt, keine Änderungen wurden ausgeliefert. Zwei Gründe, warum Kunden darauf gestoßen sein könnten: 1) Paubox versendet fast täglich Verbesserungen - wenn plötzlich etwas nicht verfügbar ist, müssen Sie sich möglicherweise anmelden / zurück, um Ihren Zugang zu aktualisieren Damit die Inbound-Quarantäne Ergebnisse anzeigt, müssen "alle Kategorien" oder mindestens eine Kategorie ausgewählt werden. Wenn keine Kategorien ausgewählt sind, zeigt die Seite keine Ergebnisse an.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. Juli 2026 um 19:07 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 8. Juli 2026 um 19:22 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 25. Juni 2026 um 15:23 UTCidentified

   Kunden berichten, dass die Freisetzung einer eingehenden Sicherheitsquarantäne nicht funktionell ist - ein Fix ist in Arbeit.

2. 25. Juni 2026 um 17:11 UTCmonitoring

   Ein Fix ist vorhanden und wir überwachen die Ergebnisse.

3. 25. Juni 2026 um 18:04 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. Juni 2026 um 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 um 17:00 UTCmonitoring

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

3. 17. Juni 2026 um 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. Mai 2026 um 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. Mai 2026 um 23:02 UTCresolved

   This incident has been resolved.

1. 8. April 2026 um 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 um 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 um 20:52 UTCmonitoring

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

4. 8. April 2026 um 21:54 UTCmonitoring

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

5. 8. April 2026 um 23:34 UTCresolved

   Google has marked this issue resolved.

1. 7. April 2026 um 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 um 23:06 UTCidentified

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

3. 7. April 2026 um 23:54 UTCmonitoring

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

4. 8. April 2026 um 00:20 UTCresolved

   Queues have recovered and delays as resolved.

1. 29. März 2026 um 21:05 UTCinvestigating

   We are currently investigating inbound mail delays.

2. 29. März 2026 um 21:18 UTCidentified

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

3. 29. März 2026 um 21:35 UTCmonitoring

   A fix is in place and we are monitoring results.

4. 29. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 19:49 UTCidentified

   We have identified the cause and are implementing a fix.

3. 18. März 2026 um 20:23 UTCmonitoring

   A fix has been implemented and we are monitoring results.

4. 18. März 2026 um 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. März 2026 um 15:08 UTCinvestigating

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

2. 18. März 2026 um 15:19 UTCidentified

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

3. 18. März 2026 um 15:47 UTCmonitoring

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

4. 18. März 2026 um 16:29 UTCresolved

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

1. 3. März 2026 um 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. März 2026 um 23:17 UTCidentified

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

3. 3. März 2026 um 23:40 UTCmonitoring

   A fix has been implemented & we are monitoring results.

4. 4. März 2026 um 00:05 UTCresolved

   The issue has been resolved.

1. 25. Februar 2026 um 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 um 19:38 UTCresolved

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

1. 23. Februar 2026 um 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 um 21:56 UTCmonitoring

   We have shipped a correction and are monitoring the results.

3. 24. Februar 2026 um 02:17 UTCresolved

   This incident has been resolved.

1. 22. Januar 2026 um 20:20 UTCidentified

   Microsoft365 outage reported on the Microsoft Service Health Status page

2. 23. Januar 2026 um 14:19 UTCresolved

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

1. 3. Dezember 2025 um 17:07 UTCinvestigating

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

2. 3. Dezember 2025 um 17:17 UTCidentified

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

3. 3. Dezember 2025 um 19:30 UTCidentified

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

4. 3. Dezember 2025 um 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. Dezember 2025 um 22:13 UTCinvestigating

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

6. 3. Dezember 2025 um 23:27 UTCmonitoring

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

7. 4. Dezember 2025 um 04:08 UTCresolved

   The deferral queue has cleared and outbound is functioning normally.

1. 28. November 2025 um 18:11 UTCmonitoring

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

2. 4. Dezember 2025 um 04:08 UTCmonitoring

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

3. 6. Dezember 2025 um 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 um 19:37 UTCinvestigating

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

2. 29. September 2025 um 20:25 UTCidentified

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

3. 29. September 2025 um 21:24 UTCmonitoring

   We have implemented a fix and are monitoring the results.

4. 29. September 2025 um 22:18 UTCresolved

   We have been unable to recreate timeout errors post update.