Vendor reports: degradedResolved · vendor status “resolved”Official status API

Webhook delays for some SparkPost customers (US hosted only)

Reported by SparkPost · Communication & Messaging · source last read just now

Official source (opens in a new tab)
Vendor start
Nov 20, 2025, 15:56 UTC
Vendor's clock
Resolved
Nov 20, 2025, 18:23 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 h 27 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

  • SparkPost reports degraded: "Webhook delays for some SparkPost customers (US hosted only)".[E1, E2]
  • The vendor marked it resolved at 2025-11-20 18:23 UTC.[E3, E7]

Affected products and regions

  • Components: Event Webhooks - USA.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-11-20 18:23 UTC · summary s1, evidence 812f5e8f9cd1b6de

Evidence (7)
  1. E1SparkPost reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Webhook delays for some SparkPost customers (US hosted only)". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-11-20 15:56 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Event Webhooks - USA. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-11-20 18:23 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Event Webhooks - USA

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

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.

  1. Nov 20, 2025, 15:56 UTCVendor-reported startVendor time
  2. Nov 20, 2025, 18:23 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.