To maintain service continuity, all customers using the PingOne Mobile SDK for Android must upgrade to the latest supported versions by February 16, 2026. After this date, older versions of the SDK will become inoperable due to a mandatory infrastructure certificate rotation.
Impacted Versions Any Android SDK version released prior to July 2025 is impacted. Specifically: v1.11.0 and earlier v2.1.0 and earlier
What is Happening? On February 17, 2026, the PingOne Infrastructure team will begin a scheduled certificate rotation. Because the Android SDK versions listed above do not support the new certificates, any application still running these versions will lose the ability to communicate with PingOne services, resulting in a total loss of service for those users. This will impact Android device pairing and Push notifications.
Required Action To avoid service disruption, update your applications to the following versions (or newer) immediately: Upgrade v1.x users to: v1.11.1 (or latest) Upgrade v2.x users to: v2.1.1 (or latest) Note: Since older versions will become inoperable, we strongly recommend initiating a forced upgrade as soon as possible before the February 16th deadline.
Timeline Today – Feb 16: Upgrade and deployment window. Feb 17, 2026: Certificate rotation begins; legacy SDKs lose connectivity. For technical documentation or assistance with the upgrade process, please visit the PingIdentity Developer Portal or contact Global Customer Support.
Posted Jan 15, 2026 - 04:21 UTC
This scheduled maintenance affects: PingOne and PingOne Services - United States (.com services) (PingOne MFA: API, PingOne MFA), PingOne and PingOne Services - Singapore (.sg services) (PingOne MFA: API, PingOne MFA), PingOne and PingOne Services - Europe (.eu services) (PingOne MFA: API, PingOne MFA), PingOne and PingOne Services - Australia (.asia and .com.au services) (PingOne MFA API, PingOne MFA), and PingOne and PingOne Services - Canada (.ca services) (PingOne MFA: API, PingOne MFA).