SoundStack Outage History

Started Oct 21, 2026, 07:39 PM UTC· resolved Oct 22, 2026, 02:07 AM UTC

1. monitoring Oct 21, 2026, 07:39 PM UTC

   We observed a brief period of increased network latency at our Dallas data center (DAL03), lasting approximately 30–60 seconds. The issue has been mitigated, and we are closely monitoring the situation. We will provide further updates as needed. Thank you for your patience and understanding.

2. resolved Oct 22, 2026, 02:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 19, 2026, 02:19 PM UTC· resolved Oct 19, 2026, 06:32 PM UTC

1. investigating Oct 19, 2026, 02:19 PM UTC

   We are currently investigating an issue affecting the Live365 Dashboard, which may result in failed requests or service disruptions. Our engineering team is actively working to identify and resolve the issue. We will provide further updates as more information becomes available.

2. monitoring Oct 19, 2026, 04:17 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 19, 2026, 06:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 12, 2026, 09:08 PM UTC· resolved Sep 13, 2026, 01:18 AM UTC

1. investigating Sep 12, 2026, 09:08 PM UTC

   We’re currently experiencing intermittent connectivity issues affecting a portion of SoundStack services in the US-WEST region due to a network routing issue. Our team is actively working to restore normal traffic flow. Built-in redundancy is helping minimize customer impact while we work toward full resolution. We’re closely monitoring the situation and will provide additional updates as more information becomes available.

2. identified Sep 12, 2026, 09:33 PM UTC

   We’ve identified the source of the connectivity issues affecting a portion of SoundStack services in the US-WEST region and have taken mitigation steps. Traffic is beginning to stabilize, and our team is closely monitoring recovery. We’ll provide another update as the situation progresses.

3. monitoring Sep 12, 2026, 10:10 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Sep 13, 2026, 01:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 12, 2026, 04:03 AM UTC· resolved Aug 12, 2026, 02:12 PM UTC

1. investigating Aug 12, 2026, 04:03 AM UTC

   SoundStack is currently investigating a network connectivity issue affecting a subset of our Europe-based live streaming services. The affected services are experiencing a service disruption while we work to identify the cause and restore normal connectivity. We will provide additional updates as more information becomes available.

2. identified Aug 12, 2026, 04:09 AM UTC

   We have identified the issue as originating with an upstream provider supporting a portion of our European footprint. The provider is actively investigating the underlying connectivity issue. Impact remains limited to a subset of our Europe-based live streaming services, and we will continue to provide updates as more information becomes available.

3. monitoring Aug 12, 2026, 04:38 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Aug 12, 2026, 02:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 27, 2026, 09:34 AM UTC· resolved May 28, 2026, 11:58 AM UTC

1. identified May 27, 2026, 09:34 AM UTC

   We are currently investigating an infrastructure-related issue affecting parts of the Accounts platform, which may cause intermittent disruptions or degraded performance for some users. Our engineering team is actively working to stabilize the affected services and minimize impact. We’ll continue to share updates as more information becomes available.

2. resolved May 28, 2026, 11:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2026, 08:49 PM UTC· resolved May 22, 2026, 07:55 AM UTC

1. investigating May 21, 2026, 08:49 PM UTC

   Our engineering team is currently investigating an issue causing intermittent disruptions on the Podcaster platform. We are actively working to identify the root cause and restore full service as quickly as possible. We appreciate your patience and will continue to share updates as more information becomes available.

2. monitoring May 21, 2026, 09:34 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved May 22, 2026, 07:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 19, 2026, 01:37 PM UTC· resolved May 19, 2026, 03:36 PM UTC

1. investigating May 19, 2026, 01:37 PM UTC

   Some users might be experiencing difficulties accessing their accounts and logging in. Our engineering team is actively investigating the issue and working to resolve it as quickly as possible.

2. resolved May 19, 2026, 03:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 09, 2026, 08:12 AM UTC· resolved Apr 09, 2026, 09:47 AM UTC

1. investigating Apr 09, 2026, 08:12 AM UTC

   We are currently investigating a network-related incident affecting a subset of services. Our team is actively working to identify the root cause and restore full service as quickly as possible.

2. investigating Apr 09, 2026, 08:15 AM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 09, 2026, 08:35 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Apr 09, 2026, 09:47 AM UTC

   The incident affecting a subset of services has been resolved, and all impacted systems are now operating normally. Our team will continue monitoring the environment closely, and we will share a full Root Cause Analysis once it is completed.

5. postmortem Apr 09, 2026, 04:34 PM UTC

   On April 9, 2026, between approximately 06:58 UTC and 08:43 UTC, a subset of services in the US-Central environment experienced connectivity issues. ## **What Happened** During routine maintenance activity within the US-Central environment, a network configuration issue caused a disruption to connectivity between parts of the Soundstack and Live365 platform and its control services. As a result, some services were unable to start or recover normally during the incident window. Both existing and new workloads were impacted during this time. Existing services experienced degraded behavior due to loss of connectivity, while new or restarting services could remain unavailable until communication was restored. ## **Resolution** Our engineering team identified the issue and implemented a temporary routing adjustment, followed by a DNS change at approximately 08:18 UTC to restore platform communication. Services began recovering immediately after this change, with most functionality restored by approximately 08:33 UTC. Full service recovery, including resolution of residual failures and verification of system stability, was completed by approximately 08:43 UTC. ## **Preventive Actions** To reduce the possibility of similar incidents in the future, we are implementing the following improvements: * Restricting unattended maintenance activity on critical infrastructure nodes * Upgrading core network failover components to versions with improved health monitoring and self-recovery capabilities * Reviewing recovery procedures to further reduce restoration time We apologize for the disruption and appreciate your patience while the issue was resolved.

Read the full incident report →

Started Mar 26, 2026, 10:12 PM UTC· resolved Mar 29, 2026, 03:26 PM UTC

1. investigating Mar 26, 2026, 10:12 PM UTC

   One of our primary EU datacenter partners is currently experiencing a network-level routing issue, which has impacted service availability. Our monitoring systems detected the issue immediately, and our engineering team is actively investigating. We are working closely with the datacenter provider to resolve the problem as quickly as possible. Due to SoundStack's advanced redundancy, only partners with encoders that are only pushing to this location are affected. We sincerely apologize for the disruption your station may have experienced and for any inconvenience caused to you and your listeners.

2. investigating Mar 26, 2026, 10:51 PM UTC

   We are continuing to investigate this issue.

3. identified Mar 26, 2026, 10:55 PM UTC

   Our datacenter partner has confirmed that the issue is related to a backbone connectivity disruption affecting network routing. Work is actively underway on their side to restore full service, and we are continuing to monitor the situation closely. We are seeing signs of progress and will share further updates as they become available. We appreciate your continued patience and understanding while this is being resolved.

4. monitoring Mar 27, 2026, 12:25 AM UTC

   Connectivity has been restored following a temporary fix implemented by our datacenter partner, and services are now returning to normal. We are continuing to monitor the situation closely to ensure stability while additional measures are implemented to fully address the issue. Thank you for your patience during this time.

5. monitoring Mar 27, 2026, 11:22 PM UTC

   Update – Monitoring / Near Resolution We are continuing to monitor the situation following the mitigation implemented by our datacenter partner. The disruption was related to underlying network infrastructure issues impacting connectivity in the region. While mitigation measures have been effective, our team remains in close coordination with the provider as they complete final remediation work. At this time, we believe we are approaching full resolution. If conditions remain stable, we expect to close this incident tomorrow. Thank you again for your patience and understanding throughout this incident.

6. resolved Mar 29, 2026, 03:26 PM UTC

   Resolved The incident affecting our EU datacenter network has been resolved. Our datacenter partner has completed remediation work, and network stability has been fully restored. We have continued to monitor the situation and have confirmed that services are operating normally. We appreciate your patience and understanding throughout this incident. If you continue to experience any issues, please don’t hesitate to reach out to our support team.

Read the full incident report →

Started Mar 26, 2026, 08:31 PM UTC· resolved Mar 30, 2026, 01:56 PM UTC

1. investigating Mar 26, 2026, 08:31 PM UTC

   Our engineering team is currently investigating an issue that is causing intermittent disruptions on the Arm/Insights platform. Please note that no statistical data is impacted by this incident—only platform access is affected. We are actively working to identify the root cause and implement a resolution.

2. identified Mar 26, 2026, 09:19 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Mar 26, 2026, 09:23 PM UTC

   A fix has been implemented and we are monitoring the results.

4. investigating Mar 27, 2026, 01:56 PM UTC

   After further review this morning, we’ve observed some anomalies in reporting, so we’ve moved the incident back to Investigating while our team continues to dig into the root cause. We’ll keep you posted as we learn more.

5. identified Mar 27, 2026, 03:01 PM UTC

   The issue has been identified and a fix is being implemented.

6. monitoring Mar 28, 2026, 05:27 PM UTC

   A fix has been implemented and we are monitoring the results.

7. resolved Mar 30, 2026, 01:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 25, 2026, 10:21 AM UTC· resolved Mar 26, 2026, 07:31 PM UTC

1. investigating Mar 25, 2026, 10:21 AM UTC

   We’re currently experiencing an increase in false positive alerts from our stream monitoring systems. Our team is actively investigating the cause of these alerts and working to restore normal monitoring accuracy. We’ll continue to provide updates as more information becomes available.

2. investigating Mar 25, 2026, 05:45 PM UTC

   Update – Monitoring System We have identified the issue causing increased false positive alerts in our monitoring system and are actively working toward a full resolution. This issue is limited to monitoring accuracy and does not impact stream delivery or uptime. As a temporary mitigation, we have disabled automated monitoring alerts to prevent unnecessary notifications. Customers will not receive alert emails while this is in place. No action is required on your end. We are continuing to make progress and will restore alerting once accuracy has been fully resolved. We will share further updates as work continues.

3. resolved Mar 26, 2026, 07:31 PM UTC

   Resolved – Monitoring System Monitoring accuracy has remained stable over the past 24 hours, and alerting is now functioning as expected. Following the fixes implemented, we have not observed any further false positive alerts. As a result, this incident is now considered resolved, and normal monitoring operations have been fully restored. We will continue to keep an eye on the system as part of our standard processes to ensure continued stability. Thank you for your patience and understanding while we worked through this.

Read the full incident report →

Started Mar 24, 2026, 05:27 PM UTC· resolved Mar 25, 2026, 05:04 PM UTC

1. monitoring Mar 24, 2026, 05:27 PM UTC

   We identified an issue affecting the Analytics & Reporting Manager (Insights), where the Peak Listeners graph was not updating correctly and appeared static. A hotfix has now been deployed, restoring the data, as a result, the graph will now reflect accurate values moving forward. We will continue monitoring the situation to ensure stability. We appreciate your patience and understanding.

2. resolved Mar 25, 2026, 05:04 PM UTC

   The issue affecting the Analytics & Reporting Manager (Insights), where the Peak Listeners graph was not updating correctly, has now been fully resolved. We have continued to monitor the system after the fix was applied and have not observed any further anomalies. Stability has been confirmed. We appreciate your patience while this issue was being investigated and resolved. If you notice anything unexpected, please don’t hesitate to reach out to our support team.

Read the full incident report →

Started Mar 10, 2026, 11:05 PM UTC· resolved Mar 11, 2026, 03:21 AM UTC

1. investigating Mar 10, 2026, 11:05 PM UTC

   We are currently investigating an incident affecting network infrastructure in one of our Dallas data centers (DAL03). Our engineering team is actively working to identify the root cause and resolve the issue. We will provide further updates as more information becomes available. Thank you for your patience and understanding.

2. monitoring Mar 10, 2026, 11:25 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 11, 2026, 03:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 18, 2026, 02:51 PM UTC· resolved Feb 18, 2026, 09:08 PM UTC

1. investigating Feb 18, 2026, 02:51 PM UTC

   Our Engineering team is currently investigating an issue affecting some Live365 stations that are experiencing problems when switching between streaming modes: AutoDJ and LiveDJ.

2. identified Feb 18, 2026, 05:18 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Feb 18, 2026, 07:15 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Feb 18, 2026, 09:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 05:15 PM UTC· resolved Dec 05, 2025, 07:59 PM UTC

1. investigating Dec 05, 2025, 05:15 PM UTC

   We have identified an issue that is causing intermittent issues preventing broadcasters from completing certain actions on the Live365 Dashboard. Our engineering team is actively investigating this issue and will provide updates throughout the investigation.

2. identified Dec 05, 2025, 05:34 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Dec 05, 2025, 06:00 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Dec 05, 2025, 07:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 02:24 PM UTC· resolved Nov 18, 2025, 05:54 PM UTC

1. investigating Nov 18, 2025, 02:24 PM UTC

   We are currently investigating reports of intermittent issues with multiple services. This is potentially linked to a major ongoing incident at Cloudflare, one of our infrastructure partners. Cloudflare has reported an "internal service degradation" and is working to restore service. We are monitoring our systems closely and will provide an update as soon as we have more information.

2. resolved Nov 18, 2025, 05:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 14, 2025, 09:44 AM UTC· resolved Nov 14, 2025, 04:16 PM UTC

1. investigating Nov 14, 2025, 09:44 AM UTC

   SoundStack is currently investigating a disruption to our Live Streaming Ingest service in the EU-CENTRAL region. Further updates will be provided as they become available.

2. monitoring Nov 14, 2025, 10:25 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Nov 14, 2025, 04:16 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 13, 2025, 06:01 PM UTC· resolved Nov 13, 2025, 09:07 PM UTC

1. investigating Nov 13, 2025, 06:01 PM UTC

   We are currently investigating an issue causing intermittent unavailability of the Login service. Our engineering team is actively looking into the cause. More updates will be provided as they become available.

2. identified Nov 13, 2025, 06:35 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Nov 13, 2025, 07:10 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Nov 13, 2025, 09:07 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 12, 2025, 06:22 PM UTC· resolved Nov 12, 2025, 08:59 PM UTC

1. investigating Nov 12, 2025, 06:22 PM UTC

   Our engineering team is currently investigating a network incident affecting one of our sites in the US-Central region. Some customers may experience intermittent connectivity issues or brief disruptions. We are actively working to identify the root cause and will provide updates as more information becomes available. Thank you for your patience and understanding.

2. identified Nov 12, 2025, 07:24 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Nov 12, 2025, 07:55 PM UTC

   Our engineering team identified and mitigated the issue that caused temporary service instability. Performance has returned to normal, and we continue to monitor the environment to ensure ongoing stability. Thank you for your patience as we work to maintain optimal service performance.

4. resolved Nov 12, 2025, 08:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 31, 2025, 01:19 PM UTC· resolved Oct 31, 2025, 09:38 PM UTC

1. investigating Oct 31, 2025, 01:19 PM UTC

   Our team is currently investigating a network incident affecting one of our sites in the US-Central region. We will provide more details as they become available.

2. monitoring Oct 31, 2025, 02:55 PM UTC

   Some streams and services hosted in the US-Central region may have experienced intermittent connectivity issues as routing reconverged. Our team has implemented corrective measures and is moving the incident to Monitoring while we continue to observe the situation to ensure stability.

3. resolved Oct 31, 2025, 09:38 PM UTC

   We’ve identified that the issue was caused by an upstream provider. The incident has now been resolved, and we’re actively working with the provider to ensure measures are in place to prevent a recurrence.

Read the full incident report →

Started Oct 30, 2025, 09:26 PM UTC· resolved Oct 31, 2025, 12:12 AM UTC

1. investigating Oct 30, 2025, 09:26 PM UTC

   We’ve identified an issue affecting certain Live365 Dashboard functions, which may prevent some users from performing specific actions on their accounts. Our engineering team is actively investigating to restore full functionality as quickly as possible. Thank you for your patience and understanding.

2. monitoring Oct 30, 2025, 09:56 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 31, 2025, 12:12 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 22, 2025, 06:14 PM UTC· resolved Nov 03, 2025, 05:32 PM UTC

1. investigating Oct 22, 2025, 06:14 PM UTC

   We’re currently experiencing an increase in false positive alerts from our stream monitoring systems. Our team is actively investigating the cause of these alerts and working to restore normal monitoring accuracy. We’ll continue to provide updates as more information becomes available.

2. monitoring Oct 29, 2025, 11:40 PM UTC

   Engineering team identified an issue affecting monitoring service responsiveness and implemented corrective actions. The service is now operating normally, and we are continuing to monitor closely to ensure full stability.

3. monitoring Oct 31, 2025, 12:35 AM UTC

   While monitoring the service, we discovered that the issue was not completely resolved. The engineering team has implemented additional corrective actions to address the remaining impact. We will continue to monitor the service closely to ensure stability and identify any further disruptions.

4. resolved Nov 03, 2025, 05:32 PM UTC

   The stream monitoring service has remained stable following our recent corrective actions. Our team will continue to monitor performance to ensure continued stability. At this time, we consider this incident resolved. If you experience any related issues, please reach out to us through our support portal.

Read the full incident report →

Started Aug 25, 2025, 10:21 PM UTC· resolved Aug 26, 2025, 12:47 AM UTC

1. investigating Aug 25, 2025, 10:21 PM UTC

   We are investigating network instability issues affecting multiple sites. We will provide an update as soon as we have more information. Thank you for your patience.

2. monitoring Aug 25, 2025, 10:45 PM UTC

   The issue has been identified as an incident with a network transport vendor within Frankfurt. Network traffic is now returning to normal. We continue to monitor stability and will provide a final update shortly.

3. resolved Aug 26, 2025, 12:47 AM UTC

   We have confirmed that this incident had minimal impact on listener traffic. The disruption was limited to traffic traversing through Frankfurt before reaching SoundStack’s network. All services are now fully stable.

Read the full incident report →

Started Aug 25, 2025, 09:43 PM UTC· resolved Aug 26, 2025, 12:44 AM UTC

1. investigating Aug 25, 2025, 09:43 PM UTC

   We are currently investigating a potential network issue impacting one of our US-EAST data center sites. We will share more updates as soon as we have additional details. Thank you for your patience and understanding.

2. resolved Aug 26, 2025, 12:44 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 30, 2025, 06:42 AM UTC· resolved Jul 30, 2025, 09:32 PM UTC

1. investigating Jul 30, 2025, 06:42 AM UTC

   We’re currently looking into a potential network issue at one of our US-CENTRAL data centers. We will share more updates as soon as we have additional details. Thank you for your patience and understanding!

2. monitoring Jul 30, 2025, 07:54 AM UTC

   The network at our US-CENTRAL data center has stabilized, and services are operating normally. We’re continuing to monitor the situation closely and will share more details as they become available. Thank you for your continued patience and understanding.

3. resolved Jul 30, 2025, 09:32 PM UTC

   One of our upstream network providers (Level 3) experienced intermittent connectivity issues in the US-CENTRAL (Dallas) region, causing brief disruptions as traffic shifted between carriers. During these periods, alternate providers successfully handled most of the traffic.

Read the full incident report →