Vendor reports: major outageResolved · vendor status “resolved”Official status API
Partial Outage and Delivery Issues in US-West-2 Region
Reported by SparkPost · Communication & Messaging · source last read 2 min ago
- Vendor start
- Jul 24, 2026, 11:14 UTC
- Vendor's clock
- Resolved
- Jul 24, 2026, 18:44 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 7 h 30 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
What is unknown
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-07-24 18:44 UTC · summary s1, evidence 501ba01efdbc6a48
Evidence (7)
- E1SparkPost reports major outage. (vendor) source (opens in a new tab)
- E2Vendor title: "Partial Outage and Delivery Issues in US-West-2 Region". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-07-24 11:14 UTC. (vendor) source (opens in a new tab)
- E5Regions written in the title (inferred): us-west-2. (Statuswall) source (opens in a new tab)
- E6Components the vendor attached: Transmissions API - USA, SMTP API - USA, SMTP Delivery - USA. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-07-24 18:44 UTC. (vendor) source (opens in a new tab)
Affected scope
us-west-2
Components: Transmissions API - USA, SMTP API - USA, SMTP Delivery - USA
Read from region codes written in the incident title, so treat it as inferred.
Potential relevance
SparkPost is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Jul 24, 2026, 11:14 UTCVendor-reported startVendor time
- Jul 24, 2026, 18:44 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.