Arlo Outage History

Started Oct 16, 2026, 08:05 PM UTC· resolved Oct 17, 2026, 01:40 PM UTC

1. investigating Oct 16, 2026, 08:05 PM UTC

   We're aware of an ongoing issue where some users are only receiving motion notifications instead of smart notifications. Our team is actively investigating the root cause. We apologize for any inconvenience and appreciate your patience.

2. resolved Oct 17, 2026, 01:40 PM UTC

   This incident has been resolved

Read the full incident report →

Started Oct 06, 2026, 04:48 PM UTC· resolved Oct 06, 2026, 08:22 PM UTC

1. investigating Oct 06, 2026, 04:48 PM UTC

   We are experiencing an authentication service disruption due to a third-party Identity outage, affecting new logins and authentication from untrusted devices/browsers. Users already authenticated are not affected, and our team is actively investigating and working to restore full service as quickly as possible.

2. monitoring Oct 06, 2026, 05:14 PM UTC

   We are closely monitoring the fix deployed and actively working on the mitigation of the issue.

3. resolved Oct 06, 2026, 08:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 07, 2026, 01:31 AM UTC· resolved Jun 10, 2026, 10:45 PM UTC

1. investigating Jun 07, 2026, 01:31 AM UTC

   The Arlo team is aware of an issue causing the iOS app to crash on launch for some users with the recent version 6.30.0. This appears to primarily affect older iPhone models, including iPhone 8 and iPhone 11. We apologize for the inconvenience and are actively working on a fix.

2. monitoring Jun 08, 2026, 10:25 PM UTC

   We are currently deploying a fix through a slow rollout. Please update to the latest iOS app version 6.31.0. We are monitoring the results.

3. resolved Jun 10, 2026, 10:45 PM UTC

   The issue has been resolved. Please upgrade to the latest available iOS app version.

Read the full incident report →

Started May 26, 2026, 09:17 PM UTC· resolved May 28, 2026, 05:10 AM UTC

1. investigating May 26, 2026, 09:17 PM UTC

   We are aware of an issue affecting geofencing functionality for some customers on iOS app. Our team is actively investigating and working toward a resolution. We will provide updates as they become available. We apologize for the inconvenience !

2. identified May 27, 2026, 01:23 AM UTC

   We've identified the cause of the problem preventing iOS users from using geofencing. The Arlo DevOps team is working to implement a solution for the issue.

3. monitoring May 27, 2026, 07:27 PM UTC

   We are currently deploying a fix through a slow rollout. Please update to latest iOS app 6.29.1 version. We are monitoring the results.

4. resolved May 28, 2026, 05:10 AM UTC

   Geofencing issue has been resolved. Please upgrade to latest available iOS app version.

Read the full incident report →

Started Apr 20, 2026, 06:00 PM UTC· resolved Apr 21, 2026, 04:53 PM UTC

1. investigating Apr 20, 2026, 06:00 PM UTC

   We are currently investigating an issue that prevents community users from logging in to the Arlo community. This does not impact log in to your Arlo account at my.arlo.com or the Arlo website at arlo.com. We apologize for the inconvenience and will provide updates as soon as have more information to share.

2. resolved Apr 21, 2026, 04:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 22, 2026, 04:00 PM UTC· resolved Mar 22, 2026, 04:00 PM UTC

1. resolved Mar 22, 2026, 04:00 PM UTC

   Beginning Saturday, some US and Canadian customers experienced issues with camera connectivity, onboarding, and motion recording. Our engineering team has already deployed a fix, service is now being restored. If your cameras are back online, no action is needed. If you are still not seeing recordings, a factory reset of your device may be required to restore service. To reset your Arlo camera, press and hold the physical sync button on the device for approximately 15 seconds until the LED flashes amber. How to reset your Arlo camera -> [How to factory reset Arlo devices](https://kb.arlo.com/000062659/How-to-factory-reset-Arlo-devices) Please be aware that our contact center is experiencing longer than usual wait times. We strongly encourage using the self-help link above as the fastest way to get back online. If you still need assistance after following the reset steps, visit [Arlo Community](https://community.arlo.com/) or contact support at [Contact Us](https://us.arlo.com/pages/contact-us)

Read the full incident report →

Started Mar 21, 2026, 04:40 PM UTC· resolved Mar 22, 2026, 07:47 PM UTC

1. investigating Mar 21, 2026, 04:40 PM UTC

   We are aware that some customers are currently experiencing issues with camera devices appearing offline and encountering onboarding failures. We sincerely apologize for the disruption and appreciate your patience while we work to resolve this as quickly as possible.

2. resolved Mar 21, 2026, 05:24 PM UTC

   This incident has been fully resolved. Impact was limited to users in the US region only.

3. resolved Mar 22, 2026, 07:47 PM UTC

   Beginning Saturday, some Arlo customers and devices experienced issues with camera connectivity, onboarding, and motion recording. Our engineering team has deployed a fix—service is now being restored. If your cameras are back online, no action is needed. If you are still not seeing recordings, a factory reset of your device may be required to restore service. To reset your Arlo camera, press and hold the physical sync button on the device for approximately 15 seconds until the LED flashes amber. How to reset your Arlo camera [How to factory reset Arlo devices](https://kb.arlo.com/000062659/How-to-factory-reset-Arlo-devices) Please be aware that our contact center is experiencing longer than usual wait times. We strongly encourage using the self-help link above as the fastest way to get back online. If you still need assistance after following the reset steps, visit [Arlo Community](https://community.arlo.com/) or contact support at [Contact Us](https://us.arlo.com/pages/contact-us)

Read the full incident report →

Started Mar 11, 2026, 04:20 PM UTC· resolved Mar 13, 2026, 07:09 PM UTC

1. investigating Mar 11, 2026, 04:20 PM UTC

   The Arlo team is investigating an issue where a few customers using the latest Arlo iOS app (version 6.18.0) may experience problems using the app. We are working on resolving this issue and apologize for the inconvenience.

2. monitoring Mar 11, 2026, 05:32 PM UTC

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

3. resolved Mar 13, 2026, 07:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 04, 2026, 12:42 AM UTC· resolved Mar 04, 2026, 02:09 AM UTC

1. investigating Mar 04, 2026, 12:42 AM UTC

   We are aware that some Arlo customers are experiencing intermittent connectivity issues. Our team is actively investigating and will share updates as they become available.

2. resolved Mar 04, 2026, 02:09 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 08, 2025, 09:10 PM UTC· resolved Nov 08, 2025, 11:11 PM UTC

1. investigating Nov 08, 2025, 09:10 PM UTC

   Arlo team is investigating an issue where customers would be experiencing motion recordings and live streaming not working intermittently. We apologize for this inconvenience we are working on resolving this issue.

2. monitoring Nov 08, 2025, 10:04 PM UTC

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

3. resolved Nov 08, 2025, 11:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 30, 2025, 03:46 AM UTC· resolved Oct 30, 2025, 04:05 AM UTC

1. investigating Oct 30, 2025, 03:46 AM UTC

   Arlo team is actively investigating an issue where customers in the APAC region are unable to use livestreaming and motion recording features. We apologize for the disruption and inconvenience this is causing. Our team is working to resolve the issue as quickly as possible.

2. resolved Oct 30, 2025, 04:05 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 30, 2025, 11:53 AM UTC· resolved Oct 30, 2025, 04:04 AM UTC

1. investigating Aug 30, 2025, 11:53 AM UTC

   The Arlo DevOps team is investigating an issue where Arlo Europe customers are experiencing a gap in timelines for continuous video recordings. We apologize for this inconvenience and are working to resolve the issue.

2. monitoring Aug 30, 2025, 05:14 PM UTC

   The issue has been resolved and we are monitoring the system.

3. resolved Aug 30, 2025, 06:27 PM UTC

   This incident has been resolved.

4. resolved Oct 30, 2025, 04:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 10, 2025, 06:06 PM UTC· resolved Jun 12, 2025, 02:03 PM UTC

1. investigating Jun 10, 2025, 06:06 PM UTC

   We have identified an issue with our Android application, where users with the GeoFencing/Arrive & Leave feature enabled are facing issues changing the modes. Our team is actively investigating the root cause. We apologize for any inconvenience and appreciate your patience

2. monitoring Jun 11, 2025, 07:19 AM UTC

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

3. resolved Jun 12, 2025, 02:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 16, 2025, 11:15 AM UTC· resolved May 16, 2025, 02:30 PM UTC

1. investigating May 16, 2025, 11:15 AM UTC

   We're currently investigating an ongoing issue where users in Europe are receiving motion notifications only, instead of the expected smart notifications. Our team is actively working to identify and resolve the root cause. We apologize for the inconvenience and appreciate your patience as we work to restore full functionality.

2. monitoring May 16, 2025, 01:39 PM UTC

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

3. resolved May 16, 2025, 02:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2025, 06:43 AM UTC· resolved May 07, 2025, 10:32 AM UTC

1. investigating May 07, 2025, 06:43 AM UTC

   Arlo DevOps team is investigating an issue where customers are not able to log in through Web Browsers and Mobile Apps. We are working on resolving this issue. We apologize for the inconvenience!

2. identified May 07, 2025, 09:27 AM UTC

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

3. monitoring May 07, 2025, 09:38 AM UTC

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

4. resolved May 07, 2025, 10:32 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 28, 2025, 07:47 AM UTC· resolved Apr 28, 2025, 09:51 AM UTC

1. investigating Apr 28, 2025, 07:47 AM UTC

   We're aware of an ongoing issue where users are only receiving motion notifications instead of smart notifications. Our team is actively investigating the root cause. We apologize for any inconvenience and appreciate your patience.

2. monitoring Apr 28, 2025, 09:48 AM UTC

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

3. resolved Apr 28, 2025, 09:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 23, 2025, 05:44 PM UTC· resolved Apr 23, 2025, 06:27 PM UTC

1. investigating Apr 23, 2025, 05:44 PM UTC

   The Arlo team is investigating an issue where some US & Canada customers are experiencing motion recordings missing in the library. We apologize for the inconvenience. We are working on resolving this issue.

2. monitoring Apr 23, 2025, 06:08 PM UTC

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

3. resolved Apr 23, 2025, 06:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 23, 2025, 04:15 AM UTC· resolved Apr 23, 2025, 06:26 PM UTC

1. investigating Apr 23, 2025, 04:15 AM UTC

   Arlo team is investigating an issue affecting some customers in the APAC region would be experiencing issue with motion recordings, Live streaming and Notifications may be significantly delayed, or may not arrive at all. We apologize for this inconvenience. The teams are working on resolving this issue at the earliest.

2. resolved Apr 23, 2025, 09:54 AM UTC

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

3. resolved Apr 23, 2025, 06:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 17, 2025, 12:45 PM UTC· resolved Apr 23, 2025, 04:13 PM UTC

1. investigating Apr 17, 2025, 12:45 PM UTC

   The Arlo DevOps team is investigating an issue where Arlo North America & Europe customers are experiencing a gap in timelines for continuous video recordings. We apologize for this inconvenience and are working to resolve the issue.

2. resolved Apr 17, 2025, 01:54 PM UTC

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

3. resolved Apr 23, 2025, 04:13 PM UTC

   After reviewing the incident, we would like to confirm that this only impacted CVR timelines for users in the Europe region and had no impact on users in the North America region.

Read the full incident report →

Started Apr 11, 2025, 07:50 PM UTC· resolved Apr 11, 2025, 09:31 PM UTC

1. investigating Apr 11, 2025, 07:50 PM UTC

   We are aware of an ongoing issue where some users are receiving only motion notifications instead of notifications for Person Recognition and Vehicle Recognition. Our team is actively investigating the root cause. We apologize for any inconvenience and appreciate your patience.

2. monitoring Apr 11, 2025, 09:06 PM UTC

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

3. resolved Apr 11, 2025, 09:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 12, 2025, 05:36 PM UTC· resolved Mar 12, 2025, 06:32 PM UTC

1. investigating Mar 12, 2025, 05:36 PM UTC

   Arlo DevOps team is investigating an issue where customers would be experiencing devices appear offline in all 3 clients. We apologize for this inconvenience we are working on resolving this issue.

2. monitoring Mar 12, 2025, 06:17 PM UTC

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

3. resolved Mar 12, 2025, 06:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 21, 2025, 09:24 PM UTC· resolved Feb 24, 2025, 08:47 AM UTC

1. investigating Feb 21, 2025, 09:24 PM UTC

   We are aware of an issue affecting Android app users on the latest version, 5.5.2_28806 (released on Feb 14th). Impacted users may be unable to access feeds. Our team is actively investigating the issue, and we will provide updates as we have more information

2. resolved Feb 24, 2025, 08:47 AM UTC

   A fix has been successfully implemented in the 5.5.3_28810 version and is available on the Play Store. Thank you for your understanding. We strongly encourage you to update to the latest version.

Read the full incident report →

Started Feb 18, 2025, 09:51 PM UTC· resolved Feb 20, 2025, 04:28 PM UTC

1. investigating Feb 18, 2025, 09:51 PM UTC

   We're aware of an ongoing issue where some users are intermittently receiving motion notifications instead of smart notifications for the US region. Our team is actively investigating the root cause. We apologize for any inconvenience and appreciate your patience.

2. resolved Feb 20, 2025, 04:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 22, 2025, 06:14 AM UTC· resolved Jan 22, 2025, 06:59 AM UTC

1. investigating Jan 22, 2025, 06:14 AM UTC

   Arlo team is investigating an issue where customers would be experiencing motion recordings missing in the library. We apologize for this inconvenience we are working on resolving this issue.

2. monitoring Jan 22, 2025, 06:32 AM UTC

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

3. resolved Jan 22, 2025, 06:59 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 09, 2025, 01:14 AM UTC· resolved Jan 09, 2025, 02:50 AM UTC

1. investigating Jan 09, 2025, 01:14 AM UTC

   We are currently investigating an issue that is causing intermittent failures when purchasing new plans on our platform. We apologize for the inconvenience.

2. monitoring Jan 09, 2025, 02:19 AM UTC

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

3. resolved Jan 09, 2025, 02:50 AM UTC

   This incident has been resolved.

Read the full incident report →