Treasure Data incident

[EU01 Tokyo AP03 Regions] Batch Data Load failure for RT2.0

Resolved after 13 hours 53 minutes, affecting Realtime 2.0 and Realtime 2.0 and 1 more, on September 30, 2026.

resolved Sep 30, 2026, 04:36 AM UTC

Between Sept 28th (5:30 PM UTC) and Sept 29th (6:30 PM UTC) customers with no batch segments who had scheduled attribute updates would have seen failed jobs preventing batch data from loading into Reactor. Customers would have seen errors while waiting for the config changes to update. The impact is any realtime applications, personalizations, or campaigns during that window may have relied on stale batch attribute data. The system has recovered and workflows are now sending updated data.

Started
Sep 30, 2026, 04:36 AM UTC
Resolved
Sep 30, 2026, 06:30 PM UTC
Duration
13h 53m
Detected by Pingoru
Sep 30, 2026, 04:36 AM UTC

Affected components

Realtime 2.0Realtime 2.0Realtime 2.0

Update timeline

  1. resolved Sep 30, 2026, 04:36 AM UTC

    Between Sept 28th (5:30 PM UTC) and Sept 29th (6:30 PM UTC) customers with no batch segments who had scheduled attribute updates would have seen failed jobs preventing batch data from loading into Reactor. Customers would have seen errors while waiting for the config changes to update. The impact is any realtime applications, personalizations, or campaigns during that window may have relied on stale batch attribute data. The system has recovered and workflows are now sending updated data.

Your product runs on more than Treasure Data

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →