Paubox incident

Outbound mail delay reported by some customers

Major Resolved View vendor source →

Paubox experienced a major incident on March 5, 2025 affecting Outbound Security, lasting 7h 44m. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2025, 04:58 PM UTC
Resolved
Mar 06, 2025, 12:42 AM UTC
Duration
7h 44m
Detected by Pingoru
Mar 05, 2025, 04:58 PM UTC

Affected components

Outbound Security

Update timeline

  1. investigating Mar 05, 2025, 04:58 PM UTC

    We are currently investigating a mail delay in excess of 10 minutes on our outbound servers.

  2. identified Mar 05, 2025, 05:58 PM UTC

    While some customers report an outbound mail delay in excess of 60 minutes, we have identified the issue and are working on a solution. An additional report has been filed demonstrating ~10 minute delay on Email API.

  3. monitoring Mar 05, 2025, 07:10 PM UTC

    We have resolved the root cause of the delay however it will take a few hours for queues to return to normal processing time. We apologize for the inconvenience.

  4. monitoring Mar 05, 2025, 08:23 PM UTC

    Observing significant recovery in outbound queue sizes but delays will continue until they unspool. We will continue to monitor.

  5. monitoring Mar 05, 2025, 08:34 PM UTC

    New email is flowing normally - email sent from ~11am et until ~3pm et is still unspooling.

  6. monitoring Mar 05, 2025, 10:36 PM UTC

    Outbound queues are continuing to drop. We'll continue to monitor until deferred mail is delivered. If you see a "delivery status unknown" in your mail log - very likely it is caught in this delay. Logs should update automatically once queues clear.

  7. monitoring Mar 05, 2025, 10:36 PM UTC

    We are continuing to monitor for any further issues.

  8. monitoring Mar 05, 2025, 11:40 PM UTC

    Queue sizes have been reduced 90%; monitoring is ongoing until we observe deferrals have resolved.

  9. resolved Mar 06, 2025, 12:42 AM UTC

    Deferred mail has been delivered and the incident is now resolved.