Is Radio.co down?

Our monitoring software has detected potential downtime on a Station Server. Our DevOps team has been informed and are working to investigate the problem. Further updates will be provided in due course. If your station has stopped broadcasting we apologise for the inconvenience caused.

We've now resolved the incident. Thanks for your patience.

Our monitoring software has detected potential downtime on a Station Server. Our DevOps team has been informed and are working to investigate the problem. Further updates will be provided in due course. If your station has stopped broadcasting we apologise for the inconvenience caused.

This was a false alarm, there was no real problem.

We are aware of some instances where track fading may not function as expected in certain scenarios, especially if the incoming track has fade set to zero, or a lower fade duration than the outgoing track. Our development team is working to resolve this issue. Once we have more information we will update this report. Due to the nature of the issue we will need to undertake extensive testing before wider release.

Work is continuing on this issue. Unfortunately we do not have an ETA at this time. Once we have more information we will provide an update.

We are testing a solution internally and expect to publish this to affected stations once testing is verified. This will be within the next 24 hours. We will update this report once this has happened.

We will be rolling out an update to crossfading on Wednesday 2nd September which restores previous behaviour. This rollout will require a station restart, however only needs to be carried out if your station fades are not as expected. We will provide another update once the rollout is complete. Thanks for your patience.

We have rolled out the update across our fleet which restores the fades to expected behaviour. Please restart your station when convenient to load the new software update. If you continue to experience issues please reach out at [email protected] Once again we'd like to apologise for any inconvenience caused.

We've now resolved the incident. Thanks for your patience.

We are investigating reports that playlists may not be starting from the expected position in some instances. If you have reported this issue to support, this has been logged with our engineering team who are investigating. Further updates will be provided as this notice progresses. Thank you for your patience during this time,

We've fixed the core issue, and are waiting for things to recover.

Development have made some adjustments to the track fetch service around while they work on a permanent resolution. This should improve the situation with track ordering in most cases. We will provide a full update once available.

We’ve deployed several improvements related to playlists skipping, and reports showing skipped tracks ### The changes now live include: - Increased request timeouts, which should reduce instances where track requests are not completed in time, including some skips around the top of the hour. - Improved handling of short tracks and jingles so they are recorded more accurately in Playout History. - Requires station restart We’re continuing to monitor the results of these changes and investigate the remaining instances of playlist positions being skipped. Further work on related playback and crossfade behaviour will follow once this investigation is complete. We’ll post another update as soon as we have more information. Thank you for your patience.

Further work has been completed which has improved performance and reduced the occurrences of track skip events significantly. Changes now live: - Full review of our platform infrastructure scaling with additional performance improvements and fallbacks in place As per our update yesterday, a station restart addressed an issue affecting short tracks (such as Jingles) being missed from the playout report, despite being played. If you are still experiencing this issue, we advise to restart your station at a convenient time. We will provide further updates once known.

Further optimisations have been made to the platform and we have seen a dramatic decrease in instances of skipped playlist items. The team continues to work on the matter to further improve playout in edge cases. The majority of track playouts should be as expected. We will provide another update within the next 24 hours.

We’ve been monitoring the platform closely over the last 24 hours and have seen a significant reduction in occurrences. In some cases, this behaviour can happen when a station has strict separation rules enabled and the system is unable to find a suitable track within a reasonable timeframe. When this happens, a playlist tag item may be skipped as expected. To help reduce the likelihood of this occurring, we recommend relaxing your separation rules so that, where multiple rules are enabled, they do not exceed 120 minutes. If you continue to experience issues, especially if you do not have separation rules enabled, please contact us at [email protected] or reply to your existing support conversation. Once again we thank you for your patience during this time.

We've now resolved the incident. Thanks for your patience.

An update has been rolled out to general availability to address this. In order for your station to benefit from the new version, please restart at your convenience.