- 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.
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.
The server s13 is being rebooted due to reported slowness. We expect it to come back online in the next 10 minutes.
Thank you for your patience.
We are aware that a routing issue outside of our networks is causing slowness on some servers.
Due to the nature of the internet, most connections travel through multiple third party networks and when one of them experiences high traffic or some other problem then it can affect services.
We are monitoring the situation and have contacted our network providers to see if they can work with the third party at fault.
Please note that if you need to get back online right away then you can click the [Change] button next to your Server Address/Host and change to a different server. European servers are not affected.
We are currently rebooting S11 due to an issue with streams not starting. There has been a problem which is causing a delay for the server to come back online but we are working on this to get service back up ASAP.
You may have experienced some downtime over the last hour, this was due to a configuration error which resulted in the web server using an old SSL certificate. The configuration is now fixed and the new SSL certificate is active.
Thank you for your patience.
We are currently rebooting s31 as a customer has reported some issues with the stream. The server has been online without a reboot for almost 2 years so this may be causing it to slow down slightly.
Due to the server freezing, it is currently being rebooted. Thank you for your patience
Our network provider in Europe is currently looking into a network issue that’s currently causing buffering for some customers and may be affecting your service. They are aware of the issue and hope to have service back to normal shortly.
There is no need to open a support ticket as we are currently waiting for the network provider to fix the issue.
We are currently experiencing a network issue which is affecting your service. We hope to have service back to normal shortly.
Thank you for your patience.
Update: resolved
It appears that Shoutcast.com is down for maintenance and therefore customers will find that their server cannot connect to the YP. You may get a message on your DNAS saying that your server is ‘private’, this is normal when a server is unable to connect to the YP. This does not affect your service and your listeners can still tune in as normal, it’s just the Shoutcast website that’s not loading.
| Server ID |
Current Status |
Jan 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 |