Triton Digital Platform Status

Resolved: 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.

Investigating: 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

Resolved: 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.

Investigating: 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

Resolved: This incident has been resolved.

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

Investigating: 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.

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident has been resolved.

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

Investigating: 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.

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

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

Investigating: 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.

Resolved: This incident has been resolved.

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

Investigating: 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.

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident has been resolved.

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

Investigating: 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.

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

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

Investigating: 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.

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

Identified: 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.

Identified: 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.

Investigating: 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.

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

Identified: 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.

Identified: 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.

Investigating: 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.

Resolved: This incident has been resolved.

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

Investigating: 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.

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident has been resolved.

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

Investigating: 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.

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

Resolved: This incident is considered resolved.

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

Investigating: 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.

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

Investigating: 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.

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

Identified: 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.

Identified: 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.

Investigating: 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.