Triton Digital Platform Status

Identified: We have identified an issue affecting only a portion of our clients using Server Side Transcode (SST) for their ingestion streams. In the last 24 hours, it's possible that some of your listeners were having problems to connect to the streams, lowering your overall listenership on these SST stations only. This issue was caused by a bug introduced in the latest update of our Media Relay software. We have rolled back the update and a permanent fix will be deployed early next week. More information to come.

Identified: We have identified an issue affecting only a portion of our clients using Server Side Transcode (SST) for their ingestion streams. In the last 24 hours, it's possible that some of your listeners were having problems to connect to the streams, lowering your overall listenership on these SST stations only. This issue was caused by a bug introduced in the latest update of our Media Relay software. We have rolled back the update and a permanent fix will be deployed early next week. More information to come.

Resolved: Data processing is not complete. All data displayed in Manadge is up to date and displaying normally. This incident is considered resolved.

Identified: The issue has been identified and the system is now back to ingesting data normally. However, we have a gap in data from February 13th 13:00 UTC to 15th 2:00 UTC. We are currently reingesting and reprocessing this data for display in the UI. More information to come.

Investigating: We are investigating an issue in our data processing flow which is causing delay in the data we publish in Manadge.
Last data reported in Manadge is on the 12th of February at 12PM UTC . Yield-Op delivery is not impacted.

Identified: We have identified an issue affecting only a portion of our clients using Server Side Transcode (SST) for their ingestion streams. In the last 24 hours, it's possible that some of your listeners were having problems to connect to the streams, lowering your overall listenership on these SST stations only. This issue was caused by a bug introduced in the latest update of our Media Relay software. We have rolled back the update and a permanent fix will be deployed early next week. More information to come.

Identified: There is delay in the delivery of the replacement part. Our team is doing all it can to speed up the delivery and replacement of the part. More information to come.

Identified: We have identified failing hardware on one of the core equipement in London.
The device has been isolated and the site is stable. We are still running with lower capacity. Streaming services have been redistributed to other locations until we regain full capacity.

Investigating: We are investigating an issue on our London datacenters affecting one of the core network equipment, causing loss of core redundancy and capacity. This might impact ad delivery and listeners experience (podcast and live streaming). More information to come.

Resolved: This incident is considered resolved.

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

Investigating: We are experiencing high level of packet loss out of our MAD2 datacenter hosting Streaming services. We are in contact with the provider investigating the issue. During this period, listeners might experience disconnection and/or slow start of stream if connected to that datacenter.

Identified: There is delay in the delivery of the replacement part. Our team is doing all it can to speed up the delivery and replacement of the part. More information to come.

Identified: We have identified failing hardware on one of the core equipement in London.
The device has been isolated and the site is stable. We are still running with lower capacity. Streaming services have been redistributed to other locations until we regain full capacity.

Investigating: We are investigating an issue on our London datacenters affecting one of the core network equipment, causing loss of core redundancy and capacity. This might impact ad delivery and listeners experience (podcast and live streaming). More information to come.

Resolved: This incident is considered resolved.

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

Investigating: We are experiencing high level of packet loss out of our MAD2 datacenter hosting Streaming services. We are in contact with the provider investigating the issue. During this period, listeners might experience disconnection and/or slow start of stream if connected to that datacenter.

Identified: There is delay in the delivery of the replacement part. Our team is doing all it can to speed up the delivery and replacement of the part. More information to come.

Identified: We have identified failing hardware on one of the core equipement in London.
The device has been isolated and the site is stable. We are still running with lower capacity. Streaming services have been redistributed to other locations until we regain full capacity.

Investigating: We are investigating an issue on our London datacenters affecting one of the core network equipment, causing loss of core redundancy and capacity. This might impact ad delivery and listeners experience (podcast and live streaming). More information to come.

Identified: There is delay in the delivery of the replacement part. Our team is doing all it can to speed up the delivery and replacement of the part. More information to come.

Identified: We have identified failing hardware on one of the core equipement in London.
The device has been isolated and the site is stable. We are still running with lower capacity. Streaming services have been redistributed to other locations until we regain full capacity.

Investigating: We are investigating an issue on our London datacenters affecting one of the core network equipment, causing loss of core redundancy and capacity. This might impact ad delivery and listeners experience (podcast and live streaming). More information to come.

Identified: There is delay in the delivery of the replacement part. Our team is doing all it can to speed up the delivery and replacement of the part. More information to come.

Identified: We have identified failing hardware on one of the core equipement in London.
The device has been isolated and the site is stable. We are still running with lower capacity. Streaming services have been redistributed to other locations until we regain full capacity.

Investigating: We are investigating an issue on our London datacenters affecting one of the core network equipment, causing loss of core redundancy and capacity. This might impact ad delivery and listeners experience (podcast and live streaming). More information to come.

Identified: There is delay in the delivery of the replacement part. Our team is doing all it can to speed up the delivery and replacement of the part. More information to come.

Identified: We have identified failing hardware on one of the core equipement in London.
The device has been isolated and the site is stable. We are still running with lower capacity. Streaming services have been redistributed to other locations until we regain full capacity.

Investigating: We are investigating an issue on our London datacenters affecting one of the core network equipment, causing loss of core redundancy and capacity. This might impact ad delivery and listeners experience (podcast and live streaming). More information to come.

Resolved: Data processing is not complete. All data displayed in Manadge is up to date and displaying normally. This incident is considered resolved.

Identified: The issue has been identified and the system is now back to ingesting data normally. However, we have a gap in data from February 13th 13:00 UTC to 15th 2:00 UTC. We are currently reingesting and reprocessing this data for display in the UI. More information to come.

Investigating: We are investigating an issue in our data processing flow which is causing delay in the data we publish in Manadge.
Last data reported in Manadge is on the 12th of February at 12PM UTC . Yield-Op delivery is not impacted.

Identified: We have identified an issue affecting only a portion of our clients using Server Side Transcode (SST) for their ingestion streams. In the last 24 hours, it's possible that some of your listeners were having problems to connect to the streams, lowering your overall listenership on these SST stations only. This issue was caused by a bug introduced in the latest update of our Media Relay software. We have rolled back the update and a permanent fix will be deployed early next week. More information to come.

Identified: We have identified an issue affecting only a portion of our clients using Server Side Transcode (SST) for their ingestion streams. In the last 24 hours, it's possible that some of your listeners were having problems to connect to the streams, lowering your overall listenership on these SST stations only. This issue was caused by a bug introduced in the latest update of our Media Relay software. We have rolled back the update and a permanent fix will be deployed early next week. More information to come.

Resolved: Data processing is not complete. All data displayed in Manadge is up to date and displaying normally. This incident is considered resolved.

Identified: The issue has been identified and the system is now back to ingesting data normally. However, we have a gap in data from February 13th 13:00 UTC to 15th 2:00 UTC. We are currently reingesting and reprocessing this data for display in the UI. More information to come.

Investigating: We are investigating an issue in our data processing flow which is causing delay in the data we publish in Manadge.
Last data reported in Manadge is on the 12th of February at 12PM UTC . Yield-Op delivery is not impacted.