Get email notifications whenever Copaco Cloud - Statuspage creates, updates or resolves an incident.
Get text message notifications whenever Copaco Cloud - Statuspage creates or resolves an incident.
Get webhook notifications whenever Copaco Cloud - Statuspage creates an incident, updates an incident, resolves an incident or changes a component status.
All affected VMs have been recovered. Please verify that your VMs are running correctly.
Posted Nov 16, 2024 - 10:13 CET
Monitoring
The underlying issue has been resolved, and we are now in the process of bringing up the VMs
Posted Nov 16, 2024 - 08:41 CET
Update
We have identified the problem and are actively working with Broadcom support to resolve it. Broadcom is also investigating the incident and exploring potential solutions.
Posted Nov 16, 2024 - 04:24 CET
Update
As a precaution, we have postponed backup jobs and limited actions in the environment to assist Broadcom in narrowing down the issue. A small number of VMs are significantly impacted, but we are currently unable to implement corrective actions. We will provide an update as soon as we have more information.
Posted Nov 16, 2024 - 01:19 CET
Update
Broadcom is investigating the incident.
Posted Nov 16, 2024 - 00:06 CET
Update
A P1 ticket has also been raised with Broadcom.
Posted Nov 15, 2024 - 22:56 CET
Investigating
At this moment we have a degraded VMware environment in AMS1
We are investigating the issue and will post regular updates.
We appreciate your patience and understanding. If you have any questions or concerns, please send to the Cloud Support team at support@copaco.cloud
Posted Nov 15, 2024 - 22:15 CET
This incident affected: Copaco VMware Cloud (AMS1 - vmware clusters).