Migrating PingOne/PingID To New AWS Region
Scheduled Maintenance Report for Ping Identity
Completed
The scheduled maintenance has been completed.
Posted about 1 month ago. Oct 20, 2018 - 08:54 UTC
Update
Migration and qualification is completed for all services. We recommend customers test/validate their workflows. We will continue to monitor the systems closely.
Posted about 1 month ago. Oct 20, 2018 - 08:44 UTC
Update
We have identified the cause of the provisioning delays and are deploying a fix.
Posted about 1 month ago. Oct 20, 2018 - 08:08 UTC
Update
We are currently investigating some delays with provisioning. Will post another update in 30 minutes.
Posted about 1 month ago. Oct 20, 2018 - 07:31 UTC
Update
We have completed testing and validation on the following services:

AD Connect and Routing
Directory API
Directory Login
OAuth Service
Office 365 Service
PingOne dock
PingID Authenticator
PingID Server
PingID SDK Server
SCIM Provisioning
Single Sign-on
Posted about 1 month ago. Oct 20, 2018 - 06:38 UTC
Update
We have completed testing and validation on the following services:

AD Connect and Routing
Single Sign-on
PingOne dock
PingID SDK Server
Posted about 1 month ago. Oct 20, 2018 - 05:54 UTC
Verifying
Migration is completed and teams are validating services now. Updates will be posted as services are confirmed and validated.

We have completed testing and validation on the following services:

PingID SDK Server
Posted about 1 month ago. Oct 20, 2018 - 05:41 UTC
In progress
The migration to Ohio is in progress. There will be a short interruption in service as endpoints are migrated to the new region. Another update will be posted once the initial activities are completed. Users may need to re-authenticate after the migration.
Posted about 1 month ago. Oct 20, 2018 - 05:21 UTC
Scheduled
As announced earlier this year, Ping Identity will be expanding our production systems into the AWS US East Ohio Region. In order to serve you better, this region is scheduled to start carrying production traffic later this month. Services in this region are being launched to improve overall system reliability, meet the needs of our growing service, and expand our capabilities for business continuity.

While the URLs will not change, there will be new IP addresses associated with the additional
regional endpoints. Customers (and potentially their customers or affiliates) who have
whitelisted the existing IP addresses for these endpoints will need to add additional IP
addresses for the new endpoints. Detailed information on the new IP addresses are listed in this article: https://ping.force.com/Support/PingIdentityArticle?id=kA31W000000CdU3SAK. Please note that the existing endpoint IP addresses remain in effect for this service expansion.

As long as customer applications do not cache the old IP addresses and honor DNS time to live values, there should be no additional changes required. In the event that those addresses are cached, a restart may be required. We recommend customers have someone available to test/validate their workflows after traffic is routed to the new region. SSO and MFA services should be available by 04:30 UTC and all services will be available by 06:00 UTC.

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).
Posted about 2 months ago. Oct 04, 2018 - 18:12 UTC
This scheduled maintenance affected: PingOne Services (North America Critical Path (.com), Admin Portal Monitor, Directory API, Single Sign-on, Single Sign-On (PingOne SSO for SaaS Apps/APS), Administration Portal, OAuth Service, Administration API, AD Connect & Routing Service, PingOne dock - North America (.com), Directory Login - North America (.com), Directory API - North America (.com), Office365 Service - North America (.com), SCIM Provisioning - North America (.com)) and PingID Services (PingID Authenticator - North America (.com), PingID Server - North America (.com), PingID SDK Server - North America (.com)).