Resolved -
The resolution with devices with orphaned IPs on Cluster US4 has been completed. The source of the disruption has been resolved, and services have been fully restored.
A Root Cause Analysis (RCA) will follow after a full review has been completed.
Dec 7, 04:41 EST
Update -
We’ve identified the source of the service disruption with devices with orphaned IPs on Cluster US4 and continue to monitor the situation. There will continue to be a delay for data to catch up in the UI. The lag catch-up has proceeded more slowly than anticipated. The new estimated time for the lag to become current is now at some point early in the morning December 7th EST. We apologize for this delay. We’ll keep you posted on a resolution.
Dec 6, 17:00 EST
Update -
We’ve identified the source of the service disruption with devices with orphaned IPs on Cluster US4 and continue to monitor the situation. There will continue to be a delay for data to catch up in the UI. The estimated time for the lag to become current is 23:00 UTC or 6:00 PM EST. We’ll keep you posted on a resolution.
Dec 6, 13:41 EST
Monitoring -
We’ve identified the source of the service disruption with devices with orphaned IPs on Cluster US4 and are monitoring the situation. There will continue to be a delay for data to catch up in the UI. We’ll keep you posted on a resolution.
Dec 6, 13:21 EST
Identified -
We’ve identified the source of the service disruption with devices with orphaned IPs on Cluster US4. We are working to restore service as quickly as possible.
Dec 6, 12:32 EST
Investigating -
We’re experiencing disruption with devices with orphaned IPs on Cluster US4. We will continue to provide updates as they become available.
Dec 6, 11:54 EST