Radio.co incident
Track fading may not function as expected when fade markers are offset.
Radio.co experienced a major incident on August 21, 2026, lasting 13d 23h. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Aug 24, 2026, 04:37 PM UTC
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.
- resolved Aug 25, 2026, 05:38 PM UTC
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.
- resolved Aug 26, 2026, 04:14 PM UTC
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.
- resolved Sep 01, 2026, 03:31 PM UTC
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.
- resolved Sep 03, 2026, 12:59 PM UTC
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.
- resolved Sep 04, 2026, 08:33 AM UTC
We've now resolved the incident. Thanks for your patience.