Voyado Status

Resolved: Microsoft has declared their incident resolved, so we do the same.

Microsoft's summary of Impact: Between 08:51 and 10:15 UTC on 01 April 2025, we identified customer impact resulting from a power event in the North Europe region which impacted Virtual Machines, Storage, CosmosDB, PostgreSQL, Azure ExpressRoute and Azure NetApp Files. We can confirm that all affected services have now recovered. A power maintenance event led to temporary power loss in a single datacenter, in Physical Availability Zone 2, in the North Europe region affecting multiple racks and devices. The power has been fully restored and services are seeing full recovery.

Monitoring: Microsoft have extended their incident as it is affecting more resources and we are continuing to monitor the situation. Our monitoring platform currently indicates a fairly normal level of operations, but we do see intermittent failures on a per call basis, but for a very low percentage of calls. So there is some impact, ranging from slow responses to failures to perform certain actions. As Microsoft have extended the incident to include connectivity towards various forms of storage we expect to see failures reading from product feeds, and similar, possibly halting certain, but not all, messages.

Investigating: We have received reports on an ongoing incident in Microsoft Azure that may result in degraded performance for Engage. The incident has not yet been published on Azure status pages so we don't have full visibility as of right now.

At the moment we are assessing the situation through our monitoring platform to understand if and how we are impacted. We will be doing what we can to counter any effects.

Resolved: Microsoft has declared their incident resolved, so we do the same.

Microsoft's summary of Impact: Between 08:51 and 10:15 UTC on 01 April 2025, we identified customer impact resulting from a power event in the North Europe region which impacted Virtual Machines, Storage, CosmosDB, PostgreSQL, Azure ExpressRoute and Azure NetApp Files. We can confirm that all affected services have now recovered. A power maintenance event led to temporary power loss in a single datacenter, in Physical Availability Zone 2, in the North Europe region affecting multiple racks and devices. The power has been fully restored and services are seeing full recovery.

Monitoring: Microsoft have extended their incident as it is affecting more resources and we are continuing to monitor the situation. Our monitoring platform currently indicates a fairly normal level of operations, but we do see intermittent failures on a per call basis, but for a very low percentage of calls. So there is some impact, ranging from slow responses to failures to perform certain actions. As Microsoft have extended the incident to include connectivity towards various forms of storage we expect to see failures reading from product feeds, and similar, possibly halting certain, but not all, messages.

Investigating: We have received reports on an ongoing incident in Microsoft Azure that may result in degraded performance for Engage. The incident has not yet been published on Azure status pages so we don't have full visibility as of right now.

At the moment we are assessing the situation through our monitoring platform to understand if and how we are impacted. We will be doing what we can to counter any effects.

Resolved: Microsoft has declared their incident resolved, so we do the same.

Microsoft's summary of Impact: Between 08:51 and 10:15 UTC on 01 April 2025, we identified customer impact resulting from a power event in the North Europe region which impacted Virtual Machines, Storage, CosmosDB, PostgreSQL, Azure ExpressRoute and Azure NetApp Files. We can confirm that all affected services have now recovered. A power maintenance event led to temporary power loss in a single datacenter, in Physical Availability Zone 2, in the North Europe region affecting multiple racks and devices. The power has been fully restored and services are seeing full recovery.

Monitoring: Microsoft have extended their incident as it is affecting more resources and we are continuing to monitor the situation. Our monitoring platform currently indicates a fairly normal level of operations, but we do see intermittent failures on a per call basis, but for a very low percentage of calls. So there is some impact, ranging from slow responses to failures to perform certain actions. As Microsoft have extended the incident to include connectivity towards various forms of storage we expect to see failures reading from product feeds, and similar, possibly halting certain, but not all, messages.

Investigating: We have received reports on an ongoing incident in Microsoft Azure that may result in degraded performance for Engage. The incident has not yet been published on Azure status pages so we don't have full visibility as of right now.

At the moment we are assessing the situation through our monitoring platform to understand if and how we are impacted. We will be doing what we can to counter any effects.

Resolved: Microsoft has declared their incident resolved, so we do the same.

Microsoft's summary of Impact: Between 08:51 and 10:15 UTC on 01 April 2025, we identified customer impact resulting from a power event in the North Europe region which impacted Virtual Machines, Storage, CosmosDB, PostgreSQL, Azure ExpressRoute and Azure NetApp Files. We can confirm that all affected services have now recovered. A power maintenance event led to temporary power loss in a single datacenter, in Physical Availability Zone 2, in the North Europe region affecting multiple racks and devices. The power has been fully restored and services are seeing full recovery.

Monitoring: Microsoft have extended their incident as it is affecting more resources and we are continuing to monitor the situation. Our monitoring platform currently indicates a fairly normal level of operations, but we do see intermittent failures on a per call basis, but for a very low percentage of calls. So there is some impact, ranging from slow responses to failures to perform certain actions. As Microsoft have extended the incident to include connectivity towards various forms of storage we expect to see failures reading from product feeds, and similar, possibly halting certain, but not all, messages.

Investigating: We have received reports on an ongoing incident in Microsoft Azure that may result in degraded performance for Engage. The incident has not yet been published on Azure status pages so we don't have full visibility as of right now.

At the moment we are assessing the situation through our monitoring platform to understand if and how we are impacted. We will be doing what we can to counter any effects.

Resolved: Microsoft has declared their incident resolved, so we do the same.

Microsoft's summary of Impact: Between 08:51 and 10:15 UTC on 01 April 2025, we identified customer impact resulting from a power event in the North Europe region which impacted Virtual Machines, Storage, CosmosDB, PostgreSQL, Azure ExpressRoute and Azure NetApp Files. We can confirm that all affected services have now recovered. A power maintenance event led to temporary power loss in a single datacenter, in Physical Availability Zone 2, in the North Europe region affecting multiple racks and devices. The power has been fully restored and services are seeing full recovery.

Monitoring: Microsoft have extended their incident as it is affecting more resources and we are continuing to monitor the situation. Our monitoring platform currently indicates a fairly normal level of operations, but we do see intermittent failures on a per call basis, but for a very low percentage of calls. So there is some impact, ranging from slow responses to failures to perform certain actions. As Microsoft have extended the incident to include connectivity towards various forms of storage we expect to see failures reading from product feeds, and similar, possibly halting certain, but not all, messages.

Investigating: We have received reports on an ongoing incident in Microsoft Azure that may result in degraded performance for Engage. The incident has not yet been published on Azure status pages so we don't have full visibility as of right now.

At the moment we are assessing the situation through our monitoring platform to understand if and how we are impacted. We will be doing what we can to counter any effects.

Resolved: Microsoft has declared their incident resolved, so we do the same.

Microsoft's summary of Impact: Between 08:51 and 10:15 UTC on 01 April 2025, we identified customer impact resulting from a power event in the North Europe region which impacted Virtual Machines, Storage, CosmosDB, PostgreSQL, Azure ExpressRoute and Azure NetApp Files. We can confirm that all affected services have now recovered. A power maintenance event led to temporary power loss in a single datacenter, in Physical Availability Zone 2, in the North Europe region affecting multiple racks and devices. The power has been fully restored and services are seeing full recovery.

Monitoring: Microsoft have extended their incident as it is affecting more resources and we are continuing to monitor the situation. Our monitoring platform currently indicates a fairly normal level of operations, but we do see intermittent failures on a per call basis, but for a very low percentage of calls. So there is some impact, ranging from slow responses to failures to perform certain actions. As Microsoft have extended the incident to include connectivity towards various forms of storage we expect to see failures reading from product feeds, and similar, possibly halting certain, but not all, messages.

Investigating: We have received reports on an ongoing incident in Microsoft Azure that may result in degraded performance for Engage. The incident has not yet been published on Azure status pages so we don't have full visibility as of right now.

At the moment we are assessing the situation through our monitoring platform to understand if and how we are impacted. We will be doing what we can to counter any effects.

Resolved: Microsoft has declared their incident resolved, so we do the same.

Microsoft's summary of Impact: Between 08:51 and 10:15 UTC on 01 April 2025, we identified customer impact resulting from a power event in the North Europe region which impacted Virtual Machines, Storage, CosmosDB, PostgreSQL, Azure ExpressRoute and Azure NetApp Files. We can confirm that all affected services have now recovered. A power maintenance event led to temporary power loss in a single datacenter, in Physical Availability Zone 2, in the North Europe region affecting multiple racks and devices. The power has been fully restored and services are seeing full recovery.

Monitoring: Microsoft have extended their incident as it is affecting more resources and we are continuing to monitor the situation. Our monitoring platform currently indicates a fairly normal level of operations, but we do see intermittent failures on a per call basis, but for a very low percentage of calls. So there is some impact, ranging from slow responses to failures to perform certain actions. As Microsoft have extended the incident to include connectivity towards various forms of storage we expect to see failures reading from product feeds, and similar, possibly halting certain, but not all, messages.

Investigating: We have received reports on an ongoing incident in Microsoft Azure that may result in degraded performance for Engage. The incident has not yet been published on Azure status pages so we don't have full visibility as of right now.

At the moment we are assessing the situation through our monitoring platform to understand if and how we are impacted. We will be doing what we can to counter any effects.