Cloud.gov incident

New user signups not working

Minor Resolved View vendor source →

Cloud.gov experienced a minor incident on December 29, 2025 affecting Login, lasting 1d 21h. The incident has been resolved; the full update timeline is below.

Started
Dec 29, 2025, 03:26 PM UTC
Resolved
Dec 31, 2025, 12:33 PM UTC
Duration
1d 21h
Detected by Pingoru
Dec 29, 2025, 03:26 PM UTC

Affected components

Login

Update timeline

  1. investigating Dec 29, 2025, 03:26 PM UTC

    Cloud.gov support is looking into an issue when inviting new users to the platform using the Cloud.gov IDP provider. PLEASE NOTE - this only effects new Cloud.gov IDP users to the platform and not preventing EXISTING users from signing in. New users on existing IDP providers (census.gov, DOJ.gov, dol.gov, EPA.gov, FDIC.gov, fec.gov, frtib.gov, GSA.gov, mcc.gov, nih.gov, OMB.gov, onrr.gov, usaid.gov, and SSA.gov) are NOT affected.

  2. investigating Dec 29, 2025, 09:59 PM UTC

    Cloud.gov support is continuing to investigate the root cause of inviting new users. If users are being blocked please reach out to Cloud.gov support at [email protected] for a manual workaround.

  3. identified Dec 30, 2025, 05:39 PM UTC

    Cloud.gov support has identified the issue with new user signups and is currently implementing a fix thorough lower environments first before production. We plan to update production tomorrow Wednesday 12/31/25. If users are being blocked please reach out to Cloud.gov support at [email protected] for a manual workaround.

  4. resolved Dec 31, 2025, 12:33 PM UTC

    Cloud.gov has applied the new user signup fix into production and the process is now working as expected. If you encounter any issues signing up for Cloud.gov, please reach out to Cloud.gov support at [email protected].

  5. postmortem Jan 05, 2026, 07:28 PM UTC

    From approximately December 11, 2025 7:00 AM ET to December 31, 2025 7:30 AM ET, new [Cloud.gov](http://Cloud.gov) users attempting to complete new user signup not using their own agency IdP could not have completed the process. ‌ New users on existing IDP providers \([census.gov](http://census.gov), [DOJ.gov](http://DOJ.gov), [dol.gov](http://dol.gov), [EPA.gov](http://EPA.gov), [FDIC.gov](http://FDIC.gov), [fec.gov](http://fec.gov), [frtib.gov](http://frtib.gov), [GSA.gov](http://GSA.gov), [mcc.gov](http://mcc.gov), [nih.gov](http://nih.gov), [OMB.gov](http://OMB.gov), [onrr.gov](http://onrr.gov), [usaid.gov](http://usaid.gov), and [SSA.gov](http://SSA.gov)\) were NOT affected. ‌ The issue was related to a newer version of UAA for cross-site request forgery \(CSRF\) token enforcement of authenticated users from unknowingly executing unwanted actions with their current session. An updated version of the activation form was rolled out to production the morning of December 31st. ‌ There is no customer required action. If customers experience problems signing up at [Cloud.gov](http://cloud.gov), please reach out to [Cloud.gov](http://cloud.gov) support at [[email protected]](mailto:[email protected]). ‌ Next update: No further updates are planned.