Partially Degraded Service

Uptime over the past 90 days. View historical uptime.
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 Degraded Performance
90 days ago
100.0 % uptime
Today
Audio ingests Degraded Performance
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.

No incidents or maintenance related to this downtime.

Feb 21, 2026

No incidents reported today.

Feb 20, 2026

No incidents reported.

Feb 19, 2026

No incidents reported.

Feb 18, 2026

No incidents reported.

Feb 17, 2026

No incidents reported.

Feb 16, 2026
Planned Maintenance: Timbre Scheduling & Recording Migration
Completed - The scheduled maintenance has been completed.
Feb 16, 11:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 16, 10:30 UTC
Update - The maintenance window has been rescheduled for Monday the 16th at 10:30 UTC.
Feb 10, 15:07 UTC
Scheduled - Our Development team will be working to migrate Timbre's scheduling & recording services to a cloud service. We expect no disruption in recordings.

It will be timed so that recording that have been started will continue on the old servers, and new recordings will be picked up by the new server.

While unlikely, unexpected recording issues can be recovered via our backup recording server. As such, we do not expect any impact to recording services as a result of this work.
Feb 10, 13:25 UTC
Feb 15, 2026

No incidents reported.

Feb 14, 2026

No incidents reported.

Feb 13, 2026

No incidents reported.

Feb 12, 2026
Scheduled Maintenance – Primary Ingest Infrastructure (A-feeds)
Completed - The scheduled maintenance has been completed.
Feb 12, 01:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 12, 00:00 UTC
Scheduled - Maintenance Window: 12/02/2026 00:00 - 12/02/2026 01:00

This maintenance window reflects the correct timing for the essential stability work on our primary ingest infrastructure that services A-feeds contributions.

During this window, we will be carrying out stability improvements which will require a restart.

What to expect

Our afeeds ingests will experience planned downtime of approximately 15–30 minutes during the maintenance window.

Where a backup ingest contribution is configured, streams will automatically switch over to B-feeds to minimise listener impact.

If a B-feeds contribution is not configured, listeners may be disconnected or served the failover feed or silence, depending on your streaming plan type and configuration.

Recommended action

To help ensure uninterrupted service, we strongly encourage all live streaming customers to confirm that an active contribution to our B-feeds ingest is configured.

B-feeds contribution details are available in Portal.
Help guide:
https://support.sharp-stream.com/support/solutions/articles/48001215000-where-can-i-find-the-mount-information-for-encoder-contribution-

If you would like assistance reviewing your configuration, please contact support@sharp-stream.com.

Thank you for your cooperation as we continue to improve platform stability.
Feb 11, 09:37 UTC
Feb 11, 2026
A-Feeds Ingest Server Restart (Action Required)
Completed - Yesterday’s maintenance notification was sent earlier than intended due to a scheduling error.

The planned maintenance will proceed tonight as scheduled.

We apologise for any confusion caused.
Feb 11, 01:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 11, 00:00 UTC
Scheduled - 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.
Feb 9, 16:05 UTC
Feb 10, 2026

No incidents reported.

Feb 9, 2026

No incidents reported.

Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage