Resolved -
The underlying issue has been remediated, and monitoring confirms no continuing impact. The incident is now resolved
Dec 12, 15:04 UTC
Update -
Ongoing efforts are focused on completing the remaining remediation steps
Dec 11, 07:16 UTC
Update -
Efforts to complete remediation are continuing
Dec 9, 20:00 UTC
Update -
Remediation work is still in progress
Dec 8, 16:43 UTC
Update -
Remediation efforts are still in progress, and previously affected accounts continue to be reviewed to ensure the appropriate corrective actions are applied. Further updates will be shared as the work advances
Dec 5, 15:08 UTC
Monitoring -
The root cause of the issue has been identified and removed. As a result, customer accounts are no longer at risk of further impact. The accounts that were previously affected are currently being reviewed individually to determine the best remediation approach. Additional updates will be provided as remediation progresses
Dec 4, 21:23 UTC
Identified -
We've detected a discrepancy in the size of snapshots completed during the last 24 hours. We've identified the underlying issues, and are currently mitigating the problem. We expect the issue to be resolved by 19:00 UTC on 04 December 2025
Dec 4, 11:46 UTC