Soundtrack Outage History

Started Oct 19, 2026, 02:36 PM UTC· resolved Oct 19, 2026, 04:08 PM UTC

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

   We are currently investigating an issue.

2. investigating Oct 19, 2026, 02:45 PM UTC

   Some users are seeing slow loading or errors while using our web app. Music playback may also be affected. Our Tech Team is investigating the issue and working to restore full functionality.

3. identified Oct 19, 2026, 03:44 PM UTC

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

4. monitoring Oct 19, 2026, 03:58 PM UTC

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

5. resolved Oct 19, 2026, 04:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 04:27 PM UTC· resolved Sep 28, 2026, 05:20 PM UTC

1. investigating Sep 28, 2026, 04:27 PM UTC

   We are experiencing severe latencies due to a service degradation

2. identified Sep 28, 2026, 05:02 PM UTC

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

3. identified Sep 28, 2026, 05:06 PM UTC

   A fix is rolled out and the system is currently restoring.

4. monitoring Sep 28, 2026, 05:07 PM UTC

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

5. resolved Sep 28, 2026, 05:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 08, 2026, 06:01 PM UTC· resolved Sep 08, 2026, 06:03 PM UTC

1. monitoring Sep 08, 2026, 06:01 PM UTC

   We had a temporary outage in the loadbalancer towards our content backend. A fix has been implemented and we're monitoring the situation. Apologies for the late update, we had an issue with our Statuspage interagration.

2. resolved Sep 08, 2026, 06:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 05:25 PM UTC· resolved Jun 12, 2026, 05:45 PM UTC

1. investigating Jun 12, 2026, 05:25 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Jun 12, 2026, 05:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2026, 07:35 AM UTC· resolved Jun 04, 2026, 07:56 AM UTC

1. investigating Jun 04, 2026, 07:35 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. identified Jun 04, 2026, 07:50 AM UTC

   The issue has been identified, and we're rolling out a fix. This should be resolved soon.

3. resolved Jun 04, 2026, 07:56 AM UTC

   The issue is now resolved. If you're experiencing any further issue, please reach out to [email protected]

Read the full incident report →

Started Apr 20, 2026, 07:41 AM UTC· resolved Apr 20, 2026, 07:55 AM UTC

1. investigating Apr 20, 2026, 07:41 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Apr 20, 2026, 07:55 AM UTC

   The incident was resolved.

Read the full incident report →

Started Apr 13, 2026, 08:46 AM UTC· resolved Apr 13, 2026, 08:58 AM UTC

1. investigating Apr 13, 2026, 08:46 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. monitoring Apr 13, 2026, 08:55 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

3. resolved Apr 13, 2026, 08:58 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

Read the full incident report →

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

1. investigating Mar 30, 2026, 12:31 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. identified Mar 30, 2026, 12:38 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

3. monitoring Mar 30, 2026, 01:12 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

4. resolved Mar 30, 2026, 01:26 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

Read the full incident report →

Started Mar 20, 2026, 02:27 PM UTC· resolved Mar 20, 2026, 02:51 PM UTC

1. investigating Mar 20, 2026, 02:27 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. monitoring Mar 20, 2026, 02:44 PM UTC

   A fix has been released and we are monitoring the recovery

3. resolved Mar 20, 2026, 02:51 PM UTC

   Service fully restored

Read the full incident report →

Started Mar 16, 2026, 10:13 AM UTC· resolved Mar 16, 2026, 10:37 AM UTC

1. investigating Mar 16, 2026, 10:13 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. monitoring Mar 16, 2026, 10:34 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

3. resolved Mar 16, 2026, 10:37 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

Read the full incident report →

Started Mar 09, 2026, 10:45 AM UTC· resolved Mar 09, 2026, 06:10 PM UTC

1. investigating Mar 09, 2026, 10:45 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. investigating Mar 09, 2026, 11:34 AM UTC

   We’re continuing to work on the issue, and current indications are that resolution could take some time. If you have alternative ways to play music, we recommend using those in the meantime. Our team is fully engaged and working with highest priority to resolve this as quickly as possible. We’ll share updates as soon as we have more information.

3. investigating Mar 09, 2026, 11:57 AM UTC

   Update: Things are now moving in the right direction and the situation is improving. That said, we’re still dealing with some remaining effects from the incident and are continuing our work to fully stabilise the service. Thank you for your patience, we’ll keep you updated as we make further progress.

4. investigating Mar 09, 2026, 12:37 PM UTC

   Update: The previous solution didn’t fully resolve the issue. Our team is actively working on alternative ways to fix it as quickly as possible. We understand this may be disruptive and sincerely appreciate your patience. We’ll continue to provide updates as we make progress.

5. investigating Mar 09, 2026, 01:37 PM UTC

   Update: We are actively working on alternative ways to resolve the issue as quickly as possible. We understand this may be disruptive and sincerely appreciate your patience. We will continue to provide updates as we make progress.

6. investigating Mar 09, 2026, 02:26 PM UTC

   Update: We are continuing to actively work on resolving the issue as quickly as possible. We understand this may be disruptive and sincerely appreciate your patience. We will continue to provide updates as we make progress.

7. identified Mar 09, 2026, 04:34 PM UTC

   Update: We’ve narrowed down the issue and are starting to see improvements. We will continue to investigate and monitor the situation closely. We understand this may be disruptive and sincerely appreciate your patience. We’ll keep you updated as we make progress.

8. monitoring Mar 09, 2026, 05:02 PM UTC

   We’ve applied the currently necessary backend configuration to address the issue and are currently monitoring progress. It may take a little time for the situation to be fully resolved, but we’ll keep you informed. We understand this may be disruptive and sincerely appreciate your patience. We’ll continue to provide updates as we make progress.

9. resolved Mar 09, 2026, 06:10 PM UTC

   The incident was caused by an issue with our third-party hosting provider. While the problem was ongoing, we actively explored alternative ways to mitigate the impact. As a result of this incident, some devices may have become unpaired and will need to be re-paired. Music that was already played or cached should have worked, but there may have been difficulties updating to new schedules or playlists. With that said, everything should be back to normal now. If you notice any further issues, please contact us at [email protected]

10. postmortem Mar 13, 2026, 12:31 PM UTC

    # **Incident Report: Resilience, Recovery and Our Commitment to You** **Date:** March 12, 2026 10:45 UTC **Subject:** A transparent look at the March 9th service disruption At **Soundtrack Technologies**, we know that when our service stops, your business is affected. On Monday, March 9th, we faced a complex technical challenge that tested our systems. We want to share the story of what happened, how our teams responded, and the concrete steps we are taking to ensure we stay ahead of similar issues in the future. ### **The incident story** The incident began when one of our primary cloud infrastructure providers, experienced an internal service disruption. This coincided with an automated update to our server clusters. While our systems have built-in fallback mechanisms, this specific combination hit an edge-case that bypassed several of our standard redundancies. As the cloud provider’s systems attempted to upgrade, they entered us in a degraded state, leading to intermittent connectivity across our core services. To our users, this manifested in three frustrating ways: 1. **The "White Screen":** Many users saw a blank loading loop without an error message. 2. **Management Lockout:** The tools used to manage music and business accounts were temporarily unreachable. 3. **Playback Interruptions:** While our local caching kept music playing for many, some devices were disconnected because the authentication service could not verify sessions during the cloud update. ### **We Heard You** During the incident, we received a lot of feedback. We want to address the most important sentiments we heard: * **"Is it me or you?"** Many of you spent valuable time troubleshooting your own hardware—restarting iPads and checking Wi-Fi—only to find the issue was on our side. * **The Dreaded Loading Loop:** A blank screen without information causes significant confusion. You weren't sure if the app was broken or just slow. * **The Awkward Silence:** When the music stops and you cannot log in to fix it, it affects your guests and your atmosphere. We understand that responsibility. ### **Our 24/7 Response and Resolution** Our Site Reliability Engineering \(SRE\) team operates on a 24/7 model, ensuring expert eyes are on our systems every second of the day. Within minutes of the first anomaly, our on-call engineers established a centralized "War Room." Because the root cause sat within a third-party provider's infrastructure, our team took manual control to shield our customers. Our engineers manually took control over the "Control Plane"—the brain of our server clusters—and strategically restarted services in a specific sequence to restore traffic. Even as our systems were hit with **14x the normal traffic** from devices trying to reconnect, our team stabilized the platform and fully restored services by **18:10 UTC**, when the third-party cloud provider’s incident was resolved. It’s unusual for incidents to last for several hours as we’re typically able to resolve issues very quickly, making this incident one of the longest-running in Soundtrack history. ### **Turning Lessons into Action** A mature SRE culture is defined by how it learns. We are not just "fixing" this incident; we are evolving because of it. We have initiated a comprehensive roadmap of **over 15 high-priority action points** to prevent a recurrence: * **Enhanced Communication:** While we currently display a Statuspage pop-up in the web app, we are developing a dedicated **“Major Incident Error Page”** for our apps. If an outage occurs, you’ll immediately know it’s on our side—so you won’t have to spend time troubleshooting your own Wi-Fi. * **White screen issue:** We are also improving the messaging shown during the white screen loading state that many of you have experienced. * **Technical Resilience:** We are updating the "Circuit Breakers" to handle massive traffic surges and investigating multi-region, High-Availability \(HA\) setups for our most critical services to reduce dependence on any single cloud provider zone. * **Resilient Pairing:** We are updating our internal logic to ensure that even if a service returns a temporary error, your devices won't "unpair" or log you out unnecessarily. * **Smarter Maintenance:** We are separating our maintenance windows so that infrastructure updates never happen simultaneously across different parts of our system, ensuring our monitoring tools remain online even during upgrades. ### **Our Commitment** We pride ourselves on our technical maturity, but we pride ourselves more on the trust you place in us to provide the soundtrack to your day. Our 24/7 team remains vigilant, and we thank you for the candid feedback that helps us build a more robust, professional, and resilient platform. Please make sure to subscribe to our [Status page updates](https://status.soundtrack.io/), to be notified when an incident happens. — **The Soundtrack Support & Site Reliability Engineering Team**

Read the full incident report →

Started Mar 03, 2026, 03:51 PM UTC· resolved Mar 03, 2026, 04:03 PM UTC

1. identified Mar 03, 2026, 03:51 PM UTC

   We're aware that some users are experiencing limited functionality while browsing our website and app. Our team is on the case and working to restore all features. We understand how important this is and thank you for your patience as we resolve this matter.

2. identified Mar 03, 2026, 03:57 PM UTC

   We're aware that some users are experiencing load errors while browsing our website. Our team is on the case and working on a solution.

3. monitoring Mar 03, 2026, 04:00 PM UTC

   We're aware that some users are experiencing load errors while browsing our website. Our team has deployed a solution and is monitoring the situation

4. resolved Mar 03, 2026, 04:03 PM UTC

   The incident was resolved.

Read the full incident report →

Started Feb 27, 2026, 08:13 AM UTC· resolved Feb 27, 2026, 08:17 AM UTC

1. identified Feb 27, 2026, 08:13 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Feb 27, 2026, 08:17 AM UTC

   The incident was resolved.

Read the full incident report →

Started Feb 04, 2026, 02:07 PM UTC· resolved Feb 04, 2026, 02:52 PM UTC

1. investigating Feb 04, 2026, 02:07 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Feb 04, 2026, 02:52 PM UTC

   The incident was resolved.

Read the full incident report →

Started Feb 03, 2026, 06:27 PM UTC· resolved Feb 03, 2026, 07:23 PM UTC

1. investigating Feb 03, 2026, 06:27 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Feb 03, 2026, 07:23 PM UTC

   The incident was resolved.

Read the full incident report →

Started Jan 25, 2026, 03:26 PM UTC· resolved Jan 25, 2026, 03:59 PM UTC

1. investigating Jan 25, 2026, 03:26 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Jan 25, 2026, 03:59 PM UTC

   The incident was resolved.

Read the full incident report →

Started Jan 15, 2026, 08:06 AM UTC· resolved Jan 15, 2026, 08:23 AM UTC

1. investigating Jan 15, 2026, 08:06 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. identified Jan 15, 2026, 08:16 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

3. monitoring Jan 15, 2026, 08:19 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

4. resolved Jan 15, 2026, 08:23 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

Read the full incident report →

Started Dec 05, 2025, 09:14 AM UTC· resolved Dec 05, 2025, 09:24 AM UTC

1. investigating Dec 05, 2025, 09:14 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Dec 05, 2025, 09:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 24, 2025, 12:37 PM UTC· resolved Nov 24, 2025, 01:29 PM UTC

1. investigating Nov 24, 2025, 12:39 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. monitoring Nov 24, 2025, 01:27 PM UTC

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

3. resolved Nov 24, 2025, 01:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 21, 2025, 11:35 AM UTC· resolved Nov 24, 2025, 09:07 AM UTC

1. investigating Nov 21, 2025, 11:35 AM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. monitoring Nov 21, 2025, 03:00 PM UTC

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

3. monitoring Nov 21, 2025, 03:02 PM UTC

   We have identified the issue and some users (2-3%) of our mobile and desktop apps are affected. The app momentarily lost its sound zone pairing. We expect this to automatically recover in most cases, but some users might need to re-pair their player by pressing "Take over playback" from the app, or by pairing again from the web UI.

4. resolved Nov 24, 2025, 09:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 11:54 AM UTC· resolved Nov 18, 2025, 03:36 PM UTC

1. investigating Nov 18, 2025, 11:54 AM UTC

   We are currently experiencing a complete service outage and degradation stemming from a critical issue with one of our core third-party providers.

2. investigating Nov 18, 2025, 11:58 AM UTC

   We are currently experiencing a complete service outage and degradation stemming from a critical issue with one of our core third-party providers.

3. investigating Nov 18, 2025, 01:43 PM UTC

   We are continuing to investigate this issue.

4. investigating Nov 18, 2025, 02:08 PM UTC

   We are currently experiencing an external service interruption that is affecting our website, playback and other parts of the application. This is due to an outage with Cloudflare, which is a core service provider for many major websites and platforms, including ours. We sincerely apologize for the inconvenience this is causing. Please be assured that this issue is currently not an internal fault with Soundtrack, and our team is monitoring the situation closely. As soon as Cloudflare resolves their outage, our service will automatically return to normal. Temporary workaround is to play cached music which you've already played before. We appreciate your patience while this third-party service is being restored.

5. monitoring Nov 18, 2025, 02:51 PM UTC

   Cloudflare (our third-party service) has implemented a fix and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal.

6. resolved Nov 18, 2025, 03:36 PM UTC

   Everything is now operating normally and we are resolving this incident as no further issues are observed. If you experience any additional problems, please contact us at: [email protected]

Read the full incident report →

Started Nov 10, 2025, 03:05 PM UTC· resolved Nov 10, 2025, 03:46 PM UTC

1. investigating Nov 10, 2025, 03:05 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Nov 10, 2025, 03:46 PM UTC

   The incident was resolved.

Read the full incident report →

Started Aug 01, 2025, 04:09 PM UTC· resolved Aug 01, 2025, 04:29 PM UTC

1. investigating Aug 01, 2025, 04:09 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved Aug 01, 2025, 04:29 PM UTC

   The incident was resolved.

Read the full incident report →

Started Jun 12, 2025, 06:20 PM UTC· resolved Jun 12, 2025, 09:12 PM UTC

1. investigating Jun 12, 2025, 06:20 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. investigating Jun 12, 2025, 06:35 PM UTC

   We regret to inform you that our platform is currently experiencing a critical outage that is affecting most of our services. We are having issues with our Cloud Provider and investigating solutions.

3. identified Jun 12, 2025, 07:08 PM UTC

   We're currently experiencing a critical outage impacting most of our services. This is due to an issue with our cloud provider, and we're actively investigating solutions. We will provide our next update within 60 minutes.

4. identified Jun 12, 2025, 07:51 PM UTC

   We're pleased to report that we have restored functionality for some of our services following the earlier critical outage related to our cloud provider. While certain services are now accessible, we are not yet fully back to normal and continue to work diligently on restoring full platform stability. We are actively monitoring the situation and investigating solutions for remaining impacted services. We will provide our next update within 60 minutes.

5. identified Jun 12, 2025, 08:39 PM UTC

   Our last update remains consistent: we've restored some services, but our platform is not yet fully back to normal due to the cloud provider issue. Our teams are continuing to work diligently on resolving the remaining impacts and restoring full stability. We appreciate your continued patience as we focus on these efforts. We will provide our next update within 60 minutes.

6. monitoring Jun 12, 2025, 08:54 PM UTC

   We're pleased to report significant progress in restoring our services! The majority of our platform is now operational and accessible, as we've made substantial headway in addressing the cloud provider issue. We anticipate providing another update within 60 minutes, or sooner if full resolution is achieved.

7. resolved Jun 12, 2025, 09:12 PM UTC

   We're pleased to confirm that all services are now fully operational and performing as expected. The earlier critical outage, caused by an issue with our cloud provider, has been successfully resolved. We sincerely apologize for any disruption this incident may have caused. Our teams worked diligently to restore full functionality, and we will continue to monitor our systems closely. Thank you for your patience and understanding.

Read the full incident report →

Started May 28, 2025, 05:36 PM UTC· resolved May 28, 2025, 07:52 PM UTC

1. investigating May 28, 2025, 05:36 PM UTC

   We regret to inform you that our platform is currently experiencing a partial outage that is affecting some services. Users may encounter difficulties accessing any part of our platform, including website, app, and customer support channels.

2. resolved May 28, 2025, 07:52 PM UTC

   The incident was resolved.

Read the full incident report →