Is Treasure Data down?

Since October 13, 2026 02:00 UTC, some import jobs that read Parquet files from Amazon S3 complete successfully but load date and time columns as text (string) instead of numbers (long). If the destination table already defines these columns as long, the imported values are empty (NULL). Only columns stored with a date or time type in the Parquet file are affected. Other columns and other data connectors are not affected. We have identified the cause, a change introduced in the October 13 release, and are preparing a fix. We are assessing the full scope of impact. We will provide an update in 30 minutes.

We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are implementing a fix. Until the fix is deployed, affected import jobs continue to complete successfully with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period. We will provide an update in 1 hour.

We have identified the cause of Amazon S3 Parquet imports loading date and time columns as text (string) instead of numbers (long) since October 13, 2026 02:00 UTC, and are deploying a fix. Until the fix is deployed, affected import jobs continue to complete with these columns loaded as text. Other columns and other data connectors are not affected. We are verifying data integrity for data imported during this period. We will provide an update in 30 minutes.

We have deployed a fix for Amazon S3 Parquet imports loading date and time columns as text. New import jobs load these columns as numbers (long), as before October 13, 2026. We are monitoring to ensure stability. We will provide an update in 30 minutes.

The issue causing Amazon S3 Parquet imports to load date and time columns as text (string) instead of numbers (long) has been resolved. A fix was deployed on October 22, 2026 at 07:40 UTC, and new import jobs load these columns as numbers (long), as before October 13, 2026. Data imported between October 13, 2026 02:00 UTC and October 22, 2026 07:40 UTC may contain affected date and time columns. We will contact affected customers directly. We apologize for the inconvenience and thank you for your patience.

Since approximately 22:55 UTC on October 6, users of the Treasure AI Voice mobile app may be unable to transfer new recordings from their device. The transfer fails with an "Unauthorized" error. This affects both Wi-Fi and Bluetooth transfers. We have identified the cause and are deploying a fix. Recordings that were already transferred, and their transcripts and summaries, are not affected. We will provide an update in 30 minutes.

We are continuing to work on a fix for this issue.

We have deployed a server-side fix for the recording transfer failures in Treasure AI Voice. New transfers from the mobile app are succeeding again. No app update is required. Recordings that failed to transfer during the incident can be transferred again from the device. We are monitoring to ensure stability.

The recording transfer failures in Treasure AI Voice have been resolved. All systems are operating normally. Between approximately 22:55 UTC on October 6 and [fix time] UTC on October 7, new recordings could not be transferred from the mobile app. We deployed a server-side fix, and no app update is required. Recordings that failed to transfer during this period can be transferred again from the device. Thank you for your patience.

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.

We are currently investigating batch export jobs failing to load data into Reactor in the US (AWS) region. Data updates will be delayed up to 24 hours. We will update status in one hour.

A fix has been implemented and we have observed that jobs are succeeding.

This incident has been resolved, and our support team will be following up with affected customers.

We are currently experiencing an issue with our Live Chat feature for Corporate and Enterprise support plans. Our team is actively investigating. You can still reach our support team as usual by emailing [email protected]. We appreciate your patience and apologize for any inconvenience.

We have identified and resolved the issue affecting the Live Chat feature for Corporate and Enterprise support plans. The service has been fully restored and is operating normally. We sincerely apologize for any inconvenience this may have caused and thank you for your patience.