System Status
System Status
Welcome to Ping Identity's system status site.System Uptime
System Uptime
System uptime in the past 90 days.Past Incidents Past Incidents
Welcome to Ping Identity's system status site.
Please subscribe to updates to get up to the minute alert notifications on any service interuptions.
Enabling Multi-Region Traffic (North America)
Scheduled Maintenance
Report for Ping Identity
Completed
Service verification is completed. We will continue to monitor the systems closely.
Update
We are seeing some delays and increased errors for PingID authentications using policy and are investigating. Authentications without policy are not affected.
In progress
Multi-region routing is enabled and teams are validating services now.
Scheduled
In order to serve you better, Ping Identity will be re-enabling traffic to the AWS US West Oregon Region. Traffic will be automatically balanced between both AWS regions in North America (Oregon and Ohio). This is being launched to improve overall system reliability, meet the needs of our growing service, and expand our capabilities for business continuity.
No changes are expected for our customers as this will only be a change in how we route our traffic based on geography and enable automated failover in the event of a service interruption in a single AWS region. Users may need to re-authenticate after this is completed.
The URLs will not change, and the Oregon IP addresses used prior to the launch of Ohio services last year there will be put back in service. Customers (and potentially their customers or affiliates) who have whitelisted the existing IP addresses for our endpoints should verify their lists to ensure the old IP addresses were not accidentally removed. Detailed information on IP addresses are listed in this article: https://ping.force.com/Support/PingIdentityArticle?id=kA31W000000CdU3SAK.
For additional questions please contact Ping Identity Technical Support by opening a case through The Community/Support site (https://www.pingidentity.com/en/account/sign-on.html).
No changes are expected for our customers as this will only be a change in how we route our traffic based on geography and enable automated failover in the event of a service interruption in a single AWS region. Users may need to re-authenticate after this is completed.
The URLs will not change, and the Oregon IP addresses used prior to the launch of Ohio services last year there will be put back in service. Customers (and potentially their customers or affiliates) who have whitelisted the existing IP addresses for our endpoints should verify their lists to ensure the old IP addresses were not accidentally removed. Detailed information on IP addresses are listed in this article: https://ping.force.com/Support/PingIdentityArticle?id=kA31W000000CdU3SAK.
For additional questions please contact Ping Identity Technical Support by opening a case through The Community/Support site (https://www.pingidentity.com/en/account/sign-on.html).
This scheduled maintenance affected: PingOne for Enterprise - Global (Administration API, AD Connect & Routing Service, Administration Portal, OAuth Configuration Service, Single Sign-on), PingOne for Enterprise - United States (.com services) (Directory API, Directory Login, Office365 Service, PingOne Dock, SCIM Provisioning), and PingID - United States (.com services) (PingID Authenticator, PingID Server, PingID SDK Server).