All Systems Operational

Uptime over the past 90 days. View historical uptime.
Live Streams Operational
Icecast Streams Operational
Monetised Streams Operational
On-Demand Streaming Operational
Standard on-demand streams Operational
Monetised on-demand streams Operational
Ingress Operational
Audio ingests Operational
Premium ingests Operational
Portal Operational
Portal user access Operational
TimbreCMS Operational
TimbreCMS user access Operational
Analytics Operational
Radar User Access Operational
Network & Infrastructure Operational
Core network devices Operational
Transit providers Operational
Storage Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Premium Streams - Considerations for Remembrance Day Silence Observances Nov 11, 2026 11:17-12:17 UTC

This is a notice to all Premium Stream Customers ahead of Remembrance Day observances on Sunday and Wednesday.

For stations observing the Silence, we want to inform you of the preparations required to ensure that your backup content is not played out on your live stream during this time. Please ensure that one of the following actions has been taken ahead of the silence:

1) Have an ambient noise file (>-40dB) prepared to play out instead of silence: This is typical practice for stations given the number of automated fallbacks that tend to be in place at FM transmission sites or DAB Muxs. This could be a cityscape or birdsong or similar, just ensure your file exceeds -40dB and this will not be flagged as silence and therefore not trigger a fallback to backup file by our script. You can find a file for this purpose in our help guide here: https://support.sharp-stream.com/support/solutions/articles/48001244755-observed-silence-best-practice-guide

2) Replace your backup content with silence: If you do not plan to play an ambient file at the time of the silence, then your silent encoder feed will trigger a fallback to your backup feed. If your backup feed is set to play out music or backup audio, replace this audio with a silence file in Timbre. Ensure the backup content has been reloaded prior to the time of silence so the silence file takes hold.

We recommend that you run a test of your silence ahead of the day to ensure the above settings that you have applied are functioning correctly.
Posted on Nov 05, 2026 - 11:21 UTC

Maintenance: Switching static routes for Premium A-Feeds ingests Nov 11, 2026 23:00 - Nov 12, 2026 02:00 UTC

As part of our initiative to deploy our next generation infrastructure - We’re carrying out a planned maintenance window to migrate the static route for A-Feeds for premium ingests to our new datacentre location.

We recommend ensuring you have a stable B-Feeds connection in place ahead of this work to ensure your content remains consistent.

If you do not have a B-Feed contribution in place you can find the contribution details in Portal. More information here: https://support.sharp-stream.com/support/solutions/articles/48001215000-where-can-i-find-the-mount-information-for-encoder-contribution-
Posted on Nov 05, 2026 - 11:25 UTC

Nov 5, 2026

No incidents reported today.

Nov 4, 2026

POSTPONED Maintenance: Switching static routes for Premium A-Feeds ingests
Completed - THIS MAINTENANCE HAS BEEN POSTPONED

Due to team availability, we have decided to postpone this maintenance to 11/11/26
Nov 4, 17:52 UTC
Scheduled - As part of our initiative to deploy our next generation infrastructure - We’re carrying out a planned maintenance window to migrate the static route for A-Feeds for premium ingests to our new datacentre location.

We recommend ensuring you have a stable B-Feeds connection in place ahead of this work to ensure your content remains consistent.

If you do not have a B-Feed contribution in place you can find the contribution details in Portal. More information here: https://support.sharp-stream.com/support/solutions/articles/48001215000-where-can-i-find-the-mount-information-for-encoder-contribution-
Oct 30, 12:07 UTC
Maintenance: Switching static route for non-premium ingest A-feeds servers
Completed - The scheduled maintenance has been completed.
Nov 4, 02:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 3, 23:00 UTC
Scheduled - As part of our initiative to deploy our next generation infrastructure - We’re carrying out a planned maintenance window to migrate the static route for A-Feeds for non-premium ingests to our new datacentre location.

We recommend ensuring you have a stable B-Feeds connection in place ahead of this work to mitigate any potential audience loss as the route switches. If you do not have a B-Feed contribution in place you can find the contribution details in Portal. More information here: https://support.sharp-stream.com/support/solutions/articles/48001215000-where-can-i-find-the-mount-information-for-encoder-contribution-
Oct 30, 12:03 UTC

Nov 3, 2026

Nov 2, 2026

No incidents reported.

Nov 1, 2026

No incidents reported.

Oct 31, 2026

No incidents reported.

Oct 30, 2026

No incidents reported.

Oct 29, 2026

No incidents reported.

Oct 28, 2026

Soaking new datacentre edges
Completed - The scheduled maintenance has been completed.
Oct 28, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 28, 09:00 UTC
Scheduled - We are updating our network routing so that a new datacentre can start handling a portion of live traffic. This is part of ongoing capacity and resilience improvements across our delivery network.

No changes to your configuration or stream URLs are required as part of this work.

Note: This maintenance will take place during business hours to ensure the necessary availability of internal teams and external network providers. We will complete the changes within the specified maintenance window and actively monitor traffic and routing throughout the day.


Expected Impact:

- Some network paths for incoming contribution streams (both primary and backup feeds) may change as traffic starts using the new datacentre edges.

- We do not expect listener-facing interruption as this is a network routing update, not an application or service change.
Oct 26, 16:44 UTC

Oct 27, 2026

No incidents reported.

Oct 26, 2026

Maintenance: Announcing New Datacentre to the Internet
Completed - The scheduled maintenance has been completed.
Oct 26, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 26, 08:00 UTC
Scheduled - As part of our initiative to deploy our next generation infrastructure - We’re carrying out a planned network maintenance window to prepare our new datacentre location for live use.

What’s happening

We’re updating how one of our new datacentres connects out to the wider internet. This work is needed so we can start bringing new edge servers and services online in that location.

Impact
- Some routing paths changes may occur for incoming feeds to static routes. However, no interruptions are to be expected.
- We do not expect any interruption to streams, feeds, or access during this work.
- Some internal ranges will begin routing directly via the new data centre rather than via an intermediary site. These are not yet used for production services, so this will not impact end users.
- We’ve verified that safety mechanisms for routing (including handling of unreachable routes) are correctly configured and will not affect service availability.
Oct 22, 08:26 UTC

Oct 25, 2026

No incidents reported.

Oct 24, 2026

No incidents reported.

Oct 23, 2026

CVE-2026-109618 & CVE-2026-109619 | Critical Security Alert – PHP
Resolved - Dear Customers,

We can confirm all core SharpStream services are now update to stable versions of PHP with the CVE-2026-109618 and CVE-2026-109619 vulnerabilities patched, resolving this incident.

As with any incident of this nature we may expect further patches to be released over the coming weeks. We shall continue to follow guidance on the latest PHP versions and regularly monitor all services to ensure security and stability is retained.

Kind regards,
SharpStream Team
Oct 23, 15:44 UTC
Update - Recoverable Incomplete AOD assets from the previous work have now been restored. Concluding this portion of the patch process.
Oct 22, 17:17 UTC
Update - Recordings commencing at 16:00 BST have successfully started, We are working to recover any incomplete assets from the previous scheduler deployment.
Oct 22, 15:36 UTC
Update - As part of the response to yesterday’s PHP vulnerabilitys and emergency patches, we have updated the scheduling and recording service used by Timbre.

As part of this release the recording container has been restarted, which will result in some short / truncated recordings during the deployment window.

We will use our recovery tooling to restore affected recordings from backup once broadcasts have reached their scheduled end.

Recovery will be run periodically until all impacted recordings have been patched.

We shall monitor new recordings from 16:00 BST onwards


Risk:

We’ve conducted through testing in the dev environment has been positive, but there remains some operational risk given the nature of the security change and the time constraints. Initial signs indicate functionality will continue as expected at the next key recording window (16:00)
Oct 22, 14:41 UTC
Update - We would like to provide a further update on our ongoing remediation efforts relating to CVE-2026-109618 and CVE-2026-109619.
Our engineering teams have now completed the priority security updates across all identified publicly accessible services.

As further technical information regarding these vulnerabilities becomes available, additional assessment and remediation may be necessary. Our engineering teams will continue to monitor developments closely and take any further action required.

We have made significant progress today and will continue to prioritise the security and integrity of our services. Further updates will be provided as appropriate.
Oct 21, 19:03 UTC
Identified - Following our earlier communication regarding security vulnerabilities CVE-2026-109618 and CVE-2026-109619, we wanted to provide a further update on our remediation efforts.

Security patches have now been released, and our engineering teams are actively deploying the necessary updates across relevant systems as a precautionary measure.

During this process, there may be minor, temporary interruptions to service as systems are updated and restarted. We are taking steps to minimise any disruption and will continue to monitor our services closely throughout the deployment.

We appreciate your patience and understanding as we work to ensure our systems remain secure and up to date.

We will provide further updates as necessary.

Kind regards,
The SharpStream Team
Oct 21, 16:36 UTC
Investigating - We are aware of the recently disclosed security vulnerabilities CVE-2026-109618 and CVE-2026-109619 and are actively reviewing the available information to assess any potential impact on our systems and services.

The situation remains fluid, with further technical details and security patches expected from the relevant maintainers.

In the meantime, our engineering teams are closely monitoring developments and preparing to deploy the necessary updates as soon as verified patches become available.

We will provide a further update once additional information is confirmed, including any relevant remediation actions.

We take the security and integrity of our services seriously and will continue to monitor the situation closely.
Oct 21, 13:24 UTC

Oct 22, 2026

Incident History Powered by Atlassian Statuspage