Subscribe to alerts

  • 25 Apr 2019
  • 4:13 pm
  • Server reboot s38

In order to complete an update, a reboot is required. We expect around 10-15 minutes of downtime.

Thank you for your patience.

UPDATE: Reboot complete

  • 25 Apr 2019
  • 3:49 pm
  • Server reboot s34

In order to complete an update, a reboot is required. We expect around 10-15 minutes of downtime.

Thank you for your patience,

UPDATE: Reboot complete

  • 25 Apr 2019
  • 3:41 pm
  • Server reboot s13

In order to complete an update, a reboot is required. We expect around 10-15 minutes of downtime.

Thank you for your patience.

UPDATE: Reboot complete, downtime was less than expected.

  • 25 Apr 2019
  • 1:58 pm
  • Server reboot s3

Due to a fault on s3 which is causing server restarts to fail, it requires a reboot. We hope for service to be back up in the next 10-15 minutes.

UPDATE:

After a reboot attempt, the server failed to come back online. A technician is currently checking the server for faults.

We may need to reinstall the server, but this is a worst case scenario – if this happens then it may take up to 45-60 minutes for service to be back to normal.

Thank you for your patience.

UPDATE:

The motherboard has been replaced and the server is now back online. No reinstallation was required.

  • 18 Apr 2019
  • 8:52 pm
  • SHOUTcast 2.6 now available

We have now added SHOUTcast 2.6 as an option in the user area. We recommend using this version if you have a ‘new style’ authhash.

If you need to update from 2.5 then log into the user area and scroll down to Server Settings > Server Type. You will now see the option for SHOUTcast 2.6.

We have decided not to automatically force the update for all customers as many are still using the old style of Authhash to get listed on the SHOUTcast YP.

Unsure which version to use?

If you are not listed on the SHOUTcast YP then you can use an version.

If you have an old style Authhash, which is a string of letters and numbers only (e.g gM7nnd9TFjP94yE7EdJr), then use V2.5

If you have a new style Authhash, which contains dashes along with letters and numbers (e.g hNw3RgDg-W66u-pm8S-YAh7-aHGs8JWCBg4V), then use V2.6

Note: The authhashes above are randomly generated and will not work. They are intended only as examples to show the difference between the new and old formats.

  • 6 Dec 2018
  • 4:22 pm
  • Website slowness

We are currently experiencing slowness on the website, this is being investigated and we expect the issue to resolved shortly.

Thank you for your patience.

  • 28 Jul 2018
  • 7:40 pm
  • Network issue affecting s4 and s34

There is currently a network issue affecting the above servers. We hope to have service resumed shortly.

Thank you for your patience.

  • 28 Jun 2018
  • 11:01 pm
  • Network issue

We are currently experiencing a network issue which is affecting a small number of servers. It is being worked on and we hope to have service back to normal shortly.

Thank you for your patience.

  • 8 Jun 2018
  • 5:57 pm
  • s11 outage

We are aware of an issue with s11 and are currently looking into it. The server has been rebooted but not yet come back online so an technician is checking for faults.

Thank you for your patience.

Server
ID		 Current
Status		 Nov
Uptime
s1 checking
s2 checking
s3 checking
s4 checking
s5 checking
s6 checking
s7 checking
s8 checking
s9 checking
s10 checking
s11 checking
s12 checking
s13 checking
s14 checking
s15 checking
s16 checking
s17 checking
s18 checking
s19 checking
s20 checking
s21 checking
s22 checking
s23 checking
s24 checking
s25 checking
s26 checking
s27 checking
s28 checking
s29 checking
s30 checking
s31 checking
s32 checking
s33 checking
s34 checking
s35 checking
s36 checking
s37 checking
s38 checking
s39 checking
s40 checking
s41 checking
s42 checking
s43 checking
s44 checking
s45 checking
s46 checking
s47 checking
s48 checking