Treasure Data Status

Investigating: Our utilization dashboards are not updating with up-to-date information. Customers accessing their Treasure Data usage dashboards will see a gap in usage details from early morning Saturday UTC. There is no impact to ongoing usage of Treasure Data, and all usage information is correctly being stored internally. However, the dashboard where customers can view their consumption is not up-to-date. We are working to diagnose the issue, and will provide an update in the next hour.

Resolved: We are writing to inform you that the issue with realtime attribute retrieval in the CDP API occurred on June 23, 2025, at 04:46 UTC and was resolved on June 23, 2025, at 07:55 UTC.

We sincerely apologize for any inconvenience this may have caused.

Identified: We are currently experiencing an issue with the CDP API concerning the retrieval of realtime attributes.

When opening the settings screen or attempting to change settings, realtime attribute values cannot be retrieved, resulting in an error. This issue exclusively affects the realtime segment settings screen and does not impact the actual behavior of realtime segments.

Our team is actively working to resolve this issue.

We sincerely apologize for any inconvenience or disruption this may cause.

Investigating: Our utilization dashboards are not updating with up-to-date information. Customers accessing their Treasure Data usage dashboards will see a gap in usage details from early morning Saturday UTC. There is no impact to ongoing usage of Treasure Data, and all usage information is correctly being stored internally. However, the dashboard where customers can view their consumption is not up-to-date. We are working to diagnose the issue, and will provide an update in the next hour.

Resolved: We are writing to inform you that the issue with realtime attribute retrieval in the CDP API occurred on June 23, 2025, at 04:46 UTC and was resolved on June 23, 2025, at 07:55 UTC.

We sincerely apologize for any inconvenience this may have caused.

Identified: We are currently experiencing an issue with the CDP API concerning the retrieval of realtime attributes.

When opening the settings screen or attempting to change settings, realtime attribute values cannot be retrieved, resulting in an error. This issue exclusively affects the realtime segment settings screen and does not impact the actual behavior of realtime segments.

Our team is actively working to resolve this issue.

We sincerely apologize for any inconvenience or disruption this may cause.

Investigating: Our utilization dashboards are not updating with up-to-date information. Customers accessing their Treasure Data usage dashboards will see a gap in usage details from early morning Saturday UTC. There is no impact to ongoing usage of Treasure Data, and all usage information is correctly being stored internally. However, the dashboard where customers can view their consumption is not up-to-date. We are working to diagnose the issue, and will provide an update in the next hour.

Resolved: We are writing to inform you that the issue with realtime attribute retrieval in the CDP API occurred on June 23, 2025, at 04:46 UTC and was resolved on June 23, 2025, at 07:55 UTC.

We sincerely apologize for any inconvenience this may have caused.

Identified: We are currently experiencing an issue with the CDP API concerning the retrieval of realtime attributes.

When opening the settings screen or attempting to change settings, realtime attribute values cannot be retrieved, resulting in an error. This issue exclusively affects the realtime segment settings screen and does not impact the actual behavior of realtime segments.

Our team is actively working to resolve this issue.

We sincerely apologize for any inconvenience or disruption this may cause.

Investigating: Our utilization dashboards are not updating with up-to-date information. Customers accessing their Treasure Data usage dashboards will see a gap in usage details from early morning Saturday UTC. There is no impact to ongoing usage of Treasure Data, and all usage information is correctly being stored internally. However, the dashboard where customers can view their consumption is not up-to-date. We are working to diagnose the issue, and will provide an update in the next hour.

Resolved: We are writing to inform you that the issue with realtime attribute retrieval in the CDP API occurred on June 23, 2025, at 04:46 UTC and was resolved on June 23, 2025, at 07:55 UTC.

We sincerely apologize for any inconvenience this may have caused.

Identified: We are currently experiencing an issue with the CDP API concerning the retrieval of realtime attributes.

When opening the settings screen or attempting to change settings, realtime attribute values cannot be retrieved, resulting in an error. This issue exclusively affects the realtime segment settings screen and does not impact the actual behavior of realtime segments.

Our team is actively working to resolve this issue.

We sincerely apologize for any inconvenience or disruption this may cause.

Investigating: Our utilization dashboards are not updating with up-to-date information. Customers accessing their Treasure Data usage dashboards will see a gap in usage details from early morning Saturday UTC. There is no impact to ongoing usage of Treasure Data, and all usage information is correctly being stored internally. However, the dashboard where customers can view their consumption is not up-to-date. We are working to diagnose the issue, and will provide an update in the next hour.

Resolved: We are writing to inform you that the issue with realtime attribute retrieval in the CDP API occurred on June 23, 2025, at 04:46 UTC and was resolved on June 23, 2025, at 07:55 UTC.

We sincerely apologize for any inconvenience this may have caused.

Identified: We are currently experiencing an issue with the CDP API concerning the retrieval of realtime attributes.

When opening the settings screen or attempting to change settings, realtime attribute values cannot be retrieved, resulting in an error. This issue exclusively affects the realtime segment settings screen and does not impact the actual behavior of realtime segments.

Our team is actively working to resolve this issue.

We sincerely apologize for any inconvenience or disruption this may cause.