Radio.co Outage History

Radio.co is up right now

Pingoru has recorded 61 incidents for Radio.co: 61 in the last 12 months and 23 in the last 90 days.

Source: status.radio.co

61incidents recorded
61last 12 months
23last 90 days
34 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Radio.co in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026438 of 720 (5%)
May 202622 of 744 (0%)
June 20262184 of 720 (25%)
July 20265202 of 744 (27%)
August 20267368 of 744 (49%)
September 202610158 of 720 (22%)
October 20269125 of 744 (17%)
November 202600 of 123 (0%)

Incidents, newest first

Major August 7, 2026 Stations Off Air 29m Radio.co Studio, studio.radio.co, Database, Platform and 4 more

Started Aug 07, 2026, 02:34 PM UTC· resolved Aug 07, 2026, 03:04 PM UTC

  1. investigating Aug 07, 2026, 02:34 PM UTC

    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.

  2. investigating Aug 07, 2026, 02:51 PM UTC

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

  3. resolved Aug 07, 2026, 03:04 PM UTC

    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.

Read the full incident report →

Major July 21, 2026 Possible Degraded Performance on "Streamer" pool 6d

Started Jul 21, 2026, 10:57 AM UTC· resolved Jul 27, 2026, 10:58 AM UTC

  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 2m

Started Jul 21, 2026, 07:42 AM UTC· resolved Jul 21, 2026, 07:45 AM UTC

  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 14, 2026 Potential Downtime on a Station server 16h 23m

Started Jul 14, 2026, 03:20 PM UTC· resolved Jul 15, 2026, 07:43 AM UTC

  1. investigating Jul 14, 2026, 03:20 PM 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 15, 2026, 07:43 AM UTC

    Our monitoring software has detected the station server is back online. This incident has now been closed. If you continue to experience issues please contact [email protected] Thanks.

Read the full incident report →

Major July 7, 2026 Possible Degraded Performance on "Streamer" pool 49m

Started Jul 07, 2026, 01:05 PM UTC· resolved Jul 07, 2026, 01:55 PM UTC

  1. investigating Jul 07, 2026, 01:05 PM 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 07, 2026, 01:55 PM 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 7, 2026 Possible Degraded Performance on "S3" streaming pool 1h 2m

Started Jul 07, 2026, 12:57 PM UTC· resolved Jul 07, 2026, 02:00 PM UTC

  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 2d 18h

Started Jun 29, 2026, 10:17 PM UTC· resolved Jul 02, 2026, 04:20 PM UTC

  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 June 8, 2026 Potential Downtime on a Station server 6d 13h

Started Jun 08, 2026, 10:10 AM UTC· resolved Jun 14, 2026, 11:57 PM UTC

  1. investigating Jun 08, 2026, 10:10 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 Jun 14, 2026, 11:57 PM UTC

    Our monitoring software has detected the station server is back online. This incident has now been closed. If you continue to experience issues please contact [email protected] Thanks.

Read the full incident report →

Major May 28, 2026 Potential Downtime on a Station server 2m

Started May 28, 2026, 11:46 PM UTC· resolved May 28, 2026, 11:49 PM UTC

  1. resolved May 28, 2026, 11:49 PM UTC

    Our monitoring software has detected the station server is back online. This incident has now been closed. If you continue to experience issues please contact [email protected] Thanks.

Read the full incident report →

Major May 21, 2026 Possible Degraded Performance on "Streamer" pool 1h 39m

Started May 21, 2026, 05:02 PM UTC· resolved May 21, 2026, 06:41 PM UTC

  1. investigating May 21, 2026, 05:02 PM 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 May 21, 2026, 06:41 PM 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 April 26, 2026 Possible Degraded Performance on "Stream" pool 1d 6h

Started Apr 26, 2026, 02:11 AM UTC· resolved Apr 27, 2026, 09:08 AM UTC

  1. investigating Apr 26, 2026, 02:11 AM 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 Apr 27, 2026, 09:08 AM 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 23, 2026 Potential Downtime on a Station server 7m

Started Apr 23, 2026, 07:52 AM UTC· resolved Apr 23, 2026, 07:59 AM UTC

  1. resolved Apr 23, 2026, 07:59 AM UTC

    Our monitoring software has detected the station server is back online. This incident has now been closed. If you continue to experience issues please contact [email protected] Thanks.

Read the full incident report →

Major April 21, 2026 Studio Inaccessible / Streams Off Air 1h 11m

Started Apr 21, 2026, 08:01 AM UTC· resolved Apr 21, 2026, 09:13 AM UTC

  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 →

Major April 16, 2026 Stations Status Incorrectly Reporting Off Air 5h 18m

Started Apr 16, 2026, 04:11 PM UTC· resolved Apr 16, 2026, 09:30 PM UTC

  1. resolved Apr 16, 2026, 09:30 PM UTC

    We've now resolved the incident. Thanks for your patience. If you experience any further issues please contact support - [email protected]

Read the full incident report →

Major March 30, 2026 Potential Downtime on a Station server 1m

Started Mar 30, 2026, 07:42 PM UTC· resolved Mar 30, 2026, 07:44 PM UTC

  1. resolved Mar 30, 2026, 07:44 PM UTC

    Our monitoring software has detected the station server is back online. This incident has now been closed. If you continue to experience issues please contact [email protected] Thanks.

Read the full incident report →

Major March 29, 2026 Possible Degraded Performance on "Streamer" pool 1d 17h

Started Mar 29, 2026, 02:11 AM UTC· resolved Mar 30, 2026, 07:46 PM UTC

  1. resolved Mar 30, 2026, 07:46 PM 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 March 24, 2026 Possible Degraded Performance on "S3" streaming pool 1d 17h

Started Mar 24, 2026, 06:16 PM UTC· resolved Mar 26, 2026, 11:51 AM UTC

  1. resolved Mar 26, 2026, 11:51 AM 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 March 24, 2026 Possible Degraded Performance on "Stream" pool 2h 3m

Started Mar 24, 2026, 12:04 AM UTC· resolved Mar 24, 2026, 02:08 AM UTC

  1. resolved Mar 24, 2026, 02:08 AM 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 March 18, 2026 Potential Disruption on Citron 50m

Started Mar 18, 2026, 03:45 PM UTC· resolved Mar 18, 2026, 04:36 PM UTC

  1. resolved Mar 18, 2026, 04:36 PM UTC

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

Read the full incident report →

Major March 18, 2026 Possible Degraded Performance on "Stream" pool 19m

Started Mar 18, 2026, 10:33 AM UTC· resolved Mar 18, 2026, 10:52 AM UTC

  1. resolved Mar 18, 2026, 10:52 AM 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 March 13, 2026 Potential Downtime on a Station server 22m

Started Mar 13, 2026, 07:46 AM UTC· resolved Mar 13, 2026, 08:09 AM UTC

  1. resolved Mar 13, 2026, 08:09 AM UTC

    Our monitoring software has detected the station server is back online. This incident has now been closed. If you continue to experience issues please contact [email protected] Thanks.

Read the full incident report →

Major March 12, 2026 Possible Degraded Performance on "Stream" pool 23m

Started Mar 12, 2026, 04:05 PM UTC· resolved Mar 12, 2026, 04:29 PM UTC

  1. resolved Mar 12, 2026, 04:29 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 February 26, 2026 Issues affecting 'Login with Radio.co' services 21d 6h

Started Feb 26, 2026, 09:44 AM UTC· resolved Mar 19, 2026, 04:08 PM UTC

  1. resolved Mar 19, 2026, 04:08 PM UTC

    We've now resolved this issue, you will again be able to use the 'Login with Radio.co' service. Thanks for your patience.

Read the full incident report →

Major January 30, 2026 Potential Downtime on a Station server 6m

Started Jan 30, 2026, 04:29 PM UTC· resolved Jan 30, 2026, 04:36 PM UTC

  1. resolved Jan 30, 2026, 04:36 PM UTC

    Our monitoring software has detected the station server is back online. This incident has now been closed. If you continue to experience issues please contact [email protected] Thanks.

Read the full incident report →

Major January 23, 2026 Possible Degraded Performance on "Streams" pool 12m

Started Jan 23, 2026, 05:09 PM UTC· resolved Jan 23, 2026, 05:22 PM UTC

  1. resolved Jan 23, 2026, 05:22 PM UTC

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

Read the full incident report →