On June 18th, 2019 beginning at 17:37 UTC, customers experienced the inability to login to the PingOne Directory services (login.pingone.com and directory-api.pingone.com). Services were fully recovered by 18:12 UTC after a database restoration.
At the time of the incident, there were planned maintenance activities on a downstream database cluster. These activities triggered an edge case scenario where AWS terminated all instances in the cluster in a specific AWS region.
June 18, 2019 (all times in UTC)
Service restoration occurred after the new database nodes were created and data was recovered. There was no data lost during this incident.