Umbrellar Outage History

Umbrellar is up right now

Pingoru has recorded 1 incident for Umbrellar: 1 in the last 12 months and 0 in the last 90 days.

Source: status.umbrellar.com

1incidents recorded
1last 12 months
0last 90 days
9 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Umbrellar in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 518 (0%)

Incidents, newest first

Critical October 29, 2025 Azure Front Door - Connectivity issues 8h 42m Australia East, Australia Southeast

Started Oct 29, 2025, 04:00 PM UTC· resolved Oct 30, 2025, 12:43 AM UTC

  1. identified Oct 29, 2025, 06:19 PM UTC

    We want to inform you that we are currently aware of an issue affecting Azure Front Door, which may be impacting your service availability or performance. Microsoft has acknowledged the incident and is actively working on a resolution. You can follow their updates directly via https://azure.status.microsoft/en-us/status. We are closely monitoring the situation and will keep you informed as we learn more. Your experience is important to us, and we appreciate your patience and understanding.

  2. identified Oct 29, 2025, 07:39 PM UTC

    At this stage, Microsoft anticipate full mitigation within the next four hours as they continue to recover nodes. This means we expect recovery to happen by 12:20PM on 30 October 2025. We will provide another update on our progress within two hours, or sooner if warranted

  3. identified Oct 29, 2025, 11:25 PM UTC

    Microsoft has deployed its last known good configuration and recovery is progressing. They are actively restoring nodes and rerouting traffic through healthy systems. While improvements are being seen, some requests may still hit unhealthy nodes, causing intermittent failures or reduced availability. The recovery process involves reloading configurations and rebalancing traffic across a large fleet. This is being done gradually to maintain stability and avoid overload as dependent services come back online. Microsoft expects full mitigation by 12:40PM NZDT on 30 October 2025, and will communicate if recovery completes sooner. Customer configuration changes remain temporarily blocked by Microsoft to prevent interference with recovery efforts. They will notify when this restriction is lifted.

  4. identified Oct 29, 2025, 11:30 PM UTC

    We are continuing to work on a fix for this issue.

  5. resolved Oct 30, 2025, 12:43 AM UTC

    We’re pleased to confirm that the recent Microsoft Azure service disruption has now been fully resolved. All affected Azure services are now operating normally, and recovery activities have been completed across all impacted regions. Our own monitoring also confirms that your hosted environments are stable, accessible, and performing as expected. The outage was linked to a configuration change within Azure Front Door (AFD) that caused DNS and connectivity issues across several regions. Microsoft promptly rolled back the change, restored normal operation, and is now conducting a full review of the event.

Read the full incident report →