Historique des pannes de Treasure Data

1. 27 juillet 2026 à 08:29 UTCresolved

   Entre 7/25 et aujourd'hui, 7/27 à 11:30 JST, nous avons connu un problème de dégradation des performances affectant BulkLoad (Data Connector Import), Result Export (Activation) et Bulk Import. À la suite des rapports reçus ce matin, notre équipe d'ingénieurs a étudié la question et identifié la charge élevée du système dans des conditions spécifiques (retard croissant dans la communication des composants internes) comme étant la cause principale. Le problème a été résolu par rotation complète de nos nœuds de serveur, et la pleine performance a été rétablie à partir de 11:30 AM JST. Nous nous excusons sincèrement pour tout désagrément causé. Nous examinons actuellement nos règles de surveillance et d'alerte afin d'éviter des problèmes similaires à l'avenir.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 7 juillet 2026 à 17:04 UTCinvestigating

   Nous observons des performances dégradées dans Treasure Work et tdx dans la région de Tokyo. Ce numéro est limité au modèle Claude Haiku 4.5 dans la région de Tokyo seulement. Les utilisateurs peuvent remarquer que les demandes utilisent Claude Haiku 4.5 erreurs de retour ou de délai. Pour le moment, nous ne voyons aucun problème avec d'autres modèles. Comme solution de rechange, les utilisateurs peuvent choisir un modèle différent. Nous enquêtons activement sur cette question et nous nous efforcerons de la mettre à jour dans 30 minutes.

2. 7 juillet 2026 à 17:40 UTCinvestigating

   Nous continuons d'enquêter sur cette question et nous fournirons une autre mise à jour dans 30 minutes.

3. 7 juillet 2026 à 18:07 UTCidentified

   Nous continuons d'étudier cette question et nous évaluons actuellement une solution possible. Nous mettrons à jour dès que nos tests seront terminés.

4. 7 juillet 2026 à 19:42 UTCidentified

   Nous continuons de travailler à la recherche d'une solution et à la détermination de tout facteur contributif potentiel. Encore une fois, comme le problème est localisé aux modèles Haiku 4.5 dans la région de Tokyo, nous recommandons aux utilisateurs d'utiliser temporairement un autre modèle s'ils connaissent des taux d'erreur élevés. Nous nous excusons pour le désagrément et nous aurons bientôt une autre mise à jour.

5. 7 juillet 2026 à 20:27 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

6. 7 juillet 2026 à 20:59 UTCresolved

   Cette question a été résolue. Treasure Work et tdx fonctionnent normalement, et le modèle Claude Haiku 4.5 de la région de Tokyo ne connaît plus d'erreurs ou de chronométrages. Merci de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 26 juin 2026 à 21:48 UTCidentified

   Nous vivons une dégradation des performances des requêtes Hive dans la région américaine. Ce numéro a commencé le 25 juin 2026. Les utilisateurs peuvent observer des temps d'exécution de la requête plus longs que prévu, en particulier pour les tâches à long terme avec de grands volumes de données. Nous avons identifié la cause et nous travaillons sur une solution. Nous fournirons une mise à jour dans 30 minutes.

2. 26 juin 2026 à 22:22 UTCidentified

   Nous vivons une dégradation des performances des requêtes Hive dans la région américaine. Ce numéro a commencé le 25 juin 2026. Les utilisateurs peuvent observer des temps d'exécution de la requête plus longs que prévu, en particulier pour les tâches à long terme avec de grands volumes de données. Nous avons identifié la cause. Pour y remédier, nous validons un changement de configuration de cluster avant de l'appliquer à l'environnement de production. Nous fournirons une mise à jour dans 30 minutes.

3. 26 juin 2026 à 22:57 UTCidentified

   Nous continuons de travailler sur une solution. Notre équipe valide un changement de configuration avant de l'appliquer à l'environnement de production. Nous fournirons une mise à jour dans 30 minutes.

4. 26 juin 2026 à 23:57 UTCmonitoring

   Nous avons fourni un nouveau cluster avec une capacité suffisante et nous y acheminons maintenant des emplois. On s'attend à ce que la performance des requêtes se rétablisse progressivement à mesure que le groupe se stabilise. Nous suivons la situation de près. Nous fournirons une mise à jour dans 1 heure.

5. 27 juin 2026 à 01:13 UTCresolved

   La dégradation de la performance des requêtes de sauvetage dans la région américaine a été résolue. Nous avons réussi à fournir un nouveau cluster et acheminé tout le trafic vers lui. Les systèmes fonctionnent maintenant normalement. Merci de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 25 juin 2026 à 11:46 UTCresolved

   Résolue — Certains emplois d'exportation de résultats (exportation de données) aux États-Unis, à Tokyo et dans les régions de l'UE peuvent avoir échoué ou avoir été retardés entre le 24 juin 2026 21:00 UTC et le 25 juin 2026 05:26 UTC. Au cours de cette période, les nœuds de calcul sous-jacents étaient intermittents et instables, ce qui pourrait entraîner la cessation des travaux d'exportation avant d'être terminés. Dans certains cas, un emploi touché peut avoir pris fin sans message d'erreur clair. Le problème a été résolu et tous les systèmes fonctionnent normalement. L'intégrité des données n'est pas affectée — les données sources dans Treasure Data n'ont pas été affectées; seule la livraison d'emplois d'exportation vers des destinations extérieures pendant cette fenêtre aurait pu être perturbée. Si vous avez exécuté une exportation de résultats/données pendant cette fenêtre, nous vous recommandons de la confirmer complétée et de la relancer si la sortie semble incomplète. Nous contacterons également directement les clients concernés. Merci de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 24 juin 2026 à 11:11 UTCresolved

   Nous avons identifié un retard dans l'enregistrement des données de l'événement e-mail (comme ouvrir, cliquer, rebondir, les événements de livraison et les événements d'erreur) aux tables d'événements clients. Période affectée (approximative): - 22 juin, 03:45 UTC – 23 juin, 04:15 UTC - 23 juin, 07:00 UTC – 24 juin, 07:30 UTC Pendant ces périodes, l'enregistrement des données de l'événement par courriel a été retardé. La livraison du courriel n'a pas été affectée — les courriels ont été envoyés et reçus normalement. Le problème a été résolu et tous les systèmes fonctionnent normalement. Les événements retardés ont été entièrement traités. Si vous avez lancé des requêtes sur des tables event ou error event pendant les périodes concernées, nous vous suggérons de réinitialiser ces requêtes pour obtenir des résultats précis. Nous nous excusons pour tout désagrément.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 5 mai 2026 à 16:20 UTCidentified

   Incident: Real-time Profile Deletion Workflow Failures Status: Identified Impacted Regions: EU01, US01, Tokyo, AP03 (USA) Update (May 5, 2026 - 11:19 AM CDT) We have identified the root cause of the failures affecting Real-time (RT) bulk profile deletion, load, and stitch workflows in the affected regions. Summary of the Issue: A backend configuration issue resulted in a loss of necessary permissions for the service responsible for processing Real-time bulk profile operations. As a result, impacted workflows are failing with an "Authorization" or "400" error when attempting to invoke internal functions. Current Status: Our engineering team has developed a fix and is currently in the process of deploying it to all affected regions. We expect service to be restored shortly after the deployment is completed. We will provide a further update once the fix has been fully deployed and we have confirmed that workflow processing has returned to normal.

2. 5 mai 2026 à 16:23 UTCidentified

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

3. 5 mai 2026 à 17:43 UTCresolved

   We have applied the fix, and are observing that traffic is flowing correctly now.

1. 27 avril 2026 à 17:31 UTCmonitoring

   Between 8:05 AM and 8:30 AM PDT, customers operating in the EU01 (Europe) region may have experienced intermittent errors (5xx) affecting two primary areas: Data Ingestion: Errors when attempting to send records via the Ingest API. Real-Time Personalization: Request failures for personalization and profile lookup services. The disruption was caused by an service interruption with an upstream provider in our data processing layer within the eu-central-1 region. This prevented our systems from successfully persisting incoming data to our streaming infrastructure and executing real-time lookups during the affected window. The upstream provider has confirmed the issue is resolved. Our engineering team monitored the recovery, and we have confirmed that all services in the EU01 region have returned to normal operating parameters. Data Integrity: For data ingestion, records that were rejected with a retryable error code during this window should be resubmitted. Records that have already been successfully ingested following the recovery require no further action. Personalization: Real-time request success rates have returned to 100%. We are continuing to monitor the stability of the region. We apologize for any inconvenience this may have caused to your operations. For further questions, please contact our support team at [email protected].

2. 27 avril 2026 à 18:25 UTCresolved

   The upstream provider has restored service.

1. 18 février 2026 à 20:45 UTCinvestigating

   We are investigating a possible problem currently affecting Treasure Insights. We will provide an update as soon as we know more.

2. 18 février 2026 à 21:27 UTCidentified

   We have partially resolved the incident. We are continuously working to resolve the incident.

3. 18 février 2026 à 21:32 UTCmonitoring

   The performance went back to normal, and no errors are observed now. We will monitor at least for 15 minutes.

4. 18 février 2026 à 22:00 UTCresolved

   This incident has been resolved.

1. 21 janvier 2026 à 02:55 UTCinvestigating

   Starting at approximately 17:00 PST, we observed increased latency affecting all operations accessing table resources in Plazma. At around 19:00 PST, we applied temporary tuning to the database managing table resources and confirmed recovery based on internal performance metrics. We are currently continuing to monitor the system to ensure overall performance remains stable. Visible impacts are: - Streaming, Mobile, and JavaScript/Browser imports may delay - Jobs execution may delay - Table creation may error - Console execution may delay - Plazma Public API may return errors - Treasure Workflow may delay and fail - Workflow REST API may be unavailable - Workflow operations in Console and CLI may become unavailable - Presto JDBC/ODBC queries and CDP segmentation queries may fail - Console Table preview update may delay - The REST API to submit and cancel jobs may be unavailable - Data Connector Integrations may become unavailable - ADH (Ads Data Hub) and DCR (Data Clean Room) service may be unavailable - ADL (Active Data Layer) service may be unavailable We will send an additional update in 30 minutes

2. 21 janvier 2026 à 03:37 UTCidentified

   We identified the same issue in the Tokyo region and applied database parameter tuning. We are currently assessing the impact of this change on system performance. As a result of this temporary mitigation applied in both the US and Tokyo regions, the following impact is observed: In Data Workbench, updates to table metadata for row counts and preview data are temporarily paused. We will continue monitoring and provide further updates as we make progress.

3. 21 janvier 2026 à 03:40 UTCidentified

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

4. 21 janvier 2026 à 04:06 UTCidentified

   Performance in the Tokyo region improved at approximately 12:50 JST. The Tokyo region had been experiencing gradually increasing performance degradation since around 09:00 JST. We are currently proceeding with the steps to resume updates of table metadata in Data Workbench. Due to the temporary pause of metadata updates, application metrics that rely on this information, such as Parent Segment size, have also been temporarily not updated. We will continue monitoring the system and share further updates as needed.

5. 21 janvier 2026 à 04:12 UTCidentified

   In the US region, table metadata updates have been resumed. At this point, the system in the US region is expected to be fully recovered, and we are continuing to monitor it closely. For the Tokyo region, metadata updates will be resumed after we complete confirmation of system performance. We will provide another update when this step begins.

6. 21 janvier 2026 à 04:41 UTCmonitoring

   The system in the US region is operating normally with no observed issues. In the Tokyo region, table metadata updates have also been resumed. At this point, the Tokyo region is expected to be fully recovered, and we will continue to monitor system performance. Once stability is fully confirmed, we plan to close this status page.

7. 21 janvier 2026 à 05:07 UTCresolved

   Incident Impact Summary (Plazma / Table Resources) We have confirmed that the system in the Tokyo region is operating normally with no remaining issues. What happened - All operations accessing Plazma table resources experienced increased latency. When - US region: 17:00 PST – 18:40 PST - Tokyo region: 09:00 JST – 12:50 JST Temporary impact during recovery - Updates to table row counts and preview data were temporarily paused. Recovery status - US region: Table metadata updates resumed at 20:00 PST. - Tokyo region: Table metadata updates resumed at 13:40 JST. Both regions are now fully recovered. Data integrity - No data loss or data corruption occurred. We will prepare and publish a post-mortem document to explain the circumstances under which this incident occurred one day after the recent system maintenance. With this confirmation, the incident is now closed.

8. 26 janvier 2026 à 18:36 UTCpostmortem

   ## Post-Mortem Summary This incident was related to a database maintenance performed on January 19, during which management of Plazma table resources was migrated from the existing RDBMS to a dedicated Aurora database. The purpose of this change was to better isolate table resource workloads and improve long-term scalability. The migration itself completed successfully, and both the original database and the newly introduced Aurora database were operating normally immediately after the maintenance. On the following day, when internal batch processes began running, the newly introduced database experienced unexpected load. Investigation determined that the internal batch system was configured to connect to the master database endpoint instead of a reader endpoint. As a result, internal batch processing competed with user-facing requests, causing increased latency when accessing table resources. To mitigate the impact and enable rapid recovery, temporary database tuning was applied. This tuning was intended solely as a short-term measure to stabilize the system and has since been fully reverted. The permanent fix consisted of correcting the configuration of the internal batch system so that it accesses the appropriate database endpoint. Following these actions, system performance recovered in both the US and Tokyo regions, and all services returned to normal operation. No data loss or data corruption occurred. To prevent similar issues in the future, we are reviewing our configuration and deployment practices, including reducing configuration differences between staging and production environments and strengthening validation of database endpoints used by internal workloads.

1. 10 décembre 2025 à 06:03 UTCresolved

   An unexpected behavior occurred in the REST API "GET /v3/job/result/{job_id}" which caused it to return only a partial set of results. This issue stemmed from an update to the job result download mechanism implemented around 2025/12/09 01:00 (UTC). The issue was resolved after a fix was applied around 2025/12/10 04:36(UTC). The affected API is used through the following methods: - Directly calling the REST API - Using functions in libraries (e.g., pytd) that reference job results - Toolbelt commands that refers to job results - Setting store_last_results:true in the td>:/td_run> operator in Treasure Workflows - Using the td_for_each>, td_wait> and td_wait_table>: operators in Treasure Workflows Unfortunately, we are unable to identify which API requests were affected. Please compare the number of results retrieved by your job with the download results to see if you were affected. We sincerely apologize for the inconvenience this has caused.

1. 5 décembre 2025 à 09:18 UTCinvestigating

   We are currently experiencing issues accessing Treasure Insights. Our investigation has identified that this is caused by an outage with a third-party service provider utilized by Treasure Insights. We are monitoring the situation and working with the provider to resolve the issue. We will provide updates as soon as more information becomes available.

2. 5 décembre 2025 à 09:22 UTCmonitoring

   The third-party service provider has implemented a fix. We are monitoring the results.

3. 5 décembre 2025 à 09:30 UTCresolved

   We confirmed the third-party service is now operational. The incident has been resolved.

1. 5 novembre 2025 à 03:49 UTCinvestigating

   We have encountered a temporary issue with the availability of Premium Audit Logs for Artificial Intelligence services (AI Agent Foundry and Audience Agent) during the period of November 4th 23:19:26 UTC to November 5th 00:57:55 UTC. While some data during this period may not have been captured, our engineering team is actively investigating the situation. We are taking all necessary steps to restore full service and ensure that all future logs are recorded without issue. We apologize for any inconvenience this may have caused and will keep you updated on our progress.

2. 5 novembre 2025 à 03:55 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 5 novembre 2025 à 07:58 UTCresolved

   Services have been restored to normal operations, and all of our systems are reporting healthy once again. If you observe any lingering issues, please connect with our support team, and we would be happy to help: https://docs.treasuredata.com/articles/#!pd/contacting-treasure-data-support

1. 20 octobre 2025 à 08:53 UTCinvestigating

   We are aware of an issue affecting log writing and reading for the Profile API in all regions. This is due to an incident with an upstream service. Our team is monitoring the provider's status. We will provide an update shortly.

2. 20 octobre 2025 à 10:15 UTCinvestigating

   We are also investigating reports indicating that this incident might be causing login errors for customers using SSO (Single Sign-On) to log into our service. Customers attempting a new login via SSO may be unable to access the service. We believe users who are already logged in (have an active session) and users logging in with methods other than SSO (e.g., username/password) are not affected by this login issue. We are working to confirm this.

3. 20 octobre 2025 à 15:09 UTCinvestigating

   Our upstream service provider is gradually recovering its services, and our services are gradually recovering too. SSO login is working fine, however profile API 1.0 is still recovering its service with latency. As the upstream service provider incident is still ongoing, you might still encounter unexpected errors or issues. We will closely monitoring our services and work with our upstream service provider.

4. 20 octobre 2025 à 18:53 UTCidentified

   We are continuing to work with our service provider to track this issue. Customers may continue to observe higher latency than normal and may notice delays in processing. We are monitoring the situation closely and are adding additional capacity in anticipation of a recovery. As this situation develops, we will keep you updated on any changes in expected behavior.

5. 20 octobre 2025 à 21:32 UTCresolved

   Delays should be improving for all customers, and services should be returning to normal. Given the similarity of the two issues, we'll continue tracking any concerns related to this interruption as part of the "[US Region] Issue Affecting Treasure Data Services" issue. For further updates, please track here: https://status.treasuredata.com/incidents/w7v5wtmkdllj If you experience continued issues specifically relating to our Profiles API or SSO Logins, please contact our support team: https://docs.treasuredata.com/articles/#!pd/contacting-treasure-data-support

1. 20 octobre 2025 à 08:27 UTCinvestigating

   We are currently investigating an issue originating from an upstream service provider used by our infrastructure. This may be affecting the normal operation of some Treasure Data services. We are working to determine the scope of the impact. Observed symptoms may include, but are not limited to, the failure of various jobs (such as Trino, Hive, Result Export, Import, and Custom Script execution) to start. Our team is actively monitoring the situation and working with the provider. We will provide further updates as more information becomes available.

2. 20 octobre 2025 à 15:05 UTCinvestigating

   Our upstream service provider is gradually recovering its services, and our services are gradually recovering too. Most of our Treasure Data services are back to normal except for Custom Script, autoML and realtime services such as profile API 1.0, and realtime 2.0. As the upstream service provider incident is still ongoing, you might still encounter unexpected errors or issues. We will closely monitoring our services and work with our upstream service provider.

3. 20 octobre 2025 à 18:49 UTCinvestigating

   We are continuing to monitor ongoing recovery efforts, and most of our systems remain operating. As the situation with our upstream provider develops we will react if we discover any new issues. At this time, we are observing delays in our systems, including Profile API 1.0 and Realtime 2.0. Requests are being processed as they have been received, but users may see a slowdown in results, and may notice delays when updating configurations or journeys. You may notice continued slower performance or unexpected errors. We are working with our service provider to address these issues and will provide an update with new information soon.

4. 20 octobre 2025 à 19:35 UTCmonitoring

   We are seeing continued recovery across our systems, and are currently working to process any buffered or delayed messages. Customers may continue to observe delays in data processing and may notice slower-than-usual processing of configuration changes. We expect these delays to decrease as our systems catch up. Our team is continuing to track recovery closely, and we'll inform you of any new developments.

5. 20 octobre 2025 à 21:42 UTCmonitoring

   Service levels continue to improve as upstream services become more stable. Users may still see processing delays, though those should be decreasing as we process the backlog of messages from this event. We are continuing to monitor our systems and deploy capacity as needed. We will update you with additional information as it develops.

6. 20 octobre 2025 à 23:15 UTCresolved

   Services have been restored to normal operations, and all of our systems are reporting healthy once again. If you observe any lingering issues, please connect with our support team, and we would be happy to help: https://docs.treasuredata.com/articles/#!pd/contacting-treasure-data-support

1. 15 octobre 2025 à 18:16 UTCinvestigating

   We are currently investigating an issue where some customers are experiencing intermittent “query expired” errors when retrieving segment counts in Audience Studio. In many cases, queries may succeed after a retry, but this behavior can impact the ability to view or use segment results reliably. Our engineering teams are actively investigating the root cause and working to mitigate the issue. We will provide updates here as soon as more information becomes available. In the meantime, affected users may be able to work around the issue by retrying the query after a short interval.

2. 16 octobre 2025 à 05:05 UTCmonitoring

   We've identified that an internal component between our query engine which extracts the number of records that match Segment rules and Audience Studio ran into a capacity issue during a specific time. We have increased the capacity and will continue to monitor the situation. If the issue does not reoccur by approximately 2025/10/17 01:00 (+00:00), we will consider this incident resolved and close this.

3. 17 octobre 2025 à 01:55 UTCresolved

   After a successful monitoring period, we can confirm that our fix is working and the issue is now resolved. Thank you for your patience.

1. 15 octobre 2025 à 02:05 UTCinvestigating

   We are currently experiencing an issue with email delivery for Treasure Data system emails, such as password resets. The affected email deliveries are: * Default email notification of Treasure Workflow * Password reset * New user invitation * Password change * Email address change * User lock notifications The following emails are NOT affected: * Email delivery with the mail>: operator of Treasure Workflow * Email delivery with Engage Studio Our team is actively working to resolve this issue. We sincerely apologize for any inconvenience or disruption this may cause.

2. 15 octobre 2025 à 02:52 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 15 octobre 2025 à 04:38 UTCmonitoring

   The issue has been addressed with an applied fix. We are currently monitoring the system to ensure the services are fully restored and stable. Thank you for your patience while we addressed this.

4. 15 octobre 2025 à 05:06 UTCresolved

   The issue has been fully resolved. Thank you for your patience.

1. 30 septembre 2025 à 03:37 UTCinvestigating

   We are currently investigating an issue where AI agents in the AI Agent Foundry may prematurely stop their response without providing a final conclusion, especially during their thinking process. This behavior does not generate an error message. Our initial findings show it is more likely to occur in agents handling long or extensive conversations, though we have not yet identified a specific threshold. Our engineering team is actively investigating the root cause. We will provide another update as soon as more information is available. We apologize for any inconvenience this may cause.

2. 30 septembre 2025 à 06:08 UTCidentified

   We have an update on the root cause of the issue causing AI agents to provide incomplete responses. Our investigation has found that when an agent uses its tools, the user's original prompt was being sent multiple times to the underlying AI model. This duplication caused the model to incorrectly process the tool results, leading it to return an empty response instead of a complete answer. The hotfix we are preparing will correct this behavior by ensuring the user's prompt is sent only once for each task. This will allow the AI to properly process all tool results and generate a complete, final response. We are working to deploy this fix as quickly as possible and will provide another update once it is ready. Thank you for your continued patience.

3. 30 septembre 2025 à 06:53 UTCmonitoring

   The hotfix for the incomplete agent responses has been deployed. This should prevent the duplicate prompt issue during tool use. We are now monitoring the platform to ensure everything is working as expected. We will resolve this incident once we've confirmed stability.

4. 30 septembre 2025 à 07:22 UTCresolved

   After a successful 30-minute monitoring period, we can confirm that our fix is working and the issue is now resolved. All AI agents are functioning as expected. Thank you for your patience.

1. 26 septembre 2025 à 19:12 UTCidentified

   We are currently experiencing delays in our Profile API replication pipeline in the Tokyo region. This issue began at approximately 13:00 UTC and is affecting all customers in this region. Impact: - Profile API responses may return stale data (up to several hours behind) - Lookup functionality remains available but data may be inconsistent Our engineering team is actively working on recovery. We estimate normal service will be restored within 8-10 hours. We will continue to provide updates as we make progress toward resolution.

2. 26 septembre 2025 à 23:02 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 26 septembre 2025 à 23:24 UTCresolved

   This incident has been resolved.

1. 24 septembre 2025 à 06:53 UTCresolved

   We experienced a partial issue on September 24th, between 01:55 and 02:40 UTC, where some users may have encountered incorrect permission errors when accessing their tables and databases in Hive and Trino. The issue was caused by a high load on our table API, which temporarily struggled to retrieve correct permission data. All underlying data remained secure and unaffected. The API load has returned to normal, and all services are operating as expected. If you had any jobs that failed with a permission error during this period, please try running them again. We apologize for any confusion this may have caused.

1. 18 août 2025 à 21:03 UTCinvestigating

   Treasure Data Insights is currently unavailable; we are investigating this issue.

2. 18 août 2025 à 21:49 UTCresolved

   The issue was resolved; it was linked to a vendor issue. The vendor has resolved the problem that was impacting TD Insights.