CloudieConnect Servers Failing to Register

Update timeline

1. investigating Jun 03, 2026, 01:16 PM UTC

   **What Occurred:** At approximately 8:30 AM, June 3, 2026, we became aware that the IPs associated with the CloudieConnect services became unassociated with the registration servers. **What is Affected:** CloudieConnect desktop and mobile apps are unable to register for both branded and unbranded apps. **When It began:** June 3rd, 2026, at 8:30 AM ET **Current Status**: We are working to reassociate the affected IPs as quickly as possible. **Next Steps**: Clients may use SNAPmobile or SNAPmobile Web as a temporary workaround until the problem is resolved. * * **Next Update**: June 3rd, 2026, at 10:30 AM ET.

2. resolved Jun 03, 2026, 02:20 PM UTC

   **What was Affected:** CloudieConnect desktop and mobile apps were unable to register for both branded and unbranded apps. **When It began:** June 3rd, 2026, at 8:30 AM ET **Current Status**: At this time, the IP addresses have been successfully reassociated, and we have confirmed both the mobile and desktop apps are working as expected. **Next Steps**: * If CloudieConnect continues to show unregistered, or if users are unable to answer calls or experience one-way/no audio, please log out and log back in. If the issue persists after logging back in, please submit a support ticket so our team may assist further. * We will continue monitoring for the next 24 hours. * A Major Incident Report (MIR) will be issued within 48 business hours. **Next Update:** June 4th, 2026, at 10:00 AM ET.

3. resolved Jun 04, 2026, 06:26 PM UTC

   **What Occurred:** At approximately **8:30 AM ET on June 3, 2025**, we became aware that the IPs associated with the CloudieConnect services became unassociated with the registration servers. **What Was Affected:** CloudieConnect desktop and mobile apps were unable to register for both branded and unbranded apps. **When It began:** June 3rd, 2026, at 8:30 AM ET **Current Status:** Following 24 hours of monitoring, the issue has been fully resolved with no further concerns identified. A Major Incident Report (MIR) will be issued within 24 business hours..

4. monitoring Jun 05, 2026, 03:38 PM UTC

   This incident is considered resolved, and the Major Incident Report (MIR) is now available. * **Major Incident Report (MIR):** .