Status History
June 2024
- Upcoming Scheduled Maintenance - Infrastructure Upgrade
June 28, 2024 8:27AM UTC
Upcoming Scheduled Maintenance - Infrastructure UpgradePlanned Maintenance
Description
Tealium will be conducting a scheduled infrastructure upgrade maintenance in the US East Region starting Friday, June 28, 2024 at 6AM UTC. We expect no disruption to data collection and data processing. Please reference http://status.tealium.com for the latest updates. For more information, or if you have any questions, please contact your customer success manager.
Components
Cloud Regions, Server-Side Data Collection and Processing, Server-Side Data Access and Storage, Server-Side Machine Learning
Schedule
June 28, 2024 6:00AM - June 28, 2024 12:00PM UTC
June 28, 2024 6:00AM UTC[Update] Engineers started maintenance jobJune 28, 2024 8:27AM UTC[Update] The maintenance job is now complete.
- Server-side user interface not loading for private cloud systems
June 24, 2024 4:25PM UTC
Server-side user interface not loading for private cloud systemsFully Operational
Incident Status
Fully Operational
Components
User Interface, Cloud Regions
June 21, 2024 3:21PM UTC[Investigating] Server-side user interface is returning a blank screen for private cloud customers. Engineers are investigating.June 21, 2024 3:23PM UTC[Investigating] Server-side user interface is returning a blank screen for private cloud customers. Engineers are investigating.June 21, 2024 4:44PM UTC[Monitoring] Server-Side has been restored for all Private Clouds, we will monitor.June 24, 2024 4:25PM UTC[Resolved] Incident has been resolved and all services are working as expected.
- Latency in Data Access in US East
June 21, 2024 12:09PM UTC
Latency in Data Access in US EastDegraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Client-Side CDN Regions, Server-Side Data Access and Storage
June 21, 2024 10:44AM UTC[Identified] Engineers have identified that there is increased latency in data being sent to Data Access (AudienceDB & EventDB) in the US East region. The issue has been identified and is being worked on.June 21, 2024 12:09PM UTC[Resolved] The latency has been resolved and data access is back to normal.
- Connector action backlog
June 17, 2024 8:11AM UTC
Connector action backlog Degraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Data Collection and Processing
June 17, 2024 3:46AM UTC[Investigating] Some connector actions may be delayed due to processing backlog in the AP South East 2 (Sydney) region.June 17, 2024 6:58AM UTC[Monitoring] Issue is identified and engineers have applied a fix and are monitoring.June 17, 2024 8:11AM UTC[Resolved] Incident has been resolved. Monitoring complete with no additional occurrence.
- Planned Maintenance affecting Audience Sizing & Audience Discovery Jobs in eu-west-1 (Ireland)
June 16, 2024 3:11AM UTC
Description
Planned maintenance is required on the database cluster which processes Audience Sizing and Audience Discovery jobs in the eu-west-1 (Ireland) region. During this window, jobs will fail to execute properly. Upon completion of the maintenance, please re-run any jobs which ran and failed during the maintenance period. Historical and incoming data will be unaffected. The Maintenance is expected to last for 3 hours between 2024-06-16 01:00 UTC - 2024-06-16 04:00 UTC.
Components
Cloud Regions, Server-Side Data Collection and Processing
Schedule
June 16, 2024 1:00AM - June 16, 2024 4:00AM UTC
June 16, 2024 1:00AM UTC[Update] Maintenance startedJune 16, 2024 3:11AM UTC[Update] Maintenance is now complete.
- Connector action backlog
June 13, 2024 3:47PM UTC
Connector action backlogDegraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Data Collection and Processing
June 13, 2024 12:22PM UTC[Identified] Some connector actions may be delayed due to processing backlog in the EU-central region. Engineers have identified the cause and are working to remediate the issue.June 13, 2024 1:20PM UTC[Monitoring] The incident has been resolved. We will continue to monitor.June 13, 2024 3:47PM UTC[Resolved] Incident has been resolved. Monitoring complete with no additional occurrence.
- Potential delays to Visitor processing in AP-SOUTHEAST-2 (Sydney)
June 8, 2024 4:50AM UTC
Potential delays to Visitor processing in AP-SOUTHEAST-2 (Sydney)Degraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Data Collection and Processing
June 8, 2024 1:00AM UTC[Investigating] Our on-call team have noticed an increase in Visitor Processing within ap-southeast-2 (Sydney) which might result in delays to Visitor processing time. An investigation is underway.June 8, 2024 1:37AM UTC[Monitoring] Delays are cleared. We will continue to monitor Processing progress.June 8, 2024 4:50AM UTC[Resolved] Delays all gone.
- Connector action backlog
June 7, 2024 7:42PM UTC
Connector action backlogDegraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Data Collection and Processing
June 7, 2024 12:38PM UTC[Identified] Some connector actions may be delayed due to processing backlog in the EU-central region. Engineers have identified the cause and are working to remediate the issue.June 7, 2024 7:42PM UTC[Resolved] Delays have been processed and response times have returned to normal levels.
- Predict Attribute Enrichments Impacted in EU Central Region
June 7, 2024 6:20PM UTC
Predict Attribute Enrichments Impacted in EU Central RegionDegraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Machine Learning
June 7, 2024 1:59AM UTC[Investigating] Engineers have detected degraded performance with Predict attribute enrichments in EU central Region. We are actively investigating.June 7, 2024 2:50AM UTC[Monitoring] Engineers have taken action to resolve the processing lag, and the system is returning to healthy state. We will continue to monitor.June 7, 2024 6:20PM UTC[Resolved] The issue has been resolved.
- Connector action backlog
June 6, 2024 5:11PM UTC
Connector action backlogDegraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Data Collection and Processing
June 6, 2024 12:31PM UTC[Identified] Some connector actions may be delayed due to processing backlog in the EU-central region. Engineers have identified the cause and are working to remediate the issue.June 6, 2024 5:11PM UTC[Resolved] This issue has been resolved.
- UI not loading
June 6, 2024 2:10AM UTC
UI not loadingFully Operational
Incident Status
Fully Operational
Components
User Interface
June 6, 2024 1:00AM UTC[Investigating] Problems during weekly deployment rendering the UI unable to load post login,June 6, 2024 2:10AM UTC[Resolved] Deployment updated
- Potential delays to Connector processing in EU-Central
June 6, 2024 12:58AM UTC
Potential delays to Connector processing in EU-CentralDegraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Data Collection and Processing
June 5, 2024 9:50AM UTC[Identified] Our on-call team have noticed an increase in Connector retries within eu-central-1 (Frankfurt) which might result in delays to Connector processing time. An investigation is underway.June 6, 2024 12:58AM UTC[Resolved] This issue has been resolved.
- EventStream Connectors potentially delayed in EU Central
June 4, 2024 5:16PM UTC
EventStream Connectors potentially delayed in EU CentralDegraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Data Collection and Processing
June 4, 2024 12:41PM UTC[Identified] Engineers have identified a sudden increase in volume that might result in EventStream connectors being delayed in EU Central (Frankfurt). The on-call team is adjusting capacity in the region and continuing to monitor.June 4, 2024 3:37PM UTC[Monitoring] Engineers have implemented a fix to resolve the issue and have observed a good recovery. We will continue to monitor.June 4, 2024 5:16PM UTC[Resolved] The region has been observed as healthy, this incident is now resolved.
May 2024
- Connector action backlog
May 30, 2024 8:32PM UTC
Connector action backlogDegraded Performance
Incident Status
Degraded Performance
Components
Cloud Regions, Server-Side Data Collection and Processing
May 30, 2024 11:58AM UTC[Identified] Some connector actions may be delayed due to processing backlog in the EU-central region. Engineers have identified the cause and are working to remediate the issue.May 30, 2024 3:56PM UTC[Monitoring] Engineers took action to resolve the delayed connector actions, and the backlog is now clear. We will continue to monitor.May 30, 2024 8:32PM UTC[Resolved] This issue has been resolved.
- AudienceDB and EventDB Impacted in N. Virginia
May 25, 2024 7:04AM UTC
AudienceDB and EventDB Impacted in N. VirginiaPartial Service Disruption
Incident Status
Partial Service Disruption
Components
Cloud Regions, Server-Side Data Access and Storage
May 23, 2024 6:51PM UTC[Identified] Tealium has identified issues with a subset of AudienceDB and EventDB clusters in the N. Virginia region. We are in the process of rolling out a fix. Queries may fail and take longer than usual to run and data will be delayed. Please reach out to your CS representative if you have any questions.May 23, 2024 11:20PM UTC[Identified] Update: Tealium engineers have identified the issue relating to our upstream cloud provider and have engaged their support. We are actively working with their engineers to restore services. We will provide updates as we receive more information and work towards a resolution.May 24, 2024 3:01AM UTC[Identified] Update: AudienceDB and EventDB cluster access and query execution has now been restored. Working with the provider to address the data latency.May 24, 2024 4:53PM UTC[Identified] Update: We are observing improvement to AudienceDB and EventDB data delivery for the subset of impacted customers. We are actively working with our provider for full data recovery.May 25, 2024 2:53AM UTC[Monitoring] Update: AudienceDB and EventDB are now restored. Services are fully operational. Engineers will continue to monitor.May 25, 2024 7:04AM UTC[Resolved] This incident is now resolved.
- Intermittent Publish Failures
May 20, 2024 7:51PM UTC
Intermittent Publish FailuresPartial Service Disruption
Incident Status
Partial Service Disruption
Components
User Interface
May 20, 2024 7:28PM UTC[Identified] Engineers have identified an issue with intermittent publish failures and are working to resolve the issue.May 20, 2024 7:51PM UTC[Resolved] Engineers have resolved the issue and publishing success rates have return to normal levels.
- ACTION NEEDED: Required updates to your Tealium Connector and File Imports IP Safelist(Whitelist)
May 20, 2024 5:48PM UTC
Description
Tealium’s infrastructure is being expanded to maintain seamless operations with increased server-side traffic. We are adding IP addresses to all of our data processing regions. If you are using safelists (also known as whitelists or allow lists) in outbound connectors, function actions, or file import (except S3), we ask that you include the new IP addresses. The additional IP addresses will be introduced on the following dates: Apr 29, 2024 - US – Oregon May 6, 2024 - EU (Ireland and Frankfurt) May 13, 2024 - APJ (Hong Kong, Sydney, Tokyo) May 20, 2024 - US – US East 1 To check on whether you are impacted by these changes please work with your network and/or security team to see if any of these existing IP addresses are currently configured and add any from the document linked below that are missing. 18.166.4.167 - ap-east-1 (Hong Kong) 13.112.219.50 - ap-northeast-1 (Tokyo, Japan) 52.62.159.75 - ap-southeast-2 (Sydney, Australia) 52.29.185.253 - eu-central-1 (Frankfurt, Germany) 54.229.215.104 - eu-west-1 (Dublin, Ireland) 3.210.6.72, 3.210.238.60, 107.23.142.239 - us-east-1 (Ashburn, Virginia) 50.18.192.141 - us-west-1 (San Jose, California) 44.238.18.189 - us-west-2 (Oregon) If you don’t find any of the above IP addresses configured in your systems, no further action is needed. Otherwise, refer to the following article to update your list of IPs: https://docs.tealium.com/server-side/administration/ip-allow-list/ Please contact Tealium Support for further help.
Components
Cloud Regions, Server-Side Data Collection and Processing
Schedule
April 29, 2024 5:00PM - May 20, 2024 5:00PM UTC
April 15, 2024 6:40PM UTC[Update] Please note that this will start in 14 days as per the schedule outlined.April 29, 2024 5:03PM UTC[Update] Additional IPs are now being added to our Oregon region. Update will be sent when this effort is complete.April 29, 2024 5:33PM UTC[Update] Additional IPs have successfully been added to our Oregon region and this activity is now complete. Next set of upgrades will be in our Ireland and Frankfurt regions on May 7. That maintenance was postponed by one day from its original date due to a bank holiday.May 7, 2024 9:01AM UTC[Update] Additional IPs are now being added to our Ireland and Frankfurt regions. An update will be sent when this effort is complete.May 7, 2024 9:29AM UTC[Update] Additional IPs have successfully been added to our Ireland and Frankfurt regions. This activity is now complete. Next set of upgrades will be in our Hong Kong, Sydney, and Tokyo regions on May 13.May 13, 2024 12:03AM UTC[Update] Additional IPs are now being added to our Hong Kong, Sydney, and Tokyo regions. Update will be sent when this effort is complete.May 13, 2024 12:43AM UTC[Update] Additional IPs have successfully been added to our Hong Kong, Sydney, and Tokyo regions. This activity is now complete. Next set of upgrades will be in our US East region on May 20.May 20, 2024 5:05PM UTC[Update] Additional IPs are now being added to our US East region. Update will be sent when this effort is complete.May 20, 2024 5:48PM UTC[Update] Additional IPs have successfully been added to our US East Region and this activity is now complete. All regions have now been successfully updated.
April 2024
- Anomalies in AudienceDB
April 23, 2024 4:15PM UTC
Anomalies in AudienceDBFully Operational
Incident Status
Fully Operational
Components
Cloud Regions, Server-Side Data Access and Storage
April 4, 2024 9:20PM UTC[Investigating] Our engineering team is investigating data anomalies for AudienceDB customers. The root cause of the concern has already been identified and a fix was deployed and validated in production to ensure service was restored. If and when we identify specific impacts to customers and their data we will provide updates.April 12, 2024 9:57PM UTC[Monitoring] Update to the data anomalies that were being investigated in AudienceDB - it has been confirmed that all visitor records from March 21st to April 4th do exist and are available in the database, however there is a possibility that some records may not be returned in the view of the data. We are continuing to monitor this and work with any customer who requires assistance.April 23, 2024 4:15PM UTC[Resolved] Customer Success will reach out to all impacted customers to work out a plan of action.
- TiQ Login Impacted
April 13, 2024 3:07PM UTC
TiQ Login ImpactedService Disruption
Incident Status
Service Disruption
Components
User Interface, Cloud Regions
April 12, 2024 9:45PM UTC[Investigating] We have identified an issue with TiQ login and are currently investigating.April 12, 2024 9:53PM UTC[Monitoring] The issue has been resolved, we are currently monitoring.April 13, 2024 3:07PM UTC[Resolved] The issue has been resolved, system has returned to normal
- Impacted CDN Delivery in China
April 11, 2024 3:59PM UTC
Impacted CDN Delivery in ChinaPartial Service Disruption
Incident Status
Partial Service Disruption
Components
Cloud Regions, Client-Side mCDN Tag Delivery Network
April 10, 2024 6:17PM UTC[Investigating] Engineers are investigating an issue with file delivery from the CDN in the China region.April 10, 2024 7:44PM UTC[Identified] Engineers have identified the issue and are working to resolve the problem. However, this may take several hours.April 11, 2024 3:01AM UTC[Monitoring] Engineers have resolved the issue and are now monitoring successful delivery.April 11, 2024 3:59PM UTC[Resolved] Issue has been resolved and services are working as expected.
Back to current status
Subscribe to receive status updates by email
Manage Existing SubscriptionCreate New Subscription
Subscribe to receive status updates by webhook
Each status update will POST a JSON payload to this URL
Email address for managing webhook
Manage Existing SubscriptionCreate New Subscription
Slack channel ID
Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL.
Example: https://app.slack.com/client/T04SJBK1C/C03SKGJ1P
Email address
Manage Existing SubscriptionCreate New Subscription