Is there an Delinea outage?
Delinea status: Systems Active
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Delinea and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Delinea and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Delinea.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|
View the latest incidents for Delinea and check for official updates:
Description: The incident affecting the services listed below has been resolved. Our team has deployed a fix, and all systems are now operating normally. Traffic to the endpoints identified previously has been unblocked. We apologize for any inconvenience this incident may have caused. For any questions or concerns, please reach out to our support team at https://support.delinea.com.
Status: Resolved
Impact: Major | Started At: April 12, 2024, 7:34 p.m.
Description: The incident affecting the services listed below has been resolved. Our team has deployed a fix, and all systems are now operating normally. Traffic to the endpoints identified previously has been unblocked. We apologize for any inconvenience this incident may have caused. For any questions or concerns, please reach out to our support team at https://support.delinea.com.
Status: Resolved
Impact: Major | Started At: April 12, 2024, 7:34 p.m.
Description: **Title**_:_ Privilege Manager Cloud \(PMC\) Issues in East US starting on April 3rd, 2024. **Impact:** Beginning on April 3rd, 2024, at approximately 7:52:40 PM ET, PMC customers would have started experiencing issues accessing their systems. **Issue:** On April 3rd, 2024, at approximately 7:52:40 PM ET, Azure SQL Databases in East US started experiencing issues. New connections to databases in this region may have resulted in an error or timeout. Existing connections remained available to accept new requests, however if those connections were terminated and re-established, they may have failed. Microsoft suspects that a potential deployment on their frontend gateways caused SQL database availability issues impacting customer connectivity. Microsoft worked to mitigate the issue by stopping the active rollout of their deployment. **Resolution:** At approximately 8:22 PM ET our monitoring systems started alerting regarding an issue. After initial triage, we estimated that roughly 25% of US based PMC customers were experiencing issues. At approximately 9:38 PM ET, affected PMC customers were back online and systems accessible. Our engineers monitored the Azure incident and waited for it to be fully resolved before closing the incident on our side. At approximately 11:29 PM ET on April 3rd, 2024, the Azure team declared the incident mitigated. **Action Items:** No action items to address. **Incident Start Time:** _April 3rd, 2024, 07:52:40 PM ET_ **Incident End Time:** _April 3rd, 2024, 11:29 PM ET_
Status: Postmortem
Impact: Major | Started At: April 4, 2024, 12:41 a.m.
Description: **Title**_:_ Privilege Manager Cloud \(PMC\) Issues in East US starting on April 3rd, 2024. **Impact:** Beginning on April 3rd, 2024, at approximately 7:52:40 PM ET, PMC customers would have started experiencing issues accessing their systems. **Issue:** On April 3rd, 2024, at approximately 7:52:40 PM ET, Azure SQL Databases in East US started experiencing issues. New connections to databases in this region may have resulted in an error or timeout. Existing connections remained available to accept new requests, however if those connections were terminated and re-established, they may have failed. Microsoft suspects that a potential deployment on their frontend gateways caused SQL database availability issues impacting customer connectivity. Microsoft worked to mitigate the issue by stopping the active rollout of their deployment. **Resolution:** At approximately 8:22 PM ET our monitoring systems started alerting regarding an issue. After initial triage, we estimated that roughly 25% of US based PMC customers were experiencing issues. At approximately 9:38 PM ET, affected PMC customers were back online and systems accessible. Our engineers monitored the Azure incident and waited for it to be fully resolved before closing the incident on our side. At approximately 11:29 PM ET on April 3rd, 2024, the Azure team declared the incident mitigated. **Action Items:** No action items to address. **Incident Start Time:** _April 3rd, 2024, 07:52:40 PM ET_ **Incident End Time:** _April 3rd, 2024, 11:29 PM ET_
Status: Postmortem
Impact: Major | Started At: April 4, 2024, 12:41 a.m.
Description: **Title**_:_ Secret Server Cloud \(SSC\) Issues in East US starting on April 3rd, 2024. **Impact:** Beginning on April 3rd, 2024, at approximately 7:52:40 PM ET, SSC customers would have started experiencing issues accessing their systems. **Issue:** On April 3rd, 2024, at approximately 7:52:40 PM ET, Azure SQL Databases in East US started experiencing issues. New connections to databases in this region may have resulted in an error or timeout. Existing connections remained available to accept new requests, however if those connections were terminated and re-established, they may have failed. Microsoft suspects that a potential deployment on their frontend gateways caused SQL database availability issues impacting customer connectivity. Microsoft worked to mitigate the issue by stopping the active rollout of their deployment. **Resolution:** At approximately 7:54 PM our monitoring systems started alerting regarding an issue. After initial triage, we estimated that roughly 25% of US based SSC customers were experiencing issues. At approximately 8:26 PM ET, SC failover was initiated. However, due to an issue with the automated tool to perform failover, we began to manually perform failover, which increased our response and resolution time. At approximately 10:36 PM ET the failover had completed, and all SSC systems were operational. Our engineers monitored the Azure incident and waited for it to be fully resolved before closing the incident on our side. At approximately 11:29 PM ET on April 3rd, 2024, the Azure team declared the incident mitigated. At approximately 3:56 AM ET on April 4th, 2024, a rollback to restore functionality in the primary East US region for SSC was completed. **Action Items:** 1\. Investigate issues with tooling that facilitates automated failover. **To address this and prevent future occurrences:** IN PROGRESS – Improve failover automation tooling and capabilities. **Incident Start Time:** _April 3rd, 2024, 07:52:40 PM ET_ **Incident End Time:** _April 3rd, 2024, 11:29 PM ET_
Status: Postmortem
Impact: Major | Started At: April 4, 2024, 12:30 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
