Resolved -
Okta has confirmed that the issue impacting their Core Authentication service for customers in US Cell 7 has been fully resolved. Plume services that rely on Okta authentication have returned to normal operation.
Okta will share additional root-cause details in the coming days.
Monitoring -
Okta reports that their Core Platform service is showing signs of recovery following successful mitigation efforts with their upstream provider. Plume services that rely on Okta authentication may also be stabilizing. Both Okta and Plume teams continue to monitor the situation closely. We will provide another update as soon as new information becomes available. For the latest details from Okta, please visit: https://status.okta.com/.
Dec 3, 15:58 UTC
Identified -
On December 3, 2025 at 5:15 am PST, the Okta team identified an issue affecting connectivity to their Core Platform service for customers in US Cell 7. During this time, users may experience intermittent issues when using Okta. Okta and Plume teams are actively investigating and working to mitigate the impact. We will share another update as soon as more information is available. For the latest status, please visit: https://status.okta.com/.
Dec 3, 15:32 UTC
Resolved -
This incident has been resolved.
Dec 3, 15:27 UTC
Investigating -
On December 3, 2025 at 5:15 am PST, the Okta team identified an issue affecting connectivity to their Core Platform service for customers in US Cell 7. During this time, users may experience intermittent issues when using Okta. Okta and Plume teams are actively investigating and working to mitigate the impact. We will share another update as soon as more information is available. For the latest status, please visit: https://status.okta.com/.
Dec 3, 13:15 UTC
Resolved -
This incident has been resolved.
Dec 3, 14:52 UTC
Investigating -
Service access from Frankfurt area has been disrupted since 2025-12-03 13:06:46. Users might experience trouble accessing the mobile app and backend support tools used for monitoring and onboarding. Plume's engineering team is investigating the issue and working on a correction.
Dec 3, 13:26 UTC