Is there an Delinea outage?
Delinea status: Systems Active
Last checked: 10 minutes ago
Get notified about any outages, downtime or incidents for Delinea and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 10 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: **Impact:** Beginning on 2/23/24 at approx. 21:10 UTC, engines that received the new version and had proxying turned on failed to start and were unavailable. No messages were processed by these engines and they were not reachable for any capability. **Issue:** An update to the engine SSH proxy implementation generated an assembly version conflict. This caused engines to fail loading the SSH proxy library. **Resolution:** The issue was resolved by reverting the change and releasing a new version of the Distributed Engine. Since the failure prevented the engine update check, SSH proxying was temporarily disabled and re-enabled for affected customers to allow engines to auto-upgrade. By 00:30 UTC on 2/24 the large majority of customer engines were updated to version 8.4.25.0. A very small percentage of engines had upgrade issues that could not be resolved from the back end. This list was given to support for direct resolution with the customers. **Action Items:** **To address this and prevent future occurrences:** Add automation tests to cover additional scenarios with engine upgrade and proxying. Improve Engine upgrade process so that an assembly load failure does not block upgrades. Investigate options for better back-end tracking of engine issues. Review and improve customer communication process. **Incident Start Time:** 2/23/24 21:10 UTC **Incident End Time:** 2/24/24 00:30 UTC
Status: Postmortem
Impact: Minor | Started At: Feb. 23, 2024, 11:09 p.m.
Description: **Impact:** Beginning on 2/23/24 at approx. 21:10 UTC, engines that received the new version and had proxying turned on failed to start and were unavailable. No messages were processed by these engines and they were not reachable for any capability. **Issue:** An update to the engine SSH proxy implementation generated an assembly version conflict. This caused engines to fail loading the SSH proxy library. **Resolution:** The issue was resolved by reverting the change and releasing a new version of the Distributed Engine. Since the failure prevented the engine update check, SSH proxying was temporarily disabled and re-enabled for affected customers to allow engines to auto-upgrade. By 00:30 UTC on 2/24 the large majority of customer engines were updated to version 8.4.25.0. A very small percentage of engines had upgrade issues that could not be resolved from the back end. This list was given to support for direct resolution with the customers. **Action Items:** **To address this and prevent future occurrences:** Add automation tests to cover additional scenarios with engine upgrade and proxying. Improve Engine upgrade process so that an assembly load failure does not block upgrades. Investigate options for better back-end tracking of engine issues. Review and improve customer communication process. **Incident Start Time:** 2/23/24 21:10 UTC **Incident End Time:** 2/24/24 00:30 UTC
Status: Postmortem
Impact: Minor | Started At: Feb. 23, 2024, 11:09 p.m.
Description: We've observed latency when accessing the Delinea Platform. Our team has implemented measures to resolve the issue, and we are continuing to monitor the platform's performance closely to ensure stability.
Status: Resolved
Impact: None | Started At: Feb. 15, 2024, 10 p.m.
Description: We've observed latency when accessing the Delinea Platform. Our team has implemented measures to resolve the issue, and we are continuing to monitor the platform's performance closely to ensure stability.
Status: Resolved
Impact: None | Started At: Feb. 15, 2024, 10 p.m.
Description: _**Title**:_ _Secret Server Cloud unavailable from some users in the Philippines region_ _**Impact**_ _Beginning on Feb 1st, 2024 at approx. 10:30 AM SGT \(2:30 AM UTC\), some users in the Philippines regions were unable to access Secret Server Cloud and may have encountered an error similar to “Error 20” or “Error 32”. The issue was mitigated by 11:30 AM SGT \(3:30 AM UTC\)._ _**Issue**_ _There was an issue with our upstream Web Application Firewall provider at their Manila PoP. This only affected users that were routed to the Manila PoP as part of the Anycast network._ _**Resolution**_ _We are continuing to work with our upstream provider to determine the cause and resolution of the issue._
Status: Postmortem
Impact: Minor | Started At: Feb. 1, 2024, 2: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.
