Radio.co Outage History

Radio.co is up right now

Radio.co had 11 outages in the last 2 years totaling 729h 8m of downtime — averaging 0.5 incidents per month.

There were 11 Radio.co outages since December 22, 2025 totaling 729h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.radio.co

Major July 21, 2026

Possible Degraded Performance on "Streamer" pool

Detected by Pingoru
Jul 21, 2026, 10:57 AM UTC
Resolved
Jul 27, 2026, 10:58 AM UTC
Duration
6d
Timeline · 2 updates
  1. investigating Jul 21, 2026, 10:57 AM UTC

    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.

  2. resolved Jul 27, 2026, 10:58 AM UTC

    Our monitoring system has detected the affected node is back online. Normal service on the "Streamer" pool has resumed.

Read the full incident report →

Major July 21, 2026

Potential Downtime on a Station server

Detected by Pingoru
Jul 21, 2026, 07:42 AM UTC
Resolved
Jul 21, 2026, 07:45 AM UTC
Duration
2m
Timeline · 2 updates
  1. investigating Jul 21, 2026, 07:42 AM UTC

    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.

  2. resolved Jul 27, 2026, 11:11 AM UTC

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

Read the full incident report →

Major July 7, 2026

Possible Degraded Performance on "S3" streaming pool

Detected by Pingoru
Jul 07, 2026, 12:57 PM UTC
Resolved
Jul 07, 2026, 02:00 PM UTC
Duration
1h 2m
Timeline · 2 updates
  1. investigating Jul 07, 2026, 12:57 PM UTC

    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.

  2. resolved Jul 07, 2026, 02:00 PM UTC

    Our monitoring system has detected the affected node is back online. Normal service on the "S3" streaming pool has resumed.

Read the full incident report →

Major June 29, 2026

Possible Degraded Performance on "Stream" pool

Detected by Pingoru
Jun 29, 2026, 10:17 PM UTC
Resolved
Jul 02, 2026, 04:20 PM UTC
Duration
2d 18h
Timeline · 2 updates
  1. investigating Jun 29, 2026, 10:17 PM UTC

    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.

  2. resolved Jul 02, 2026, 04:20 PM UTC

    Our monitoring system has detected the affected node is back online. Normal service on the "Streaming" pool has resumed.

Read the full incident report →

Major April 21, 2026

Studio Inaccessible / Streams Off Air

Detected by Pingoru
Apr 21, 2026, 08:01 AM UTC
Resolved
Apr 21, 2026, 09:13 AM UTC
Duration
1h 11m
Timeline · 3 updates
  1. investigating Apr 21, 2026, 08:01 AM UTC

    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.

  2. investigating Apr 21, 2026, 08:29 AM UTC

    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.

  3. resolved Apr 22, 2026, 02:13 PM UTC

    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.

Read the full incident report →