RudderStack: Incorrect routing of ETL events in destination tables
Timeline of updates
- resolved
ETL data routed to default table based on resource name instead of one configured with prefix and resource name. This has been mitigated and data is being backfilled into configured tables.
From RudderStack’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.rudderstack.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by RudderStack, started 2023-06-30 11:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Incorrect routing of ETL events in destination tables
- Vendor
- RudderStack
- Date
- URL
- https://rewindex.com/company/rudderstack/incidents/qkr8f4ljz9yn
RudderStack profileRecent RudderStack incidentsAll outages on June 30, 2023RudderStack in June 2023MarkdownJSON