Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Queries to data stored on C120 cluster are failing

Reported by Iterable · CRM, Marketing & Sales · source last read just now

Official source (opens in a new tab)
Vendor start
Apr 23, 2025, 06:50 UTC
Vendor's clock
Resolved
Apr 24, 2025, 23:17 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 16 h
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 partial outage: "Queries to data stored on C120 cluster are failing".[E1, E2]
  • The vendor marked it resolved at 2025-04-24 23:17 UTC.[E3, E7]

Affected products and regions

  • Components: Email Sends, Journey Processing, Push Sends, SMS Sends, User Updates, List Updates, User Deletions.[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-04-24 23:17 UTC · summary s1, evidence f2e5b95a699be545

Evidence (7)
  1. E1Iterable reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Queries to data stored on C120 cluster are failing". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-04-23 06:50 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Email Sends, Journey Processing, Push Sends, SMS Sends, User Updates, List Updates, User Deletions. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-04-24 23:17 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Email Sends, Journey Processing, Push Sends, SMS Sends, User Updates, List Updates, User Deletions

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. Apr 23, 2025, 06:50 UTCVendor-reported startVendor time
  2. Apr 24, 2025, 23:17 UTCVendor-reported resolutionVendor time

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