Snap One incident

We have identified a problem with OvrC service

Critical Resolved View vendor source →

Snap One experienced a critical incident on October 20, 2025 affecting Mobile App: Control4 Intercom Anywhere Android and Mobile App: OvrC and 1 more component, lasting 5h 37m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 02:01 PM UTC
Resolved
Oct 20, 2025, 07:38 PM UTC
Duration
5h 37m
Detected by Pingoru
Oct 20, 2025, 02:01 PM UTC

Affected components

Mobile App: Control4 Intercom Anywhere AndroidMobile App: OvrCMobile App: Control4 Intercom Anywhere iOSMobile App: OvrC ConnectAmazon Web ServicesMobile App: Control4 OS 2.x AndroidService: OvrC Device Communication & ConfigurationMobile App: Control4 OS 3.x AndroidService: OvrC Firmware UpdatesMobile App: Control4 OS 2.x iOS

Update timeline

  1. identified Oct 20, 2025, 02:01 PM UTC

    We are aware of the impacts on multiple services due to ongoing issues with our cloud provider. More details will follow. Thanks, Your Snap One Engineering team

  2. identified Oct 20, 2025, 02:11 PM UTC

    We are seeing additional impacts across services due to our cloud service provider

  3. identified Oct 20, 2025, 03:44 PM UTC

    The latest update from our cloud providers indicates that they continue to work to resolve network and other issues, we are actively engaged and will update as we make progress.

  4. identified Oct 20, 2025, 05:21 PM UTC

    The latest update from our cloud providers indicates that they continue to work to resolve network, lambda, and server enviornment, we are actively engaged and will update as we make progress.

  5. monitoring Oct 20, 2025, 05:46 PM UTC

    A fix has been applied by our service provider and we are seeing systems beginning to recover. You may continue to experience impacts to performance and functionality as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team

  6. resolved Oct 20, 2025, 07:38 PM UTC

    As of 3:30pm ET all of our services have fully recovered. Service impacts were caused by service failures by third-party service provider AWS. While we have observed service improvements implemented by AWS, additional information on the outage is available here: Visit AWS Status Page Thank you for your patience and understanding.