Paubox Outage History
19 incidents recorded over the last 365 days, 19 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Paubox Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Customers reporting issue with MFA codesRoughly 133 codes got stuck in our internal queues - they have been released and the MFA service is now functioning as expected. The back end is being rewritten this quarter to ensure the issue cannot reoccur. | 49 min | Resolved |
| Sep 21, 2026 | Dashboard data display issues affecting some Outbound and Marketing customersDisplay issues with Outbound Email and Marketing have been resolved. | 3h 6m | Resolved |
| Aug 14, 2026 | Users cannot log in to the Paubox Admin App/Paubox DashboardThe incident has been resolved. | 29 min | Resolved |
| Jul 22, 2026 | Some Inbound customers report blank Inbound quarantinesNo defect was identified, no changes were shipped. Two reasons customers may have encountered this: 1) Paubox is shipping improvements almost daily - if something is suddenly unavailable, you may need to log out/back in… | 58 min | Resolved |
| Jul 8, 2026 | Reports of intermittent inbound mail delaysThis incident has been resolved. | 14 min | Resolved |
| Jun 25, 2026 | Quarantine release non functional for inbound security customersThis incident has been resolved. | 2h 41m | Resolved |
| Jun 17, 2026 | Microsoft certificate rotation causing higher than average secure message conversion for some outbound customersDirect 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. | 1h 46m | Resolved |
| May 12, 2026 | Some hosted/webmail customers report certificate errors blocking mobile log inThis incident has been resolved. | 27h 9m | Resolved |
| Apr 8, 2026 | Some Google Workspace customers report inbound & outbound delays on internal emailsGoogle has marked this issue resolved. | 8h 1m | Resolved |
| Apr 7, 2026 | Outbound delays for Hosted mail & SMTP server solution customersQueues have recovered and delays as resolved. | 1h 30m | Resolved |
| Mar 29, 2026 | Inbound mail delays reportedInbound queues are healthy again. We'll complete an internal post mortem tomorrow and have an RCA available upon request. | 1h 27m | Resolved |
| Mar 18, 2026 | Hosted/webmail customers reporting incorrect statusesWe 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… | 3h 5m | Resolved |
| Mar 18, 2026 | Outbound email customers reporting delaysThis incident has been resolved. Queues have returned to normal and delayed mail is being delivered. | 1h 20m | Resolved |
| Mar 3, 2026 | Users unable to authenticate MFA codesThe issue has been resolved. | 1h 24m | Resolved |
| Feb 25, 2026 | Intermittent delivery delay affecting customers emailing hotmail.com & outlook.comWe are no longer observing intermittent delays - all mail that was deferred yesterday has been delivered. | 21h 13m | Resolved |
| Feb 23, 2026 | Inbound customers report delay in quarantine loggingThis incident has been resolved. | 8h 31m | Resolved |
| Jan 22, 2026 | Microsoft outageThis incident has been resolved. Microsoft Service Health Status - https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect | 17h 58m | Resolved |
| Dec 3, 2025 | Some customers report outbound mail delaysThe deferral queue has cleared and outbound is functioning normally. | 11h 0m | Resolved |
| Nov 28, 2025 | Some customers reporting deferrals from Yahoo & affiliatesEmail to yahoo.com and affiliates (aol.com, verizon.net, att.net, sbcglobal.net, cox.net, etc) is delivering as normal. | 176h 6m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Paubox incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Paubox Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Paubox acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Paubox outage in this window ran 7d 8h, against a mean recovery of 15h 12m. If you depend on Paubox in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.