65 recorded Triton Digital incidents since December 2025, with official updates, affected components, duration and resolution information.
We are currently investing an issue impacting ondemand ad delivery. More information to come.
We have identified a problem with our deal synchronisation mechanism with The Trade Desk. Deals created since August 20th are not syncing with The Trade Desk and therefore will not become active for delivery. We have contacted the DSP and are awaiting new authorization. Existing deals are unaffected. More information to come.
A fix was applied to our synchronization mechanism with The Trade Desk. Deals are once again sycning normally. All deals created during the incident have now properly synced to The Trade Desk. This incident is considered resolved.
We are currently investigating an issue impacting Manadge (TAP Programmatic Analytics Dashboard). The Deal ID is not available as a filter. This can disrupt Dashboard already created that were filtered by Deal ID. More information to come.
We have identified an issue with the upload mechanism in Player Web Admin where users are unable to upload new imagery to be displayed on their Triton V4 Player. Existing imagery is unaffected. We are actively looking for a solution. More information to come.
Our team has applied mitigation measures and have fixed the issue. Clients are once again able to upload new and manage Player V4 imagery in Player Web Admin as normal. This incident is considered resolved.
We are aware of an issue affecting the performance of our Advertising Services, which may result in delayed responses or, in some cases, failed requests. Our team is actively investigating the issue and working to identify the root cause. We will provide further updates as more information becomes available.
This incident has been resolved and we are continuing to monitor.
A fix has been implemented and we are monitoring the situation
This incident is considered resolved.
We are investigating an issue with the Now Playing (or "Song History") service API where no songs are returned when a query is made. This may impact certain players using this API to display currently playing songs and also players using the API to display past songs. Live song information via cue points are not affected by this incident. More information to come.
A fix has been applied and the API is now returning data as normal. We are actively monitoring the situation. More information to come.
This incident is resolved and a fix has been applied to the service via a software update.
We are aware of an issue affecting the performance of our Playing Services, which may result in delayed responses or, in some cases, failed requests. Our team is actively investigating the issue and working to identify the root cause. We will provide further updates as more information becomes available.
We are continuing to investigate this issue.
We identified a potential root cause and have taken actions to mitigate it. Our services are back to normal operational state and we will keep monitoring and investigating our services closely over the next 12 hours. Meanwhile, we can share that the overall effect has been quite limited for listeners as we have a total amount of concurrent listeners on the platform inline with the number we had last week at the same time.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident is resolved. The services ran smoothly over the last ~10 hours.
We are currently investigating an issue impacting the data flow, where TAP UI is showing incorrect impressions numbers for some flights. There is no data loss. The ad delivery is not impacted. More information to come.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of requests to the now playing service failing. We are are actively investigating
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with our Cue Point Monitoring service. As a result, some metadata alerts may not be sent. We'll keep you posted as we learn more.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with our Cue Point Monitoring service. As a result, some metadata alerts may not be sent. If you receive any support cases related to missing metadata alerts, it's likely connected to this . We'll keep you posted as we learn more
We are investigating an issue with the Omny UI where users are presented with a Server Error when trying to access Omny. More information to come.
The issue has been confirmed to also affect to the Omny Management API as well as other Omny APIs, Omny Recording Agent, Omny.fm and Omny players in addition to the Omny management portal. Our team has determined the issue relies with an Azure component. We are in contact with Azure support to resolve the issue. More information to come.
Azure (Microsoft) have confirmed that this incident is a result of a major networking issue that they are experiencing in the Western USA. We are attempting to mitigate the impact of their issues and are following their progress in resolving their issues. More information to come.
Microsoft are continuing their efforts to identify the root cause of their issue. We are actively following their efforts. More information to come.
Microsoft identified the issue to a deployment that they recently made. They have rolled back that deployment and service has now returned to normal. Omny services are now available for client use and operating under normal conditions. We will monitor the situation closely.
Microsoft Azure has remained stable and no further effects of their outage has been observed on the Omny platform ad services. This incident is considered resolved.
We are currently investigating an issue where emails for the Manadge scheduled exports are not being sent since July 16th. More information to come
We have identified the cause of the issue. A proposed fix is currently in review. We are hopeful to have a resolution June 24th 2026. More information to come.
Our fix requires more effort than anticipated. We are hopeful to have a resolution early next week. More information to come.
QA was completed on the fix. We will be deploying the fix Monday. More information to come.
Our fix has been deployed. Scheduled exports will now be sent by email normally. Scheduled exports that were not sent during this incident cannot be resent. We advise our clients to manually export the scheduled reports they didn't receive. This incident is considered resolved.
We are currently investigating an issue affecting the Content Management tab in the UI, where users may encounter 503 errors. Our team is actively working to identify the root cause. We will provide additional updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident is considered resolved.
We are currently investigating an issue with TAP Creative where after publishing the creative you will see a warning message "Creative is not live". As a workaround, you can add a space character to the Ad Group name in the creative and republish the creative.
This incident has now been resolved.
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.
This incident is considered resolved.
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.
