This incident has been resolved.

Microsoft has started releasing mitigation, and we are seeing sites come back up. We will continue to monitor until an all clear is given. Further information can be found on their monitoring site: https://azure.status.microsoft/en-us/status

Microsoft has started releasing mitigation, and we are seeing sites come back up. We will continue to monitor until an all clear is given. Further information can be found on their monitoring site: https://azure.status.microsoft/en-us/status

3rd party has started releasing mitigation, and we are seeing sites come back up. We will continue to monitor until an all clear is given.

We are continuing to track the outage caused by 3rd party infrastructure issues

The issue has been identified with the root cause being a 3rd party infrastructure issue

We are currently investigating an issue with Hippo CMMS. We will update you when we have more information.

**Hippo Detailed Root Cause Analysis \(RCA\) – Severity 1 Event July 18th, 2024**  We are profoundly grateful for your continued support and loyalty. We value your feedback and appreciate your patience as we worked to resolve this incident. **Description:** On July 18th, 4:29 PM MST we received reports that customers were not able to login. When attempting to load URL in browser, we got a blank page. Our Cloud Ops team informed us that this outage was due to a Microsoft Azure server outage that impacted many customers worldwide. **Type of Event:** S2 event - Service disruption. Eptura Asset application was not accessible. **Services\\Modules Impacted:** All modules impacted **Remediation:** Once Microsoft restore services, our sites came back online. **Timeline:** 7-18-24 4:29 PM – T1 Reports possible outage in Product – Asset Teams channel 7-18-24 4:34 PM – T2 starts investigation and checking site 7-18-24 4:36 PM – T2 recognizes S1 Event 7-18-24 4:36 PM – Support informs Cloud Ops team \(JIRA CM-83772\) 7-18-24 4:36 PM - QA Notifies Cloud Ops team in Teams channel about event 7-18-24 4:38 PM – Pager Duty Initiated 7-18-24 4:48 PM - Detailed post made by Support in Eptura-Asset-Fire-alarm channel 7-18-24 5:00 PM – Cloud Ops begins looking into the issue 7-18-24 5:15 PM – T1 reports Hippo CMMS is down as well 7-18-24 5:28 PM – OPS identifies the issue is a result of Microsoft Azure Outage 7-18-24 5:44 PM – Support creates JIRA for Hippo tracking of the same issue \(CM-83777\) 7-18-24 7:35 PM – Microsoft identifies the issue and begins applying mitigation 7-18-24 8:20 PM – Sites are starting to come back up, continuing to monitor until an all clear is given  7-18-24 10:49 PM – All clear issued **Total Duration of Event:** 7 hours 14 minutes **Root Cause Analysis:** Microsoft Azure Server Outage **Preventative Action:** Cloud Ops will monitor Azure service so we are aware of the issue sooner and can proactively communicate that to our customer base.