Triton Digital Outage History

Started Mar 30, 2026, 07:29 PM UTC· resolved Mar 31, 2026, 04:35 PM UTC

1. identified Mar 30, 2026, 07:29 PM UTC

   As a result fo the Settings UI Maintenance that happened earlier today (https://tritonstatus.statuspage.io/incidents/tmbfgtrspjyz), Station Passwords (now called Station Keys) are now required to be case sensitive (as seen in the Common Assets UI). Any password having been previously entered in Station Manager with the wrong case (upper case / lower case) will need to be re-entered with the exact case as see in the new Common Assets UI. In such cases, stations may stop streaming if the password was not correctly input in Station Manager. Please consult our guide for accessing the Common Assets UI in Settings and managing your Station Keys: https://help.tritondigital.com/docs/radio-stations For any issues, please contact support at [email protected]

2. resolved Mar 31, 2026, 04:35 PM UTC

   Mitigation measures have been applied to existing stations that were no longer authenticating due to case sensitivity mismatches Station Keys. We advise our clients to consider reviewing their station keys according to their security policies. This incident is considered resolved.

Read the full incident report →

Started Mar 29, 2026, 08:46 AM UTC· resolved Mar 29, 2026, 09:34 AM UTC

1. investigating Mar 29, 2026, 08:46 AM UTC

   We are experiencing Omny issues that's causing functionality issues including uploading files.

2. investigating Mar 29, 2026, 08:51 AM UTC

   We are experiencing issues in Omny which leads to behavior with users being unable to upload files

3. investigating Mar 29, 2026, 08:58 AM UTC

   Our team has observed an issue in Omny that could lead to behaviors such as uploading issues. We are continuously investigating the cause of the issue and to roll out a fix ASAP.

4. monitoring Mar 29, 2026, 09:01 AM UTC

   A fix has been implemented and we are currently monitoring the status.

5. resolved Mar 29, 2026, 09:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 20, 2026, 12:03 AM UTC· resolved Mar 23, 2026, 08:42 PM UTC

1. investigating Mar 20, 2026, 12:03 AM UTC

   As a result of the TAP Programmatic UI - Intermittent errors incident experienced on March 19th, we are experiencing a delay in synchronisation for deals having been created March 18th and March 19th. The system is working through deal synchronizations but the process is taking much longer than usual. Our development team is working to add mitigation measures to help the system work faster through the backlog of deals to be synched. More information to come.

2. monitoring Mar 20, 2026, 12:25 AM UTC

   Mitigation measures have been applied and all deals that were previously stuck have been synchronized successfully. Should you encounter any further anomaly with a particular deal, please email our support team at [email protected] for assistance. We will be monitoring the situation closely.

3. resolved Mar 23, 2026, 08:42 PM UTC

   This incident is considered resolved.

Read the full incident report →

Started Mar 19, 2026, 09:34 AM UTC· resolved Mar 19, 2026, 05:54 PM UTC

1. investigating Mar 19, 2026, 09:34 AM UTC

   We are currently investigating performance issues affecting the TAP Programmatic user interface. Users may experience latency, error messages, or unexpected behavior while navigating the Programmatic tab to manage deals or packages. Our engineering teams are working to identify the root cause and restore full stability to the platform as quickly as possible. Please note that this issue is limited to the user interface; ad delivery and bidding processes remain unaffected. More information to come.

2. resolved Mar 19, 2026, 05:54 PM UTC

   A fix has been applied. TAP Programmatic interface is once again operating under normal parameters. This incident is considered resolved.

Read the full incident report →

Started Mar 19, 2026, 09:06 AM UTC· resolved Mar 19, 2026, 09:06 AM UTC

1. identified Mar 19, 2026, 09:06 AM UTC

   We are investigating an issue whereby some publishers are seeing reduced auction counts in their Manadge (TAP Programmatic Dashboard) dashboards. We have identified and are working on a solution which will fix the issue for data going forward. More information to come.

2. resolved Mar 19, 2026, 09:06 AM UTC

   This incident is now resolved. We have rolled out a fix which addresses the issue going forward. Please note that clients may see reduced auction counts for 12-18 March ET (inclusive) for any auctions where there were no bids.

Read the full incident report →

Started Mar 17, 2026, 08:45 PM UTC· resolved Mar 18, 2026, 12:10 AM UTC

1. investigating Mar 17, 2026, 08:45 PM UTC

   We are investigating an issue causing delays in Omny analytics to display for some organizations. The issue is known to affect data from 2026-03-17 07:00 UTC onwards. This incident does not affect Podcast Metrics data. More information to come.

2. identified Mar 17, 2026, 10:12 PM UTC

   A fix was applied to the data processing mechanisms. Data is currently starting to populate and catch up in the UI. More information to come.

3. resolved Mar 18, 2026, 12:10 AM UTC

   Processing has caught up and data is now up to date in the UI. Data mechanisms are operating normally. This incident is considered resolved.

Read the full incident report →

Started Feb 26, 2026, 01:58 PM UTC· resolved Feb 27, 2026, 04:30 PM UTC

1. investigating Feb 26, 2026, 01:58 PM UTC

   We are currently investigating an issue impacting all deals created after February 11th, where the deal name is all in lowercase. More information to come

2. identified Feb 26, 2026, 05:06 PM UTC

   We have identified the issue and are actively working on a permanent solution The deals that were created since Feb11th have been fixed. However, any new deals created will still be in lowercase and the fix is planned for early next week. More information to come.

3. resolved Feb 27, 2026, 04:30 PM UTC

   This incident is now resolved.

Read the full incident report →

Started Feb 23, 2026, 08:28 AM UTC· resolved Feb 24, 2026, 10:13 PM UTC

1. investigating Feb 23, 2026, 08:28 AM UTC

   We are currently investigating an issue impacting the All Deals Troubleshooter (Beta). The number of Bid requests displayed is incorrect. In the meantime, for a proper troubleshooting, we recommend using My Dashboard- Deals Troubleshooting and Bids Dashboards. More information to come.

2. resolved Feb 24, 2026, 10:13 PM UTC

   A fix has been applied. The correct values for Bid Requests are now being displayed in the All Deals Troubleshooter (BETA). This feature remains in the BETA phase of development. Should you encounter any bugs, we appreciate your collaboration in reporting them to our Support team. This incident is considered resolved.

Read the full incident report →

Started Feb 20, 2026, 08:06 AM UTC· resolved Feb 24, 2026, 10:30 PM UTC

1. investigating Feb 20, 2026, 08:06 AM UTC

   We are currently investigating a networking issue in our Vancouver datacenter and evaluating the potential impact.

2. monitoring Feb 20, 2026, 10:11 AM UTC

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

3. resolved Feb 24, 2026, 10:30 PM UTC

   This incident is considered resolved.

Read the full incident report →

Started Feb 18, 2026, 04:13 PM UTC· resolved Feb 19, 2026, 09:00 AM UTC

1. investigating Feb 18, 2026, 04:13 PM UTC

   We are currently investigating an issue impacting station tags updating or creation process. A new station tag can be created, but stations cannot be added to the tag. More information to come.

2. monitoring Feb 18, 2026, 09:21 PM UTC

   A fix has been deployed. Users should now be able to add stations to station tags normally. We will monitor the situation closely.

3. resolved Feb 19, 2026, 09:00 AM UTC

   This incident has been resolved

Read the full incident report →

Started Feb 11, 2026, 02:27 PM UTC· resolved Feb 13, 2026, 05:41 PM UTC

1. investigating Feb 11, 2026, 02:27 PM UTC

   We are investigating an issue impacting Omny Studio API and UI services. Some of our users can experience slowness and intermittent errors while navigating through the API/UI. More information to come.

2. monitoring Feb 11, 2026, 03:39 PM UTC

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

3. resolved Feb 13, 2026, 05:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 05, 2026, 12:10 PM UTC· resolved Feb 05, 2026, 08:10 PM UTC

1. identified Feb 05, 2026, 12:10 PM UTC

   We have identify an issue impacting deals created with The Trade Desk. The synchronization will fail if the seller name, email and notes are empty. The team is already working on a fix that we expect to be released to production later today. More information to come.

2. resolved Feb 05, 2026, 08:10 PM UTC

   Remediation measures have been put in place. Deal synchronization is back to working as expected with TTD. This incident is considered resolved.

Read the full incident report →

Started Feb 03, 2026, 08:53 PM UTC· resolved Feb 03, 2026, 10:17 PM UTC

1. investigating Feb 03, 2026, 08:53 PM UTC

   We have identified an issue making Stream Access Control no longer available in the Console UI despite users having appropriate permission levels. Our team is actively working on a hot fix. More information to come.

2. resolved Feb 03, 2026, 10:17 PM UTC

   A fix has been applied. Stream Access Control should not be back to being accessible as normal. This incident is considered resolved.

Read the full incident report →

Started Feb 02, 2026, 07:33 PM UTC· resolved Feb 03, 2026, 01:45 PM UTC

1. investigating Feb 02, 2026, 07:33 PM UTC

   Wee are investigating an issue preventing location targeting to be added or modified in a flight in TAP. Users are seeing errors when attempting to add or modify location-based targeting in TAP flights. More information to come.

2. monitoring Feb 02, 2026, 08:43 PM UTC

   Mitigation measures have been applied. Functionality is back to normal in TAP UI. We will monitor the situation closely.

3. resolved Feb 03, 2026, 01:45 PM UTC

   This incident is considered resolved.

Read the full incident report →

Started Feb 02, 2026, 02:43 PM UTC· resolved Feb 02, 2026, 03:44 PM UTC

1. investigating Feb 02, 2026, 02:43 PM UTC

   We are currently experiencing an active network connectivity issue originating from an network provider. This issue is resulting in intermittent connectivity for stations operating on our streaming infrastructure from South America. Affected stations may experience intermittent connection instability, including brief service disruptions or degraded streaming performance. Due to our redundancy mechanisms, the listeners that were connected before the problem will remain connected and new connections will be redirected to another data center. More information to come

2. resolved Feb 02, 2026, 03:44 PM UTC

   Our ISP partner has applied mitigation measures. Connectivity to our São Paulo location has been restored to normal operating parameters. This incident is considered resolved.

Read the full incident report →

Started Jan 30, 2026, 03:44 PM UTC· resolved Feb 03, 2026, 12:13 PM UTC

1. investigating Jan 30, 2026, 03:44 PM UTC

   We are aware of an issue affecting the accuracy of data displayed in TAP Explore and TAP UI for flights that were created on January 30th. Users may notice that metrics and report outputs for these specific flights do not reflect the correct information. Our teams are actively investigating the root cause and working to resolve the data inconsistency as soon as possible. More information to come.

2. investigating Jan 30, 2026, 04:37 PM UTC

   We are continuing to investigate the issue and found that it is also impacting pacing, which could result in certain flights delivering slightly more or less than expected. More information to come.

3. monitoring Feb 02, 2026, 07:26 AM UTC

   A fix has been implemented on Friday around 4PM UTC. We are monitoring the results.

4. resolved Feb 03, 2026, 12:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 19, 2026, 02:52 PM UTC· resolved Jan 20, 2026, 06:02 PM UTC

1. identified Jan 19, 2026, 02:52 PM UTC

   We are currently experiencing a data processing delay for podcasts being measured through Log Collection. The result of this processing delay will have the podcasts show as "N/A - Not Associated to a Program" in Podcast Metrics. We are working on mitigation measures. More information to come.

2. monitoring Jan 20, 2026, 03:58 PM UTC

   Data processing for log collected podcasts has caught up to normal operating parameters. Users should now see much less occurrences of "N/A - Not Associated to a Program" in Podcast Metrics. We will continue to monitor the situation closely.

3. resolved Jan 20, 2026, 06:02 PM UTC

   This incident is considered resolved.

Read the full incident report →

Started Jan 15, 2026, 02:29 PM UTC· resolved Jan 15, 2026, 04:55 PM UTC

1. investigating Jan 15, 2026, 02:29 PM UTC

   We've gotten reports of deals with Bidswitch created since December that are not running as intended. Our teams are investigating the situation.

2. resolved Jan 15, 2026, 04:55 PM UTC

   Only deals configured via BidSwitch with the “Ignore bidder seat” setting enabled in TAP UI were affected. We have disabled this setting, and delivery has resumed. This incident is now resolved.

Read the full incident report →

Started Jan 13, 2026, 09:32 PM UTC· resolved Jan 15, 2026, 02:27 PM UTC

1. investigating Jan 13, 2026, 09:32 PM UTC

   We are currently investigating issues with errors accessing or loading content in TAP, Metrics and Settings UI. More information to come.

2. monitoring Jan 13, 2026, 09:58 PM UTC

   A fix has been applied. TAP UI, Metrics UI and Settings UI should now be loading content properly. We will be monitoring the situation closely.

3. resolved Jan 15, 2026, 02:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 06, 2026, 05:21 PM UTC· resolved Jan 06, 2026, 07:01 PM UTC

1. identified Jan 06, 2026, 05:21 PM UTC

   We have identified the cause of a bug that is causing TAP UI to refuse valid tracking pixels. Users will encounter an error when attempting to add a tracking pixel to a creative. A hot fix is currently being worked on and should be deployed soon. More information to come.

2. resolved Jan 06, 2026, 07:01 PM UTC

   A fix has been deployed. TAP should be back to properly validating tracking pixels. This incident is considered resolved.

Read the full incident report →

Started Dec 31, 2025, 08:31 PM UTC· resolved Jan 01, 2026, 02:38 AM UTC

1. investigating Dec 31, 2025, 08:31 PM UTC

   We are currently investigating a network connectivity problem in our Montreal data centre. Listener and client impact should be minimal. Our team is working to restore network connectivity as soon as possible. More information to come.

2. identified Dec 31, 2025, 11:21 PM UTC

   The problem has been found to be a faulty network switch. We are replacing the equipment. Impact on listeners should be minimal. More information to come.

3. resolved Jan 01, 2026, 02:38 AM UTC

   The replacement equipment has been installed, configured and is online. This incident is considered resolved.

Read the full incident report →

Started Dec 23, 2025, 08:36 AM UTC· resolved Feb 03, 2026, 03:29 PM UTC

1. investigating Dec 23, 2025, 08:36 AM UTC

   We are currently experiencing network connectivity issues originating from one of our network providers. This issue is resulting in intermittent connectivity for stations operating on our Los Angeles and Singapore streaming infrastructure. Affected stations may experience intermittent connection instability, including brief service disruptions or degraded streaming performance. More information to come.

2. identified Dec 23, 2025, 03:33 PM UTC

   The issue has been identified to be a a cut in our provider's trans-pacific oceanic fibre line. Our service provider is planing for the repairs of the line. At the moment we do not have an ETA for the repairs but the provider is hinting at end of January. In the meantime, we are taking steps to mitigate the issue by moving traffic to other routes. Clients having listeners in Asia (Singapore) with services hosted in North America (such as SAM Broadcaster) will experience momentary service drops as we attempt to move traffic to other locations and routes. More information to come.

3. identified Jan 05, 2026, 06:29 PM UTC

   Our third-party carrier has advised that the cable repair is scheduled to commence on January 23rd, 2026. It is expected to be completed by 1 February 2026. More information to come.

4. resolved Feb 03, 2026, 03:29 PM UTC

   Our provider has completed repairs on their trans-pacific oceanic fibre line. This incident is considered resolved.

Read the full incident report →

Started Dec 19, 2025, 03:08 PM UTC· resolved Jan 07, 2026, 03:03 PM UTC

1. investigating Dec 19, 2025, 03:08 PM UTC

   We are investigating an issue preventing users from creating, modifying and sharing new lineups in Podcast Metrics Lineups. Existing lineups, manual reporting in Explore as well as Saved Queries are unaffected. Only the functions in "Management" are affected. More information to come.

2. identified Dec 23, 2025, 03:31 PM UTC

   The issue is still being investigated by our development team. Due to the holiday code freeze, a fix is expected to be applied early January. More information to come.

3. monitoring Jan 07, 2026, 12:07 PM UTC

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

4. resolved Jan 07, 2026, 03:03 PM UTC

   This incident is considered resolved.

Read the full incident report →

Started Dec 18, 2025, 08:43 AM UTC· resolved Dec 19, 2025, 12:36 PM UTC

1. investigating Dec 18, 2025, 08:43 AM UTC

   We are currently investigating an issue impacting deals synchronization with DV360. More information to come.

2. monitoring Dec 18, 2025, 10:17 AM UTC

   A fix has been implemented and we are monitoring the results. Only newly created deals with DV360 and Xandr were impacted. More information to come.

3. resolved Dec 19, 2025, 12:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 15, 2025, 04:24 PM UTC· resolved Dec 17, 2025, 07:47 AM UTC

1. investigating Dec 15, 2025, 04:24 PM UTC

   We are investigating an issue where dashboard data is not loading in Manadge. More information to come.

2. monitoring Dec 15, 2025, 04:31 PM UTC

   Services were restarted and data is once again available. We will be monitoring the situation closely.

3. resolved Dec 17, 2025, 07:47 AM UTC

   This incident has been resolved

Read the full incident report →