SparkPost incident

Partial Outage and Delivery Issues in US-West-2 Region

Critical Resolved View vendor source →

SparkPost experienced a critical incident on July 24, 2026 affecting Transmissions API - USA and SMTP API - USA and 1 more component, lasting 7h 29m. The incident has been resolved; the full update timeline is below.

Started
Jul 24, 2026, 11:14 AM UTC
Resolved
Jul 24, 2026, 06:44 PM UTC
Duration
7h 29m
Detected by Pingoru
Jul 24, 2026, 11:14 AM UTC

Affected components

Transmissions API - USASMTP API - USASMTP Delivery - USA

Update timeline

  1. investigating Jul 24, 2026, 11:14 AM UTC

    We are investigating delivery issues caused by an ongoing AWS US West 2 region outage. Customers may experience delays or failures while we assess the impact to our service. We are actively monitoring the situation and will provide updates as more information becomes available.

  2. identified Jul 24, 2026, 11:53 AM UTC

    Outbound email delivery is blocked for our US West region. We working with our vendor resolve the issue. We are continuing to accept emails and queue them internally. We will deliver the messages as soon as the issue is resolved.

  3. monitoring Jul 24, 2026, 12:08 PM UTC

    We are starting to deliver mails in our US West region. We are working through the queued messages. We are continuing to monitor the issue and continuing to accept emails.

  4. monitoring Jul 24, 2026, 01:16 PM UTC

    We are still working through the queued messages. We are continuing to monitor the issue and continuing to accept emails.

  5. monitoring Jul 24, 2026, 05:29 PM UTC

    We have implemented additional tuning to handle the significant influx of mail due to the AWS network outage and we are seeing improvement in delivery rates We are seeing significant recovery and expect most mail to be fully delivered in the next 30-35 minutes. Estimated time for full recovery is 80-90 minutes. We are continuing to look for additional optimizations and monitor the issue.

  6. resolved Jul 24, 2026, 06:44 PM UTC

    This incident has been resolved.