Triton Digital Platform Status

Resolved: This incident is considered resolved.

Monitoring: A fix has been applied, Data has been restored. Royalty Reporting data should be available under normal data delays. We will monitor the situation closely.

Identified: The issue has been identified. Our team is working to restore the missing data. More information to come.

Investigating: Good morning.

We are currently investigating an issue affecting the Royalty reports. Performance results are not appearing from November 19th onward. We will provide an update as soon as we have more information.

Resolved: This incident is considered resolved.

Monitoring: The issue prevailed from around 12-17 UTC. It also affected Time To Listen for listeners, which increased by a few seconds. We are continuing to monitor the situation.

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. Podcast RRS and episodes delivery are not being impacted. More information to come.

Resolved: This incident is considered resolved.

Monitoring: The issue prevailed from around 12-17 UTC. It also affected Time To Listen for listeners, which increased by a few seconds. We are continuing to monitor the situation.

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. Podcast RRS and episodes delivery are not being impacted. More information to come.

Resolved: After several hours of monitoring, we confirm the issue has been fully resolved and all services are operating normally. Our preliminary analysis indicates the problem was caused by a combination of factors related to Timeshift technology, including a software bug, a race condition, and a configuration issue. These factors led certain servers to stop accepting new connections while maintaining existing listener sessions. Immediate corrective actions were implemented, and additional follow-up measures are scheduled for early next week to prevent recurrence. Thank you for your patience and understanding.

Monitoring: Our team has applied mitigation measures and service is back to normal. The issue seems to have been cause by an unexpected situation in the MediaGateway when handling TimeShift mounts. We are looking into ways of handling such situations so they don't cause a cascading effect in the future. More information to come.

Investigating: The issue was affecting only new connections to the Media Gateways. In order to apply corrective measure to the affected MGs, we need to move all traffic from them to healthy servers. This will cause a disconnection to existing listeners, who should reconnect quickly to new healthy instance. More information to come.

Investigating: We are investigating an issue with our streaming servers in Europe which is preventing streams to be delivered to listeners. Our team is working to redistribute streaming to other locations and unaffected Media Gateway instances. More information to come.

Resolved: This incident is considered resolved.

Monitoring: A fix has been applied, Data has been restored. Royalty Reporting data should be available under normal data delays. We will monitor the situation closely.

Identified: The issue has been identified. Our team is working to restore the missing data. More information to come.

Investigating: Good morning.

We are currently investigating an issue affecting the Royalty reports. Performance results are not appearing from November 19th onward. We will provide an update as soon as we have more information.

Resolved: This incident is considered resolved.

Monitoring: The issue prevailed from around 12-17 UTC. It also affected Time To Listen for listeners, which increased by a few seconds. We are continuing to monitor the situation.

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. Podcast RRS and episodes delivery are not being impacted. More information to come.

Resolved: This incident is considered resolved.

Monitoring: The issue prevailed from around 12-17 UTC. It also affected Time To Listen for listeners, which increased by a few seconds. We are continuing to monitor the situation.

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. Podcast RRS and episodes delivery are not being impacted. More information to come.

Resolved: This incident is considered resolved.

Monitoring: A fix has been applied, Data has been restored. Royalty Reporting data should be available under normal data delays. We will monitor the situation closely.

Identified: The issue has been identified. Our team is working to restore the missing data. More information to come.

Investigating: Good morning.

We are currently investigating an issue affecting the Royalty reports. Performance results are not appearing from November 19th onward. We will provide an update as soon as we have more information.

Resolved: This incident is considered resolved.

Monitoring: The issue prevailed from around 12-17 UTC. It also affected Time To Listen for listeners, which increased by a few seconds. We are continuing to monitor the situation.

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. Podcast RRS and episodes delivery are not being impacted. More information to come.

Resolved: This incident is considered resolved.

Monitoring: The issue prevailed from around 12-17 UTC. It also affected Time To Listen for listeners, which increased by a few seconds. We are continuing to monitor the situation.

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. Podcast RRS and episodes delivery are not being impacted. More information to come.