Triton Digital Platform Status

Identified: We have identified the necessary fix to implement in Station Manager. Once the bug fix goes through our QA phase, a new version of SM will be released on our User Guide pages. We will update this incident with the necessary information at that time. More information to come.

Investigating: We have deployed a partial fix for the issue in our back end services. This should remove the need for downgrading to Station Manager 5.2.6. A coming update to Station Manager will further improve things. More information to come.

Investigating: We are investigating a previously undiscovered issue in Station Manager 5.5. Under very rare circumstances, Station Manager version 5.5 may encounter an error while trying to interact with Triton Backend Services, resulting in the program becoming unable to initiate streaming of stations. Users will then see the following error in the Station Manager logs: “Error - Module=SmIdProvider : Problem communicating with dedup service”. If you encounter this error, we advise to downgrade the installed version of Station Manager to version 5.2.6 (available here: https://help.tritondigital.com/docs/sm-release-notes). Make sure to create a backup of the configuration files , uninstall SM and install version 5.2.6. Contact Customer Support ([email protected]) should you require help. Pleas note that we do not advise a preemptive downgrade. SM 5.5 contains several important features and fixes which SM 5.2.6 does not have. A downgrade should only be applied if the aforementioned error is present and stations are not streaming. Our team is currently working on a hotfix. More information to come.

Identified: We have identified the necessary fix to implement in Station Manager. Once the bug fix goes through our QA phase, a new version of SM will be released on our User Guide pages. We will update this incident with the necessary information at that time. More information to come.

Investigating: We have deployed a partial fix for the issue in our back end services. This should remove the need for downgrading to Station Manager 5.2.6. A coming update to Station Manager will further improve things. More information to come.

Investigating: We are investigating a previously undiscovered issue in Station Manager 5.5. Under very rare circumstances, Station Manager version 5.5 may encounter an error while trying to interact with Triton Backend Services, resulting in the program becoming unable to initiate streaming of stations. Users will then see the following error in the Station Manager logs: “Error - Module=SmIdProvider : Problem communicating with dedup service”. If you encounter this error, we advise to downgrade the installed version of Station Manager to version 5.2.6 (available here: https://help.tritondigital.com/docs/sm-release-notes). Make sure to create a backup of the configuration files , uninstall SM and install version 5.2.6. Contact Customer Support ([email protected]) should you require help. Pleas note that we do not advise a preemptive downgrade. SM 5.5 contains several important features and fixes which SM 5.2.6 does not have. A downgrade should only be applied if the aforementioned error is present and stations are not streaming. Our team is currently working on a hotfix. More information to come.

Resolved: This incident has been resolved.

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

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

Investigating: We are currently aware of an issue affecting Omny Podcast Embeds, which are not functioning as expected when accessed through the Mozilla Firefox browser.

Clients and end users accessing Omny embedded podcast players via Firefox may experience failures in player playback functionality, resulting in Error Code 4.

Resolved: This incident is considered resolved.

Monitoring: A fix has been applied. Manadge UI is once again allowing users to log in and is displaying data properly. We are monitoring the situation closely.

Investigating: We are investigating an issue preventing users from logging into the Manadge UI. Our team is actively working on a solution. Note that this incident is not affecting programmatic ad delivery. More information come.

Resolved: This incident has been resolved.

Identified: We are continuing to work on a fix for this issue.

Identified: Beginning January 10th 2026, the query parameter DIST was lost in the chain during migration development work that impacted Podcast Metric.  Reporting of this parameter (DIST) was blocked in Podcast Metrics.

The work has been completed to fix this issue to correctly parse this field from the logs to report in Podcast Metrics.

Data was not be repaired for old logs, the fix impacted new logs only.  We will not re-normalize the past data.

Resolved: We encountered an issue where the data gathering mechanism for Live Analytics Realtime Listening did not update the graphs between 04:15 UTC and 05:35 UTC today. Users looking at this period will see the same values displayed in the graphs for this period, resulting in a "flat line" in the graph. Due to the nature of these mechanisms, we are unable to correct the graphs for this period. Please use Totally Measurement Explore data for stats as this data was unaffected. This incident is considered resolved.

Identified: We have identified the necessary fix to implement in Station Manager. Once the bug fix goes through our QA phase, a new version of SM will be released on our User Guide pages. We will update this incident with the necessary information at that time. More information to come.

Investigating: We have deployed a partial fix for the issue in our back end services. This should remove the need for downgrading to Station Manager 5.2.6. A coming update to Station Manager will further improve things. More information to come.

Investigating: We are investigating a previously undiscovered issue in Station Manager 5.5. Under very rare circumstances, Station Manager version 5.5 may encounter an error while trying to interact with Triton Backend Services, resulting in the program becoming unable to initiate streaming of stations. Users will then see the following error in the Station Manager logs: “Error - Module=SmIdProvider : Problem communicating with dedup service”. If you encounter this error, we advise to downgrade the installed version of Station Manager to version 5.2.6 (available here: https://help.tritondigital.com/docs/sm-release-notes). Make sure to create a backup of the configuration files , uninstall SM and install version 5.2.6. Contact Customer Support ([email protected]) should you require help. Pleas note that we do not advise a preemptive downgrade. SM 5.5 contains several important features and fixes which SM 5.2.6 does not have. A downgrade should only be applied if the aforementioned error is present and stations are not streaming. Our team is currently working on a hotfix. More information to come.

Resolved: This incident has been resolved.

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

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

Investigating: We are currently aware of an issue affecting Omny Podcast Embeds, which are not functioning as expected when accessed through the Mozilla Firefox browser.

Clients and end users accessing Omny embedded podcast players via Firefox may experience failures in player playback functionality, resulting in Error Code 4.

Resolved: This incident is considered resolved.

Monitoring: A fix has been applied. Manadge UI is once again allowing users to log in and is displaying data properly. We are monitoring the situation closely.

Investigating: We are investigating an issue preventing users from logging into the Manadge UI. Our team is actively working on a solution. Note that this incident is not affecting programmatic ad delivery. More information come.

Resolved: This incident has been resolved.

Identified: We are continuing to work on a fix for this issue.

Identified: Beginning January 10th 2026, the query parameter DIST was lost in the chain during migration development work that impacted Podcast Metric.  Reporting of this parameter (DIST) was blocked in Podcast Metrics.

The work has been completed to fix this issue to correctly parse this field from the logs to report in Podcast Metrics.

Data was not be repaired for old logs, the fix impacted new logs only.  We will not re-normalize the past data.

Resolved: We encountered an issue where the data gathering mechanism for Live Analytics Realtime Listening did not update the graphs between 04:15 UTC and 05:35 UTC today. Users looking at this period will see the same values displayed in the graphs for this period, resulting in a "flat line" in the graph. Due to the nature of these mechanisms, we are unable to correct the graphs for this period. Please use Totally Measurement Explore data for stats as this data was unaffected. This incident is considered resolved.

Identified: We have identified the necessary fix to implement in Station Manager. Once the bug fix goes through our QA phase, a new version of SM will be released on our User Guide pages. We will update this incident with the necessary information at that time. More information to come.

Investigating: We have deployed a partial fix for the issue in our back end services. This should remove the need for downgrading to Station Manager 5.2.6. A coming update to Station Manager will further improve things. More information to come.

Investigating: We are investigating a previously undiscovered issue in Station Manager 5.5. Under very rare circumstances, Station Manager version 5.5 may encounter an error while trying to interact with Triton Backend Services, resulting in the program becoming unable to initiate streaming of stations. Users will then see the following error in the Station Manager logs: “Error - Module=SmIdProvider : Problem communicating with dedup service”. If you encounter this error, we advise to downgrade the installed version of Station Manager to version 5.2.6 (available here: https://help.tritondigital.com/docs/sm-release-notes). Make sure to create a backup of the configuration files , uninstall SM and install version 5.2.6. Contact Customer Support ([email protected]) should you require help. Pleas note that we do not advise a preemptive downgrade. SM 5.5 contains several important features and fixes which SM 5.2.6 does not have. A downgrade should only be applied if the aforementioned error is present and stations are not streaming. Our team is currently working on a hotfix. More information to come.

Resolved: This incident has been resolved.

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

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

Investigating: We are currently aware of an issue affecting Omny Podcast Embeds, which are not functioning as expected when accessed through the Mozilla Firefox browser.

Clients and end users accessing Omny embedded podcast players via Firefox may experience failures in player playback functionality, resulting in Error Code 4.

Resolved: This incident is considered resolved.

Monitoring: A fix has been applied. Manadge UI is once again allowing users to log in and is displaying data properly. We are monitoring the situation closely.

Investigating: We are investigating an issue preventing users from logging into the Manadge UI. Our team is actively working on a solution. Note that this incident is not affecting programmatic ad delivery. More information come.

Resolved: This incident has been resolved.

Identified: We are continuing to work on a fix for this issue.

Identified: Beginning January 10th 2026, the query parameter DIST was lost in the chain during migration development work that impacted Podcast Metric.  Reporting of this parameter (DIST) was blocked in Podcast Metrics.

The work has been completed to fix this issue to correctly parse this field from the logs to report in Podcast Metrics.

Data was not be repaired for old logs, the fix impacted new logs only.  We will not re-normalize the past data.

Resolved: We encountered an issue where the data gathering mechanism for Live Analytics Realtime Listening did not update the graphs between 04:15 UTC and 05:35 UTC today. Users looking at this period will see the same values displayed in the graphs for this period, resulting in a "flat line" in the graph. Due to the nature of these mechanisms, we are unable to correct the graphs for this period. Please use Totally Measurement Explore data for stats as this data was unaffected. This incident is considered resolved.