Triton Digital outage history

We are currently investigating an issue impacting Manadge (TAP Programmatic Analytics Dashboard), where users are getting a 404 - Not found error when trying to access the platform. More information to come.

A fix has been implemented and we are monitoring the results. More information to come.

We are currently investigating an issue affecting Omny Studio platform. We will provide additional updates as soon as more information becomes available.

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

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

Omny platform accès has remained stable and under normal operating parameters. This incident is considered resolved.

We are currently investigating an issue affecting WCM Realtime Monitoring, where some users may encounter a “No content to display” message.

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

No further indication of problems with access to Realtime statistics has been observed. Note that this incident only affected the UI and not the statistics themselves. This incident is considered resolved.

We are currently investigating an issue impacting the User Management UI when opening the Content Access section, where some requests may experience increased latency or occasional timeouts..  More information to follow.

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

This issue has been resolved.

We detected an issue with Webcast Metrics Realtime listening data for 3rd party log collected publishers. There is a data gap from June 29 at 8:23 PM UTC to June 30 at 10:30 AM UTC. Only realtime data was affected and it cannot be restored.

The data will be available in Webcast Metrics Explore, but the gap will be visible in Webcast Metrics - Realtime Listening.

We are currently investigating an issue with our Spot Converter API. We are experiencing high error rates which may affect conversions of impressions to spots on our services. More information to come.

We are still investigating an issue with our Spot Converter API. We are experiencing high error rates, and currently cannot convert from CPS goal to impressions, which affects the following services: - Live Ad Delivery: New spot flights will not deliver - Live Ad Delivery: Any updated spot flights will not have their goal updated - Forecasting: Any spots queries will return None More information to come.

The issue has been identified and a fix is being implemented in our spot converter service. More information to come when the fix is deployed.

A fix has been deployed and we are no longer experiencing errors in our spot converter service. We will continue to monitor the situation closely.

This incident has been resolved.

We are investigating an issue that is preventing users from viewing or adding new Stream Access Control rules in Console UI. This incident seems to only affect the UI. Existing SAC rules should function normally to restrict stream access. More information to come.

Please note that this incident is only affecting Default rules at the Broadcaster and Market levels. Users can still create default and Scheduled rules at Station level. More information to come.

A fix has been deployed. Users are once again able to view and manage Default rules at Broadcaster and Market levels. We will monitor the situation closely.

This incident is considered resolved.

We are currently investigating reports of slowness when uploading new clips to the Omny platform. More information will follow.

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

The system is stable and we are no longer seeing issues with the upload mechanism. This incident is considered resolved.

We are currently investigating an issue impacting TAP Programmatic Analytics Dashboard. Any deal with the start date on or after 06/08 1AM UTC will not display any Impressions in Manadge. The delivery is not being impacted. More information to come.

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

This incident is considered resolved.

We are currently investigating an issue where deals with the start date on or after 06/01 are not displayed in Manadge (TAP Programmatic Analytics Dashboard). This is only impacting Manadge reporting platform. Bid requests are being sent and most of the deals seem to have already started delivering. More information to come.

The team has implemented the fix and the deals are now being displayed in Manadge. We consider the incident as resolved.

We are currently investigating an issue where users are unable to access (login) Manadge. The issue is also preventing the Manadge API from returning data. Note that this incident does not affect programmatic ad delivery. More information to come.

A fix has been applied. Manadge is once again reachable. Data will also be returned from the Manadge API. We will be monitoring the situation closely.

This incident has been resolved.

We are currently investigating errors loading synchronization data of deals on TAP Programmatic. More information to come.

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

This incident has been resolved

We are currently investigating a data processing issue resulting in data being late in Manadge. Users will see no data since 12:00 (noon) UTC. More information to follow.

The data pipeline was restored. Missing data has been reprocessed and is now available in the Manadge. Data is now flowing normally. This incident is considered resolved.

We are currently experiencing an issue in the Forecasting Reach Extension Report where Inventory Owner names are not being displayed. This is not affecting reach extension inventory results, or the other Forecasting endpoints. Our team is implementing a fix to this issue. More information to come.

A fix has been implemented and the issue should no longer occur. We are monitoring the results.

This incident has been resolved and the issue is no longer occurring.

We're aware that there are processing delays in Omny Studio and we're currently investigating.

We are continuing to investigate this issue.

This incident has been resolved.

We are investigating an issue in TAP Explore where users selecting the "Segment PoP" Report Type will cause the UI to go blanc. Our team is actively looking on restoring functionality. More information to come.

The origin of the issue was identified. Our team is working on a fix. More information to come.

A fix has been deployed. Users should now see TAP Explore behave normally. We will be monitoring the situation closely.

This incident is considered resolved.

We are currently investigating reports of some users having issues accessing to Metrics UI (Webcast Metrics, Podcast Metrics and TAP Explore). As a workaround we recommend clearing your browser cache and temporary files and/or use incognito/Private mode. More information to come.

The issue was found to be an unexpected side effect of a deployment made as part of the recent Metrics UI maintenance for 2026-05-05 at 07:30 PM UTC (https://tritonstatus.statuspage.io/incidents/p18m3qp182hm). A rollback has been applied which has restored functionality. Users still seeing a blank page are instructed to clear their browser cache and log back into Metrics/Tap. We are monitoring the situation closely.

This incident is considered resolved.

We are currently investigating a network instability affecting our London datacenter. Listener experience and ad delivery might be impacted. We will provide further updates as more information becomes available. Thank you for your patience.

The issue was identified to be a faulty network equipment. The equipment was replaced and our team is currently working on restoring connectivity and services to the data centre. More information to come.

Connectivity and services have now been fully restored to our London data centre. This incident is considered resolved.

We are currently monitoring an issue where users might have experienced momentarily where impression data was not displayed in campaign/flight tables in TAP UI. This was not impacting delivery.

This incident is now considered resolved.

On May 1st between 18:55 and 19:55 UTC, our North American on demand ad servers experienced an abnormally high level of requests. This resulted in a temporary inability for our system to respond to On Demand Ad requests during this period. Ad Requests made to our other endpoints around the world were not affected. Our teams have mitigated the issue and we are monitoring the situation closely.

No further impact has been observed. This incident is considered resolved.