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

Ingestion and processing delay

Reported by Iterable · CRM, Marketing & Sales · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Mar 25, 2026, 19:00 UTC
Vendor's clock
Resolved
Mar 25, 2026, 19:22 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
22 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

  • Iterable reports degraded: "Ingestion and processing delay".[E1, E2]
  • The vendor marked it resolved at 2026-03-25 19:22 UTC.[E3, E7]

Affected products and regions

  • Components: Journey Processing, Journey Processing, Journey Processing, User Updates, User Updates, User Updates, List Uploads, List Uploads, List Updates.[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: 2026-03-25 19:22 UTC · summary s1, evidence 97206fbfc7dc55f4

Evidence (7)
  1. E1Iterable reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Ingestion and processing delay". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-03-25 19:00 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Journey Processing, Journey Processing, Journey Processing, User Updates, User Updates, User Updates, List Uploads, List Uploads, List Updates. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-03-25 19:22 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Journey Processing, Journey Processing, Journey Processing, User Updates, User Updates, User Updates, List Uploads, List Uploads, List Updates

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

Iterable 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. Mar 25, 2026, 19:00 UTCVendor-reported startVendor time
  2. Mar 25, 2026, 19:22 UTCVendor-reported resolutionVendor time

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