Radio.co had 15 outages in the last 2 years totaling 1537h 39m of downtime — averaging 0.6 incidents per month.
There were 15 Radio.co outages since December 22, 2025 totaling 1537h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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.
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.
Our monitoring system has detected potential degraded performance on the "Streams" pool. The affected node has been removed from service until it is available again. Listeners will be re-routed to other nearby servers automatically. Once the affected node is restored we will reintroduce it to service.
We're aware of an issue affecting the availability of some streams, as well as being unable to access Studio. We're working to resolve this, and will provide an update here shortly. We apologise for the inconvenience.
We've fixed the core issue, and are waiting for things to recover.
We've now resolved the incident. Thanks for your patience. If your station is not broadcasting, please restart to resolve. We apologise for the inconvenience, our development team will now investigate further the cause.
Our monitoring system has detected potential degraded performance on the "Streamer" pool. The affected node has been removed from service until it is available again. Listeners will be re-routed to other nearby servers automatically. Once the affected node is restored we will reintroduce it to service.
Our monitoring system has detected the affected node is back online. Normal service on the "Streamer" pool has resumed.
Our monitoring system has detected potential degraded performance on the "S3" streaming pool. The affected node has been removed from service until it is available again. Listeners will be re-routed to other nearby servers automatically. Once the affected node is restored we will reintroduce it to service.
Our monitoring system has detected the affected node is back online. Normal service on the "S3" streaming pool has resumed.
Our monitoring system has detected potential degraded performance on the "Streaming" pool. The affected node has been removed from service until it is available again. Listeners will be re-routed to other nearby servers automatically. Once the affected node is restored we will reintroduce it to service.
Our monitoring system has detected the affected node is back online. Normal service on the "Streaming" pool has resumed.
We're aware of an issue where Radio.co Studio is currently inaccessible, and your stream may be offline. We're investigating with urgency, and will provide updates as soon as possible. We apologise for the inconvenience.
We believe the core issue to be resolved, and stations should now be coming back on air. We apologise for the inconvenience, we will provide a RFO shortly.
Thank you for your patience as we worked to resolve this issue. A configuration issue within our caching system led to one component running out of available memory, which caused a temporary disruption. What we've done: - Reviewed and checked the system data and settings - Put improvements in place to prevent this happening again We apologise once again for this incident, and we appreciate your understanding.
We've now resolved the incident. Thanks for your patience. If you experience any further issues please contact support - [email protected]
We've now resolved the incident. Thanks for your patience.
We've now resolved this issue, you will again be able to use the 'Login with Radio.co' service. Thanks for your patience.
Our monitoring system has detected the affected node is back online. Normal service on the "S2" streaming pool has resumed.