Companies / Iterable / incidents

Iterable: Catalog Service Disruption

Timeline of updates

1. identified2025-09-22 07:24 UTC

   We are currently experiencing a service disruption with our catalog service, which may prevent some customers from sending messages that use templates with catalog data. Messages that do not use catalog data are not impacted. We've identified the root cause and are actively working on a fix. Please note that no messages have been lost. Our system will automatically retry all failed sends once the service has recovered. We will provide another update in 30 minutes, or sooner if the issue is resolved. We apologize for the inconvenience and thank you for your patience.

2. identified2025-09-22 08:05 UTC

   We have started rolling out the fix to individual machines and are seeing some of our messaging capabilities recover. Some customers may still have a delay in sends that use templates with catalog data, and ingestion delays for updating catalog data. We are continuing to apply the fix across all affected systems and will monitor the situation closely. No messages have been lost, and our system will automatically retry all failed sends once the service has fully recovered. We will provide another update in 30 minutes, or sooner if the issue is resolved. We appreciate your continued patience.

3. resolved2025-09-22 08:24 UTC

   The issue with our catalog service has been fully resolved, and all services are now operating normally. Any delayed sends and catalog updates are being processed currently. Messages that were queued during the disruption will be automatically retried and delivered.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Iterable profile · Recent Iterable incidents · Markdown · JSON