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

ingestion delays on c22

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

Official source (opens in a new tab)
Vendor start
Jan 13, 2025, 22:41 UTC
Vendor's clock
Resolved
Jan 14, 2025, 01:03 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 h 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 delays on c22".[E1, E2]
  • The vendor marked it resolved at 2025-01-14 01:03 UTC.[E3, E7]

Affected products and regions

  • Components: User Updates, List Uploads.[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-01-14 01:03 UTC · summary s1, evidence 210f90467a35b8cb

Evidence (7)
  1. E1Iterable reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "ingestion delays on c22". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-01-13 22:41 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: User Updates, List Uploads. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-01-14 01:03 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: User Updates, List Uploads

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. Jan 13, 2025, 22:41 UTCVendor-reported startVendor time
  2. Jan 14, 2025, 01:03 UTCVendor-reported resolutionVendor time

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

Iterable: ingestion delays on c22 — statuswall