Historique des pannes de Tealium

1. 27 août 2026 à 22:20 UTCresolved

   27 août 2026 4:42PM UTC Enquête - Les ingénieurs ont identifié un problème de connexion à l'assurance-chômage et mènent une enquête active. 27 août 2026 5h29 Surveillance UTC - Le problème touchant l'accès au profil et à la version a été identifié et résolu. Nous continuons de surveiller. 27 août, 2026 10:20 UTC Résolue - Tous les services fonctionnent normalement.

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

1. 24 août 2026 à 08:58 UTCresolved

   24 août, 2026 8:55AM UTC Identification - Les ingénieurs ont identifié un problème de connexion à l'interface utilisateur. Ils travaillent sur la situation et la régleront dès que possible. 24 août, 2026 8:58AM UTC résolu - L'interface utilisateur est disponible et fonctionne à nouveau.

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

1. 21 août 2026 à 09:21 UTCresolved

   21 août 2026 5h09 UTC Enquête - Nous avons identifié un problème mineur avec les mises à jour du modèle de tag dans TealiumIQ et nous enquêtons. Par précaution, nous vous recommandons de ne pas tenir compte des mises à jour des modèles pour le moment. Nous partagerons une mise à jour une fois qu'elle sera résolue. Nous nous excusons pour tout inconvénient que cela peut causer. Le 21 août 2026 5h27 Surveillance UTC - Les ingénieurs ont appliqué le correctif et le surveillent. 21 août 2026 9h21 UTC résolu - C'est maintenant résolu.

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

1. 16 juillet 2026 à 15:31 UTCresolved

   15 juillet, 2026 7:59PM UTC Identifié - Nous avons identifié un problème qui pourrait affecter la capacité de créer de nouvelles sources de données CDW pour les clients dans des profils avec la concurrence côté serveur ou CloudStream. À l'heure actuelle, les sources de données CDW existantes ne sont pas touchées. Le risque est limité à la création de nouvelles sources de données CDW dans des profils compatibles ou compatibles avec CloudStream uniquement. Par précaution, ne créez aucune nouvelle source de données CDW avant d'être averti. Les ingénieurs travaillent activement sur un correctif et continueront de fournir des mises à jour à mesure qu'elles seront disponibles. Nous nous excusons pour tout désagrément. Veuillez consulter status.tealium.com pour les dernières mises à jour. 16 juillet, 2026 12:54PM UTC Surveillance - Un correctif a été appliqué et validé. Les clients touchés sont débloqués de créer des sources de données CDW. 16 juillet, 2026 3:31PM UTC Résolue - Cet incident est résolu.

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

1. 13 juillet 2026 à 17:27 UTCresolved

   July 13, 2026 3:17AM UTC Identified - We have identified an issue affecting Moments API where updates to existing engine settings may not persist after save and refresh, causing previous settings to remain in place. Data processing is not impacted, and new Moments API engines can still be created. Engineers are working on a fix and we will share additional updates as they become available. July 13, 2026 5:12PM UTC Monitoring - Engineers have deployed a fix and will continue to monitor. July 13, 2026 5:27PM UTC Resolved - Incident has been resolved. All systems are fully operational.

1. 8 juillet 2026 à 22:00 UTCresolved

   July 7, 2026 9:56PM UTC Scheduled - Tealium will be performing a scheduled maintenance upgrade on Tuesday, July 8, 2026 beginning at 2:00 PM PST (21:00 UTC). During this time period the UI and APIs may experience brief intermittent disruptions. Total downtime is expected to be under 10 minutes. Data collection and data processing will continue unaffected. Estimated completion time is 5:00 PM PST (00:00 UTC July 9th). We apologize for any inconvenience. Please reference status.tealium.com for the latest updates. For more information, or if you have any questions, please contact your customer success manager. July 8, 2026 9:00PM UTC Active - This maintenance is starting now. July 8, 2026 10:00PM UTC Completed - Maintenance is finished.

1. 8 juillet 2026 à 17:53 UTCresolved

   July 7, 2026 3:26AM UTC Scheduled - We will be performing maintenance in the us-east-1 region PC-CMSGOV beginning at 2026-07-08T15:00:00Z. During this time, Visitor Lookup and Visitor Deletion services may experience intermittent disruptions. We will work to minimize any impact and will provide updates as the maintenance progresses. July 8, 2026 5:29PM UTC Active - Planned maintenance is starting July 8, 2026 5:53PM UTC Completed - Planned maintenance has completed

1. 8 juillet 2026 à 17:25 UTCresolved

   July 7, 2026 3:25AM UTC Scheduled - We will be performing maintenance in the us-east-1 region PC-CVS beginning at 2026-07-08T15:00:00Z. During this time, Visitor Lookup and Visitor Deletion services may experience intermittent disruptions. We will work to minimize any impact and will provide updates as the maintenance progresses. July 8, 2026 5:25PM UTC Active - Planned maintenance started July 8, 2026 5:25PM UTC Completed - Planned maintenance has completed

1. 8 juillet 2026 à 16:30 UTCresolved

   July 6, 2026 5:42PM UTC Scheduled - We will be performing maintenance in the ap-southeast-2 region at 2026-07-09T02:00:00+10:00. During this time, Visitor Lookup and Visitor Deletion services may experience intermittent disruptions. We will work to minimize any impact and will provide updates as the maintenance progresses. July 8, 2026 3:37PM UTC Active - Planned Maintenance is starting July 8, 2026 4:30PM UTC Completed - Maintenance has completed

1. 8 juillet 2026 à 15:32 UTCresolved

   July 6, 2026 5:36PM UTC Scheduled - We will be performing maintenance in the ap-southeast-1 region at 2026-07-08T15:00:00Z. During this time, Visitor Lookup and Visitor Deletion services may experience intermittent disruptions. We will work to minimize any impact and will provide updates as the maintenance progresses. July 8, 2026 3:00PM UTC Active - visitor-api maintenance starting July 8, 2026 3:32PM UTC Completed - completed successfully

1. 6 juillet 2026 à 16:57 UTCresolved

   July 3, 2026 12:25AM UTC Scheduled - We will be performing maintenance in the ap-northeast-1 region at 16:00 UTC on 2026-07-06. During this time, Visitor Lookup and Visitor Deletion services may experience intermittent disruptions. We will work to minimize any impact and will provide updates as the maintenance progresses. July 6, 2026 4:00PM UTC Active - Started July 6, 2026 4:57PM UTC Completed - completed successfully

1. 6 juillet 2026 à 15:53 UTCresolved

   July 3, 2026 12:22AM UTC Scheduled - We will be performing maintenance in the ap-east-1 region at 15:00 UTC on 2026-07-06. During this time, Visitor Lookup and Visitor Deletion services may experience intermittent disruptions. We will work to minimize any impact and will provide updates as the maintenance progresses. July 6, 2026 3:52PM UTC Active - Completed July 6, 2026 3:53PM UTC Completed - Completed Successfully

1. 2 juillet 2026 à 09:16 UTCresolved

   July 1, 2026 8:48AM UTC Scheduled - We will be performing maintenance in the US region at 7 AM UTC on 2026-07-02. During this time, Visitor Lookup and Visitor Deletion services may experience intermittent disruptions. We will work to minimize any impact and will provide updates as the maintenance progresses. July 2, 2026 8:13AM UTC Active - work in progress July 2, 2026 9:16AM UTC Completed - Completed

1. 2 juillet 2026 à 01:30 UTCresolved

   July 1, 2026 12:12AM UTC Scheduled - We will be performing maintenance in the EU-WEST-1 region at 00:30 UTC on July 2, 2026. During this time, Visitor Lookup and Visitor Deletion services may experience intermittent disruptions. We will work to minimize any impact and will provide updates as the maintenance progresses. July 2, 2026 12:30AM UTC Active - Scheduled maintenance has started. July 2, 2026 1:30AM UTC Completed - The maintenance completedScheduled maintenance has been completed.

1. 3 juin 2026 à 09:00 UTCresolved

   June 2, 2026 10:00AM UTC Investigating - A production change led to failures for AudienceStore data processing. June 3, 2026 9:00AM UTC Resolved - Once identified, we immediately restored the change and services are fully operational.

1. 30 mai 2026 à 17:54 UTCresolved

   May 29, 2026 4:02PM UTC Identified - We have identified an issue with the Load Order Manager feature in TiQ that's causing a white screen to be shown in certain situations. Our on-call team is actively investigating. May 29, 2026 7:55PM UTC Identified - Our engineering team has identified the issue and are working on implementing a fix. May 29, 2026 11:50PM UTC Monitoring - Engineers have released the fix and services are working as expected. We will continue to monitor. May 30, 2026 5:54PM UTC Resolved - Incident has been resolved. All systems are fully operational.

1. 11 avril 2026 à 16:26 UTCresolved

   April 7, 2026 9:27PM UTC Scheduled - We will be performing scheduled database maintenance on Saturday, April 11th at 3:00 PM UTC. During this time, you may experience brief service interruptions. We have scheduled this work during a low-traffic window to minimize impact. We will provide updates if the schedule changes or if extended downtime is expected. April 11, 2026 4:26PM UTC Active - Maintenance started. April 11, 2026 4:26PM UTC Completed - Maintenance completed successfully.

1. 22 mars 2026 à 01:02 UTCresolved

   March 19, 2026 5:12AM UTC Scheduled - To improve platform stability, our engineers will be performing a scheduled maintenance against our caching infrastructure on Sunday, March 22nd, 2026, starting at 00:00 UTC. This maintenance is scheduled for a two-hour window. During this time, the Tealium UI login and access may experience intermittent disruptions. Tag Delivery and Event Collection will remain unaffected and fully functional during this time. We apologize for any inconvenience this may cause and will provide updates at https://status.tealium.com/ March 22, 2026 12:00AM UTC Active - Maintenance commenced. March 22, 2026 1:02AM UTC Completed - Maintenance completed successfully.

1. 12 mars 2026 à 15:29 UTCresolved

   March 1, 2026 2:21PM UTC Identified - We have been notified of an ongoing incident at one of our cloud service providers. This has resulted in disruption to services in our Dubai region. We are working closely with the provider and will provide updates as we receive them. March 1, 2026 2:27PM UTC Monitoring - Engineers have deployed mitigation steps and are observing signs of recovery. March 1, 2026 3:44PM UTC Monitoring - Our cloud service provider is still working on full recovery. We will provide more updates as we receive them. In the meantime, our engineers are continuing to apply mitigation steps to limit impact. March 1, 2026 6:15PM UTC Monitoring - Engineers have restored impacted services and completed processing of backlogs. We will provide further updates as they become available from our cloud service provider. March 2, 2026 8:59AM UTC Monitoring - Engineers have been alerted that the incident has reoccured and are working with the cloud provider to resolve the situation March 2, 2026 5:12PM UTC Identified - Engineers have identified issues with cross-region traffic hitting the Dubai server side collect endpoint and are applying mitigation steps to limit impact. March 2, 2026 6:53PM UTC Monitoring - We've applied mitigation steps to address cross region impact and will continue to monitor. March 4, 2026 4:45PM UTC Monitoring - The most recent updates from our cloud provider regarding the situation in Dubai continue to recommend switching services to alternative regions where possible. Their current focus is on restoring access to backup and migration services, which suggests that a full recovery may still be some time away. We have attempted to contact all impacted customers in the region, and in most cases have already made the necessary changes to move data processing to an alternative region. If you are using the Dubai region and have not received instructions for migrating, please contact your Customer Success Manager (CSM), who will be able to assist with the process. Mitigation steps for cross-region traffic to the Dubai server-side collect endpoint remain in place, and we are observing stable performance. March 12, 2026 3:29PM UTC Resolved - We remain in regular contact with the customers impacted in the me-central-1 (Dubai) region. Where possible, we have worked with them to migrate services to alternative regions and are actively backing up historical data as database services become available. Any further updates related to this incident will be communicated directly to affected customers.

1. 7 mars 2026 à 02:20 UTCresolved

   March 6, 2026 10:40PM UTC Investigating - An issue was identified affecting batch connector actions. The connector actions were delayed without data loss. March 7, 2026 2:20AM UTC Resolved - Batched connector actions have recovered. All systems fully operational.