- Detected by Pingoru
- May 18, 2026, 04:06 PM UTC
- Resolved
- May 18, 2026, 05:11 PM UTC
- Duration
- 1h 5m
Affected: Service: OvrC Notifications
Timeline · 4 updates
-
identified May 18, 2026, 04:06 PM UTC
Delivery of emails from OvrC may be impacted based on an identified issue with one of our service providers. This includes device status notifications, Control4 and Luma customer hand-off invites, Control4 demo invites, MFA when using email delivery. More details will follow. Thanks, Your Snap One Engineering team
-
monitoring May 18, 2026, 04:28 PM UTC
The fix has been applied and email delivery latency is returning to nominal levels. You may experience slight impacts to performance as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
monitoring May 18, 2026, 04:44 PM UTC
Regarding the impact of this issue, emails that would have been generated between 7:10am and 12:25pm EDT will not be delivered. Currently, systems are operating nominally and all emails generated after 12:25pm EDT should be delivered. We are monitoring closely to ensure there is no further impact before we change the status of this issue to Resolved. Thank you for your understanding, Your Snap One Engineering team
-
resolved May 18, 2026, 05:11 PM UTC
As of 12:25pm EDT the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 06:46 PM UTC
- Resolved
- Apr 20, 2026, 07:07 PM UTC
- Duration
- 20m
Affected: Service: Control4 Access AnywhereService: Control4 Composer ExpressService: Control4 Composer Pro
Timeline · 2 updates
-
monitoring Apr 20, 2026, 06:46 PM UTC
We identified an issue that degraded Composer Pro remote access and certain legacy Control4 remote connections. A fix has been issued and Composer Pro remote connections are now working, though connection times may be slower than normal as services continue to come back online and fully stabilize. Integrator impact: Remote access using legacy Control4 OS2 and OS3 connectivity, including legacy remote Composer workflows and some cloud‑connected drivers, was affected during this incident. End‑customer impact: Customers using legacy Control4 OS2 or older OS3 environments may have experienced degraded access for services relying on legacy connectivity, including the legacy Control4 mobile app, Alexa, Google, and other web‑connected drivers. Customers running the latest supported software on Control4 OS3 or Control4 X4 are not impacted. We will continue to monitor closely and provide additional updates as services fully stabilize. Thanks, Your Snap One Engineering team
-
resolved Apr 20, 2026, 07:07 PM UTC
As of 3:00pm ET the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Apr 04, 2026, 05:29 PM UTC
- Resolved
- Apr 06, 2026, 01:37 PM UTC
- Duration
- 1d 20h
Timeline · 4 updates
-
investigating Apr 04, 2026, 05:29 PM UTC
We are aware of an issue affecting camera event media in the Control4 app. When accessing recorded camera events through the History experience, users may see a message stating "Media for this event is processing and will be available soon." Live camera streams are not affected by this issue. Our engineering team has identified the area of impact and is actively working toward a resolution. More details will follow. Thanks, Your Snap One Engineering team
-
identified Apr 04, 2026, 05:57 PM UTC
We have identified a fix, new events should be showing properly, older events may still be unavailable for a period while our servers update
-
monitoring Apr 04, 2026, 05:58 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 06, 2026, 01:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 03:11 PM UTC
- Resolved
- Mar 17, 2026, 03:34 PM UTC
- Duration
- 22m
Affected: Mobile App: OvrCMobile App: OvrC ConnectService: OvrC Device Communication & ConfigurationService: OvrC Firmware UpdatesService: OvrC LoginService: OvrC NotificationsService: OvrC Public APIsService: OvrC Web ConnectService: OvrC Speed TestService: OvrC MFA - SMSService: OvrC Account Creation
Timeline · 2 updates
-
monitoring Mar 17, 2026, 03:11 PM UTC
An issue impacting the performance of OvrC is being monitored. The root cause has been identified and the fix has been applied. OvrC is returning to normal with Partners able to use services. You may experience slight impacts to performance as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Mar 17, 2026, 03:34 PM UTC
As of 11:13am ET the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 12:59 AM UTC
- Resolved
- Mar 03, 2026, 04:57 AM UTC
- Duration
- 3h 57m
Affected: Mobile App: Control4 Intercom Anywhere AndroidMobile App: Control4 Intercom Anywhere iOSService: Control4 Access AnywhereService: Control4 AlexaService: Control4 APIsService: Control4 Composer ProService: Control4 Google AssistantService: Control4 Intercom AnywhereService: Control4 Storage
Timeline · 2 updates
-
monitoring Mar 03, 2026, 12:59 AM UTC
An issue was detected with a critical piece of infrastructure in the Control4 cloud platform. This issue has been remediated and the Control4 Cloud is returning to normal with Partners and Customer able to use services. You may experience slight impacts to performance as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Mar 03, 2026, 04:57 AM UTC
As of 11:45pm ET the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 01:54 PM UTC
- Resolved
- Feb 06, 2026, 05:43 PM UTC
- Duration
- 2d 3h
Affected: Service: Control4 Intercom Anywhere
Timeline · 6 updates
-
identified Feb 04, 2026, 01:54 PM UTC
We are aware of the impacts on Intercom Anywhere and are actively engaged in determining the cause. More details will follow. Thanks, Your Snap One Engineering team
-
identified Feb 04, 2026, 02:17 PM UTC
We are continuing to work on a fix for this issue.
-
identified Feb 04, 2026, 02:22 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Feb 04, 2026, 02:47 PM UTC
The fix has been applied and Intercom Anywhere is returning to normal with Partners and Customers able to use services. You may experience slight impacts to performance as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
monitoring Feb 04, 2026, 03:41 PM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 06, 2026, 05:43 PM UTC
As of 11 AM ET on Feb 4th, the situation was fully resolved. We will dive deeper into the root causes and apply lessons learned to continue to improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 05:49 PM UTC
- Resolved
- Jan 14, 2026, 08:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 15, 2026, 05:49 PM UTC
This issue impacted the ability to update MFA settings when SMS was selected as an option. Additionally, the ability to create a new OvrC account was impacted. As of 1/14/2026 at 5pm the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 07:16 PM UTC
- Resolved
- Nov 18, 2025, 07:16 PM UTC
- Duration
- —
Timeline · 2 updates
-
monitoring Nov 18, 2025, 01:51 PM UTC
At approximately 6:50 AM ET, we began noticing some degraded services. After investigation, we determined that our service was experiencing issues due to the current problem with our 3rd-party WAF provider. By 8:00 AM ET, we have temporarily bypassed the affected service, and Intermittent OvrC and Control4 mobile issues are returning to normal. We will continue to monitor the situation and will provide more updates as we learn more. Thanks, Your ADI/Snap One Engineering team
-
resolved Nov 18, 2025, 07:16 PM UTC
As of 2:00 PM ET the situation was fully resolved. Initial impacts were caused by service failures from the third-party service provider and have now been resolved; we have reimplemented our cloud protections. Additional information on the outage is available here: status page Thank you for your patience and understanding. Your ADI/Snap One Engineering team
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 02:01 PM UTC
- Resolved
- Oct 20, 2025, 07:38 PM UTC
- Duration
- 5h 37m
Affected: 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 iOSService: OvrC LoginMobile App: Control4 OS 3.x iOSService: OvrC NotificationsService: OvrC Public APIsService: Control4 AlexaService: OvrC Web ConnectService: OvrC Speed TestService: Control4 Google AssistantService: Control4 Intercom Anywhere
Timeline · 6 updates
-
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
-
identified Oct 20, 2025, 02:11 PM UTC
We are seeing additional impacts across services due to our cloud service provider
-
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.
-
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.
-
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
-
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.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 11:18 AM UTC
- Resolved
- Oct 20, 2025, 11:18 AM UTC
- Duration
- —
Affected: Mobile App: Control4 Intercom Anywhere AndroidMobile App: Control4 Intercom Anywhere iOSService: OvrC NotificationsService: Control4 AlexaService: Control4 Google Assistant
Timeline · 1 update
-
resolved Oct 20, 2025, 11:18 AM UTC
As of 4:22am ET the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2025, 06:32 PM UTC
- Resolved
- Nov 18, 2025, 08:47 PM UTC
- Duration
- 43d 2h
Timeline · 2 updates
-
identified Oct 06, 2025, 06:32 PM UTC
We identified a bug in the Lutron LEAP protocol driver that, when used with OS 4.x systems, could cause integrations to go offline. This issue was fixed and a new driver was deployed last week. However, a subset of systems experienced forced dropouts after the update, which require re-pairing the Lutron bridge. We are working to identify and proactively notify all affected dealers. There are no ongoing dropout issues beyond this subset, and the fix fully resolves the problem for all systems upgrading from OS 3 to OS 4.x. We will update this post with additional details as we complete dealer notifications and continue improving our deployment and testing processes to prevent future occurrences.
-
resolved Nov 18, 2025, 08:47 PM UTC
The post-update forced-drops issue has been resolved. Thank you for your patience and understanding. Your ADI/Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2025, 08:10 PM UTC
- Resolved
- Oct 09, 2025, 03:18 PM UTC
- Duration
- 7d 19h
Affected: Service: Luma X10
Timeline · 2 updates
-
investigating Oct 01, 2025, 08:10 PM UTC
We're currently experiencing an issue with the Luma X10 Password tool. Our product team is actively investigating. In the meantime, password resets for both Luma X00 and Luma X10 devices are unavailable. We’ll provide updates as soon as possible.
-
resolved Oct 09, 2025, 03:18 PM UTC
As of today the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
Notice September 11, 2025 - Detected by Pingoru
- Sep 11, 2025, 07:58 PM UTC
- Resolved
- Sep 11, 2025, 08:06 PM UTC
- Duration
- 8m
Affected: Service: OvrC Device Communication & Configuration
Timeline · 2 updates
-
identified Sep 11, 2025, 07:58 PM UTC
We are aware of the impacts on OvrC Device Services and are actively engaged in determining the cause. More details will follow. Thanks, Your Snap One Engineering team
-
resolved Sep 11, 2025, 08:06 PM UTC
As of 4:00 PM EDT the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 01:37 PM UTC
- Resolved
- Aug 19, 2025, 03:31 PM UTC
- Duration
- 1h 53m
Affected: Service: Control4 Composer Pro
Timeline · 3 updates
-
identified Aug 19, 2025, 01:37 PM UTC
We are aware of the impacts on our Composer Pro remote system connections and are actively engaged in determining the cause. More details will follow. Thanks, Your Snap One Engineering team
-
monitoring Aug 19, 2025, 02:59 PM UTC
The fix has been applied and Composer Pro remote access is returning to normal with Partners able to use services. You may experience slight impacts to performance as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Aug 19, 2025, 03:31 PM UTC
As of 11:30am ET the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2025, 05:36 PM UTC
- Resolved
- Aug 05, 2025, 06:19 PM UTC
- Duration
- 43m
Affected: Mobile App: Control4 OS 3.x AndroidMobile App: Control4 OS 3.x iOSService: Control4 Access AnywhereService: Control4 Composer ProService: Control4 Intercom Anywhere
Timeline · 2 updates
-
monitoring Aug 05, 2025, 05:36 PM UTC
The fix has been applied to the Control4 cloud infrastructure that handles remote connections. Performance metrics are returning to normal with Partners and Customers able to use services. You may experience slight impacts to performance as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Aug 05, 2025, 06:19 PM UTC
As of 2pm ET the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2025, 03:13 PM UTC
- Resolved
- Jul 28, 2025, 05:10 PM UTC
- Duration
- 1h 57m
Affected: Website: dealer.control4.comWebsite: dealer-emea.control4.com
Timeline · 2 updates
-
identified Jul 28, 2025, 03:13 PM UTC
We've become aware that some customers are experiencing issues accessing the Knowledge Base, Tech Community, or Education pages. Our team is actively investigating the incident and will provide you with more details as they become available.
-
resolved Jul 28, 2025, 05:10 PM UTC
We have resolved the incident that prevented some users from accessing the Knowledge Base, Tech Community, or Education pages, and are continuing to monitor performance. We apologize for any inconvenience this may have caused you.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2025, 12:20 AM UTC
- Resolved
- Jul 15, 2025, 12:55 AM UTC
- Duration
- 34m
Affected: Service: Control4 Access AnywhereService: Control4 Intercom Anywhere
Timeline · 2 updates
-
identified Jul 15, 2025, 12:20 AM UTC
We have identified an issue with Control4 Cloud Services - we are aware and actively investigating solutions and impact. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Jul 15, 2025, 12:55 AM UTC
As of 8:50 pm ET the situation was fully resolved. We will dive deeper into root causes and continue to improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2025, 08:53 PM UTC
- Resolved
- Jul 11, 2025, 08:58 PM UTC
- Duration
- 1d
Affected: Mobile App: Luma View
Timeline · 3 updates
-
investigating Jul 10, 2025, 08:53 PM UTC
We are currently experiencing an issue with Luma View mobile app following today’s server update, which may affect its proper functioning for some users. Our team is actively investigating and working to resolve this as quickly as possible. We sincerely apologize for any inconvenience this may cause and appreciate your patience and understanding. We will provide an update as soon as the service is fully restored. Thanks, Your Snap One Engineering team
-
monitoring Jul 11, 2025, 07:17 PM UTC
The issue affecting Luma View has been resolved. Our team will continue to closely monitor the system to ensure everything remains stable. We appreciate your patience and understanding during this time. If you experience any further issues, please don’t hesitate to contact our support team. Thank you. Thanks, Your Snap One Engineering team
-
resolved Jul 11, 2025, 08:58 PM UTC
The issue with the Luma View application is fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 09:45 PM UTC
- Resolved
- Jun 27, 2025, 11:14 PM UTC
- Duration
- 1h 28m
Affected: Mobile App: Control4 Intercom Anywhere AndroidMobile App: Control4 Intercom Anywhere iOS
Timeline · 3 updates
-
investigating Jun 27, 2025, 09:45 PM UTC
We have identified an issue with Control4 Connect subscriptions we are aware and actively investigating solutions and impact. We have reported cases of the Control4 Connect subscriptions not processing through to completion in the Control4 mobile app. We are triaging the situation as quickly as possible. If you or your customer is running into this, please hold off on trying it multiple times. We will provide an update shortly. Thanks, Your Snap One Engineering team
-
monitoring Jun 27, 2025, 10:27 PM UTC
The fix has been applied to the Control4 Connect subscriptions, and we are monitoring as things stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Jun 27, 2025, 11:14 PM UTC
As of 07:10 pm ET, the situation was fully resolved, and all new purchase transactions are functioning as expected. We are working through the transactions that previously failed during this state. We will dive deeper into root causes and continue to improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2025, 06:22 PM UTC
- Resolved
- Jun 25, 2025, 11:57 PM UTC
- Duration
- 5h 35m
Affected: Service: OvrC Login
Timeline · 2 updates
-
identified Jun 25, 2025, 06:22 PM UTC
We are aware of the impacts on text message 2FA for OvrC and are actively engaged in determining the cause. More details will follow. Thanks, Your Snap One Engineering team
-
resolved Jun 25, 2025, 11:57 PM UTC
As of 7:50 PM ET, we consider the issue resolved. We will investigate the problem with our partner that led to this issue and continue to work to improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2025, 05:48 PM UTC
- Resolved
- Jun 05, 2025, 10:32 PM UTC
- Duration
- 1d 4h
Affected: Service: Control4 Composer Pro
Timeline · 5 updates
-
monitoring Jun 04, 2025, 05:48 PM UTC
Additional changes have been applied to stabilize services which support remote access in Composer Pro. You may experience slight impacts to performance as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
identified Jun 05, 2025, 02:10 PM UTC
We are aware of continued degraded performance and/or intermittent availability of remote configuration through Composer Pro. We are actively working towards a solution. More details will follow. Thanks, Your Snap One Engineering team
-
identified Jun 05, 2025, 05:48 PM UTC
We want to apologize for the disruption this issue is causing. We know how critical Composer Pro, Intercom Anywhere, and other Control4 services are to your business and your customers — and we take that responsibility seriously. Restoring full functionality is our absolute top priority. Our engineering team is working around the clock and has already made significant progress. We will continue to provide regular updates until all issues are fully resolved. Thank you again for your patience and understanding.
-
monitoring Jun 05, 2025, 09:58 PM UTC
The fix has been applied and remote connections are returning to normal. You may experience slight impacts to performance as systems fully ramp up and stabilize - however we are already seeing significant improvement and more consistency in performance metrics. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Jun 05, 2025, 10:32 PM UTC
As of 6:30PM ET the situation was fully resolved. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- May 20, 2025, 10:32 PM UTC
- Resolved
- May 21, 2025, 01:58 AM UTC
- Duration
- 3h 25m
Affected: Mobile App: OvrCMobile App: OvrC ConnectMobile App: Luma X10Service: OvrC Device Communication & ConfigurationService: OvrC Firmware UpdatesService: OvrC LoginService: OvrC NotificationsService: OvrC Public APIsService: OvrC Web ConnectService: OvrC Speed Test
Timeline · 6 updates
-
identified May 20, 2025, 01:04 PM UTC
OvrC is in an extended maintenance window and users may experience some degradation during this period. We are working diligently to complete this process and return OvrC to full operation. We will update once this is completed. Thanks, Your Snap One Engineering team
-
identified May 20, 2025, 04:27 PM UTC
We are continuing to work on a fix for this issue.
-
identified May 20, 2025, 10:32 PM UTC
While most services have been restored, we will revert some of our previous changes at 6:00 p.m. Pacific Time tonight to ensure the continued performance and reliability of our platform. We will update the status as we progress. Thanks, Your Snap One Engineering team
-
identified May 20, 2025, 10:41 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring May 20, 2025, 10:52 PM UTC
The maintenance in OvrC was completed shortly before 5pm ET. Since then, performance has stabilized, but we will continue to monitor the situation closely. We have a final round of maintenance planned for 9pm ET which will further stabilize affected services. During that time, you may experience slight impacts to performance as systems fully ramp up. More details to follow. Thanks, Your Snap One Engineering team
-
resolved May 21, 2025, 01:58 AM UTC
As of 10pm ET, our follow-up maintenance was completed. We will dive deeper into root causes of the performance issues from the earlier maintenance window and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 10:53 PM UTC
- Resolved
- Apr 24, 2025, 02:27 AM UTC
- Duration
- 3h 33m
Affected: Service: OvrC Notifications
Timeline · 3 updates
-
identified Apr 23, 2025, 10:53 PM UTC
We are currently experiencing an issue with our third-party service provider responsible for OvrC email delivery. You may notice intermittent deliveries while they continue to work to resolve the issue. We will continue to monitor the situation, more details will follow. Thanks, Your Snap One Engineering team
-
monitoring Apr 24, 2025, 01:30 AM UTC
Update - Our third-party provider has provided the following update: "We have mitigated the issues affecting email sending and have also re-enabled our Bounce Suppressions list. Email traffic is now working 100% with all checks." Emails should be flowing normally. We will continue to monitor the situation until the vendor closes the incident. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Apr 24, 2025, 02:27 AM UTC
As of 10:20 PM ET, we consider the issue resolved. We will investigate the problem with our partner that led to this issue and continue to work to improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2025, 09:30 AM UTC
- Resolved
- Apr 15, 2025, 01:29 PM UTC
- Duration
- 3h 58m
Affected: Service: Control4 Updates
Timeline · 3 updates
-
identified Apr 15, 2025, 09:30 AM UTC
We are aware of the impacts on Control4 update service and are actively engaged in determining the cause. More details will follow. Thanks, Your Snap One Engineering team
-
monitoring Apr 15, 2025, 10:19 AM UTC
The update service has stabilized and has returned to normal, you may experience slight impacts to performance as systems fully ramp up and stabilize. More details to follow. Thanks, Your Snap One Engineering team
-
resolved Apr 15, 2025, 01:29 PM UTC
As of 6:15 a.m. EDT, the situation was fully resolved. We will continue to investigate the root causes and focus on improving our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2025, 07:26 PM UTC
- Resolved
- Apr 16, 2025, 03:42 PM UTC
- Duration
- 7d 20h
Affected: Mobile App: Luma View
Timeline · 3 updates
-
investigating Apr 08, 2025, 07:26 PM UTC
We are actively investigating the root cause of an issue affecting some users who are not receiving push notifications on iOS devices when using Luma View Mobile APP. In the meantime, we do have a workaround available. If you or your customers encounter this issue, please contact our technical support team for assistance and instructions on how to resolve it. Thank you for your patience and sorry for the inconvenience, Your Snap One Engineering team
-
identified Apr 11, 2025, 09:58 PM UTC
After further investigation, we’ve identified that this issue was caused by an abnormal token being loaded in the iOS app during a server update. This only impacts users who closed the app in the background between March 31st at 5:51 AM and April 3rd at 12:30 AM (Eastern Time). “Closing the app in the background” includes: * Restarting the iOS device * Performing an iOS update * Force closing the Luma View app via the swipe-up gesture * New installation of Luma View app Please note: If the app remained in deep sleep during that time, it will not be affected. We’re actively working on a new version of the app to fully address this issue. However, if you or your customers need an immediate fix, please reach out to our tech support. We apologize for the inconvenience and thank you for your patience and understanding.
-
resolved Apr 16, 2025, 03:42 PM UTC
As of April 3rd at 12:30 AM (Eastern Time), the root issue was resolved. No further users will be impacted. If you're experiencing residual effects of the issue, please reach out to Tech Support for resolution. Additionally, we’re actively working on a new version of the app to fully address this issue for impacted users. We will dive deeper into root causes and provide you with details on how we will improve our services. Thank you for your patience and understanding. Your Snap One Engineering team
Read the full incident report →
