All Systems Operational

Live Streams Operational
90 days ago
100.0 % uptime
Today
Icecast Streams Operational
90 days ago
100.0 % uptime
Today
Monetised Streams Operational
90 days ago
100.0 % uptime
Today
On-Demand Streaming Operational
90 days ago
99.98 % uptime
Today
Standard on-demand streams Operational
90 days ago
99.97 % uptime
Today
Monetised on-demand streams Operational
90 days ago
99.97 % uptime
Today
FTP Services Operational
90 days ago
100.0 % uptime
Today
Ingress Operational
90 days ago
100.0 % uptime
Today
Audio ingests Operational
90 days ago
100.0 % uptime
Today
Premium ingests Operational
90 days ago
100.0 % uptime
Today
Portal Operational
90 days ago
100.0 % uptime
Today
Portal user access Operational
90 days ago
100.0 % uptime
Today
TimbreCMS Operational
90 days ago
100.0 % uptime
Today
TimbreCMS user access Operational
90 days ago
100.0 % uptime
Today
Analytics Operational
90 days ago
100.0 % uptime
Today
Radar User Access Operational
90 days ago
100.0 % uptime
Today
Network & Infrastructure Operational
90 days ago
99.99 % uptime
Today
Core network devices Operational
90 days ago
100.0 % uptime
Today
Transit providers Operational
90 days ago
99.99 % uptime
Today
Storage Operational
90 days ago
100.0 % uptime
Today
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.

Scheduled Maintenance

A-Feeds Ingest Server Restart (Action Required) Feb 11, 2026 00:00-01:00 UTC

During this window, we will be carrying out essential stability work on the primary ingest infrastructure that services afeeds contributions. As part of this work, a restart will be required.

What to expect:
Our afeeds ingests will experience a planned downtime of approximately 15–30 minutes during the maintenance window. Where a backup ingest contribution is configured, streams will automatically switch over to bfeeds to minimise any impact to listeners. If a bfeeds contribution is not configured, however, listeners may be disconnected or be served the failover feed or silence, depending on your streaming plan type.

Recommended action:
To help ensure uninterrupted service, we strongly encourage all live streaming customers to confirm that they have an active contribution configured to our bfeeds service. Your bfeeds contribution details can be found in Portal, should you need to set this up in advance. See our help guide for more info: https://support.sharp-stream.com/support/solutions/articles/48001215000-where-can-i-find-the-mount-information-for-encoder-contribution-

If you’d like any assistance checking your configuration, or if you have questions about the maintenance, please don’t hesitate to get in touch with our team - support@sharp-stream.com.

Thank you for your cooperation as we carry out this work to improve platform stability.

Posted on Feb 09, 2026 - 16:05 UTC
Feb 9, 2026

No incidents reported today.

Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

Feb 6, 2026

No incidents reported.

Feb 5, 2026
Completed - The scheduled maintenance has been completed.
Feb 5, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 4, 23:00 UTC
Scheduled - We will be performing maintenance on Wednesday night to safely reboot a server and maximise our infrastructure capacity and performance.

This procedure carries a small risk of audience impact should there be an unexpected error during the boot, for this reason we shall perform the work out of hours to mitigate disruption

Feb 2, 11:31 UTC
Feb 4, 2026
Feb 3, 2026

No incidents reported.

Feb 2, 2026

No incidents reported.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026
Resolved - After continual monitoring since the incident there are no signs of further widespread impact and our monitoring dashboards indicate that this was isolate to a single edge server node. We will keep this node out of service until we have conducted a root cause investigation to prevent a future failure.
Jan 30, 16:44 UTC
Monitoring - Our streaming infrastructure team identified an issue affecting one of our streaming nodes - resulting in an single edge server drop and partial audience loss across all streaming stacks.

We do not expect any further disruption from this incident - we shall continue to monitor the service to ensure continued stability.

Jan 30, 10:52 UTC
Jan 29, 2026

No incidents reported.

Jan 28, 2026

No incidents reported.

Jan 27, 2026

No incidents reported.

Jan 26, 2026

No incidents reported.