Tealium Outage History

Tealium is up right now

Tealium had 10 outages in the last 2 years totaling 236h 56m of downtime — averaging 0.4 incidents per month.

There were 10 Tealium outages since May 29, 2026 totaling 236h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tealium.com

Minor October 1, 2026

Apply button on custom value mapping in tags

Detected by Pingoru
Oct 01, 2026, 01:43 PM UTC
Resolved
Oct 01, 2026, 10:30 PM UTC
Duration
8h 47m
Affected: User InterfaceUser Interface (Publish)
Timeline · 3 updates
  1. identified Oct 01, 2026, 01:43 PM UTC

    Engineers have identified a problem whereby using the custom value mapping feature within a tag configuration leads to the 'apply' button being unavailable. The root cause has already been identified and developers are working on a fix.

  2. identified Oct 01, 2026, 02:42 PM UTC

    If you are encountering the problem with the custom value mapping, there is a workaround if you edit each Custom Value mapping and press "Done" without making any changes to the mapping. This re-enables the Apply button so that the Tag Mapping changes can be saved.

  3. monitoring Oct 01, 2026, 08:04 PM UTC

    Engineers have applied a fix and are monitoring functionality.

Read the full incident report →

Minor September 29, 2026

Delayed Connector Processing in AP-Southeast

Detected by Pingoru
Sep 29, 2026, 12:18 AM UTC
Resolved
Sep 29, 2026, 04:47 AM UTC
Duration
4h 28m
Affected: Cloud RegionsCloud Regions (Sydney (AP-Southeast))Server-Side Data Collection and ProcessingServer-Side Data Collection and Processing (Data Connectors)
Timeline · 3 updates
  1. investigating Sep 29, 2026, 12:18 AM UTC

    Engineers are investigating an issue which is causing some connector actions to be delayed.

  2. identified Sep 29, 2026, 12:28 AM UTC

    Engineers have identified the issue and are working on a fix.

  3. monitoring Sep 29, 2026, 12:47 AM UTC

    Engineers have applied a fix and are observing recovery. We will continue to monitor.

Read the full incident report →

Minor September 25, 2026

Delayed processing on connectors in US West region

Detected by Pingoru
Sep 25, 2026, 02:31 PM UTC
Resolved
Sep 29, 2026, 12:16 AM UTC
Duration
3d 9h
Affected: Cloud RegionsCloud Regions (Oregon (US-West))Server-Side Data Collection and ProcessingServer-Side Data Collection and Processing (Data Connectors)
Timeline · 2 updates
  1. investigating Sep 25, 2026, 02:31 PM UTC

    Engineers are investigating a problem which will be causing some connector actions to be delayed.

  2. monitoring Sep 25, 2026, 03:56 PM UTC

    Engineers have resolved the issue and will continue to monitor.

Read the full incident report →

Minor September 22, 2026

Advanced Javascript GitHub sync

Detected by Pingoru
Sep 22, 2026, 02:35 PM UTC
Resolved
Sep 23, 2026, 06:11 AM UTC
Duration
15h 36m
Affected: User InterfaceUser Interface (Publish)Client-Side mCDN Tag Delivery NetworkClient-Side mCDN Tag Delivery Network (Vendor Tag Delivery to Page)Client-Side mCDN Tag Delivery Network (utag.js Delivery to Page)
Timeline · 3 updates
  1. identified Sep 22, 2026, 02:35 PM UTC

    Engineers have identified an issue for customer using the Advanced Javascript extension with the GitHub sync feature. Some ASCII characters are being encoded incorrectly, causing the javascript to fail. Engineers have identified a code fix to resolve the issue. While the solution is being verified and released, any affected users can copy/paste the javascript from GitHub to the draft template in the TiQ user interface to get things back up and running as soon as possible. If you require further assistance please contact our Support team.

  2. identified Sep 22, 2026, 09:04 PM UTC

    Update: Potential Fix Being Tested The issue has now been consistently reproduced and an encoding mismatch in the GitHub sync path has been confirmed as the root cause. Engineering is testing a proposed code fix. Once validation and QA is completed, the fix will be released to production as quickly as possible. Until then, please do not trigger a GitHub sync or publish a GitHub-linked Advanced JavaScript extension. The previously communicated draft-copy workaround remains available for affected profiles. We will provide another update when the production release is completed.

  3. monitoring Sep 23, 2026, 03:09 AM UTC

    Fix has been deployed and engineers are monitoring.

Read the full incident report →

Minor September 16, 2026

Event Feed activity graph display

Detected by Pingoru
Sep 16, 2026, 08:05 AM UTC
Resolved
Sep 18, 2026, 04:22 PM UTC
Duration
2d 8h
Affected: User InterfaceUser Interface (Usage Reporting)
Timeline · 3 updates
  1. identified Sep 16, 2026, 08:05 AM UTC

    Engineers have identified a visual issue with the Event Feed activity graphs which causes a delay or in some cases for the graphs not to show any activity. There is no effect on event processing, just the graph in the user interface. We are working with the development team to identify the cause and restore normal operation.

  2. identified Sep 16, 2026, 04:14 PM UTC

    Engineers have identified the cause and are working on a fix.

  3. monitoring Sep 17, 2026, 05:44 AM UTC

    Engineers have applied the fix and are monitoring.

Read the full incident report →

Minor August 27, 2026

UI Login Impacted

Detected by Pingoru
Aug 27, 2026, 04:42 PM UTC
Resolved
Aug 27, 2026, 10:29 PM UTC
Duration
5h 46m
Affected: User InterfaceUser Interface (Login and Access)
Timeline · 2 updates
  1. investigating Aug 27, 2026, 04:42 PM UTC

    Engineers have identified an issue with login to the UI and are actively investigating.

  2. monitoring Aug 27, 2026, 05:29 PM UTC

    The issue affecting profile and version access has been identified and resolved. We are continuing to monitor.

Read the full incident report →

Minor August 21, 2026

Manage Templates Update Impacted

Detected by Pingoru
Aug 21, 2026, 05:09 AM UTC
Resolved
Aug 21, 2026, 09:33 AM UTC
Duration
4h 23m
Affected: User InterfaceUser Interface (Publish)Cloud RegionsCloud Regions (Hong Kong (AP-East))Cloud Regions (Tokyo (APAC-Northeast))Cloud Regions (Sydney (AP-Southeast))Cloud Regions (Germany (EU-Central))Cloud Regions (Ireland (EU-West))Cloud Regions (Singapore (AP-Southeast))Cloud Regions (Virginia (US-East))Cloud Regions (Oregon (US-West))Cloud Regions (Private Clouds)
Timeline · 2 updates
  1. investigating Aug 21, 2026, 05:09 AM UTC

    We have identified a minor issue with tag template updates in TealiumIQ and are investigating. As a precaution, we recommend holding off on template updates for now. We will share an update once it's resolved. We apologise for any inconvenience this may cause.

  2. monitoring Aug 21, 2026, 05:27 AM UTC

    Engineers have applied the fix and are monitoring.

Read the full incident report →

Minor July 15, 2026

CDW Data Sources Impacted

Detected by Pingoru
Jul 15, 2026, 07:59 PM UTC
Resolved
Jul 16, 2026, 03:42 PM UTC
Duration
19h 43m
Affected: Cloud RegionsCloud Regions (Hong Kong (AP-East))Cloud Regions (Tokyo (APAC-Northeast))Cloud Regions (Sydney (AP-Southeast))Cloud Regions (Germany (EU-Central))Cloud Regions (Ireland (EU-West))Cloud Regions (Singapore (AP-Southeast))Cloud Regions (Virginia (US-East))Cloud Regions (Oregon (US-West))Server-Side Data Collection and ProcessingServer-Side Data Collection and Processing (Cloud Delivery for Events)
Timeline · 2 updates
  1. identified Jul 15, 2026, 07:59 PM UTC

    We have identified an issue that may affect the ability to create new CDW Data Sources for customers in profiles with server-side concurrency or CloudStream. At this time, existing CDW Data Sources are not impacted. The risk is limited to the creation of new CDW Data Sources in concurrency or CloudStream enabled profiles only. As a precaution, please do not create any new CDW Data Sources until further notice. Engineers are actively working on a fix and will continue to provide updates as they become available. We apologize for any inconvenience. Please reference status.tealium.com for the latest updates.

  2. monitoring Jul 16, 2026, 12:54 PM UTC

    A fix has been applied and validated. Impacted customers are unblocked from creating CDW Data Sources.

Read the full incident report →

Minor July 13, 2026

Issues Updating Existing Moments API Engine Settings

Detected by Pingoru
Jul 13, 2026, 03:17 AM UTC
Resolved
Jul 13, 2026, 05:31 PM UTC
Duration
14h 13m
Affected: User InterfaceUser Interface (Publish)Cloud RegionsCloud Regions (Hong Kong (AP-East))Cloud Regions (Tokyo (APAC-Northeast))Cloud Regions (Sydney (AP-Southeast))Cloud Regions (Germany (EU-Central))Cloud Regions (Ireland (EU-West))Cloud Regions (Singapore (AP-Southeast))Cloud Regions (Virginia (US-East))Cloud Regions (Oregon (US-West))Server-Side Data Access and StorageServer-Side Data Access and Storage (Moments API)
Timeline · 2 updates
  1. identified Jul 13, 2026, 03:17 AM UTC

    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.

  2. monitoring Jul 13, 2026, 05:12 PM UTC

    Engineers have deployed a fix and will continue to monitor.

Read the full incident report →

Minor May 29, 2026

Issue with Load Order Manager in TiQ

Detected by Pingoru
May 29, 2026, 04:02 PM UTC
Resolved
May 30, 2026, 05:57 PM UTC
Duration
1d 1h
Affected: User InterfaceUser Interface (Login and Access)Cloud RegionsCloud Regions (Private Clouds)
Timeline · 3 updates
  1. identified May 29, 2026, 04:02 PM UTC

    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.

  2. identified May 29, 2026, 07:55 PM UTC

    Our engineering team has identified the issue and are working on implementing a fix.

  3. monitoring May 29, 2026, 11:50 PM UTC

    Engineers have released the fix and services are working as expected. We will continue to monitor.

Read the full incident report →