Cloud.gov Outage History
Cloud.gov is up right nowCloud.gov had 25 outages in the last 2 years totaling 1356h 19m of downtime — averaging 1 incident per month.
There were 25 Cloud.gov outages since July 10, 2024 totaling 1356h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
Intermittent issue accessing logs.fr.cloud.gov
Affected: Application logs - Intake and storageApplication metrics - Intake and storageBrokered database logs - Intake and storageBrokered service metrics - Intake and storageAudit events - Intake and storage
Timeline · 3 updates
- identified May 28, 2026, 12:47 PM UTC
Some customers trying to access logs.fr.cloud.gov might get HTTP 404 errors. Cloud.gov support staff have identified the issue and are working on deploying a resolution. Customers are asked to keep re-trying the website to gain access while the fix is being implemented. PLEASE NOTE - this issue only involves customer access to the logs front end. Logs and metrics are still flowing from the platform and apps into the logs system and are not affected. Log alerting is also not affected at this time. Thank You
- monitoring May 28, 2026, 01:05 PM UTC
The fix has been implemented and Cloud.gov support is monitoring the system at this time. Customers should be able to access the front end of logs.fr.cloud.gov again.
- resolved May 28, 2026, 02:06 PM UTC
This incident has been resolved.
Cloud.gov Email Ticket Service Outage
Timeline · 2 updates
- identified Apr 08, 2026, 05:34 PM UTC
Zendesk, the support ticket system used by Cloud.gov, is currently experiencing email relay issues and not generating tickets when emails are sent to [email protected]. The Cloud.gov support staff are receiving the emails and can respond directly to customers while Zendesk fixes their relay issues. Zendesk status: https://status.zendesk.com/
- resolved Apr 09, 2026, 11:00 AM UTC
This incident has been resolved.
JSON application log ingestion failures
Timeline · 1 update
New user signups not working
Affected: Login
Timeline · 5 updates
Resolved - Cloudwatch Logs Ingestion Interruption
Timeline · 1 update
- resolved Dec 19, 2025, 09:14 PM UTC
Resolved: Cloudwatch logs (for example, RDS logs) did not ingest into Cloud.gov Logs between December 4, 2025 at 11:14 AM ET and December 17, 1:45 PM ET. The issue was caused by a production change that required AES-256 encryption on the S3 buckets used for log ingestion. This change prevented a Lambda in the ingestion pipeline from successfully writing logs to S3. The Lambda did not surface errors, which delayed detection. At 1:45 PM ET on December 17, the bucket policy was corrected and log ingestion was resumed. No further customer action is required. Impact: Customers may see gaps in Cloudwatch log data for the affected time window. Prevention: We are improving ingestion monitoring, expanding end-to-end smoke tests, and updating our error handling so failures surface immediately. Next update: No further updates are planned.
Partial log ingestion delay and failures - Resolved
Timeline · 2 updates
Brokered service logs and metrics not visible to customers
Affected: Brokered database logs - Intake and storage
Timeline · 2 updates
Cloud.gov operations during the FY26 appropriations lapse
Affected: ApplicationsWeb ApplicationBuildsHosted Sites
Timeline · 2 updates
- monitoring Oct 01, 2025, 05:25 PM UTC
All services are operational, but please expect slower support response times. The Cloud.gov team will continue to operate all services during the lapse in FY26 appropriations, however all custom work, e.g. for Pages Studio, is on pause. For questions or help with your account or services, reach us at [email protected].
- resolved Nov 18, 2025, 02:18 PM UTC
This incident has been resolved.
Brokered database logs not ingested
Timeline · 2 updates
Intermittent 403 responses
Timeline · 2 updates
Logs delayed on logs.fr.cloud.gov
Affected: Logs intake and storage
Timeline · 3 updates
403 Forbidden Responses for API
Timeline · 2 updates
General Internet Outage Could Be Impacting Customer Access to Cloud.gov
Affected: Cloud.gov website
Timeline · 2 updates
- investigating Jun 12, 2025, 07:45 PM UTC
While Cloud.gov is currently not experiencing an outage for the platform nor is any of our underlying services partners, some customers might be experiencing issues reaching Cloud.gov. If you are experiencing any issues in accessing, deploying, or using Cloud.gov please contact us via our normal support channel at [email protected].
- resolved Jun 12, 2025, 09:23 PM UTC
The impacted internet service and platform providers are now reporting their issues are resolved, so we are closing this issue.
Outage for Cloud.gov logging system
Affected: Logs front end
Timeline · 4 updates
Log outage for OpenSearch
Affected: Logs front end
Timeline · 3 updates
Security Notice: GitHub Actions supply chain attack targeting Cloud.gov customers
Affected: Cloud.gov compliance notification
Timeline · 3 updates
Minor outage for brokered services - RDS, Elasticache/Redis, Elasticsearch/OpenSearch
Timeline · 1 update
Cloud.gov Account Password Resets Unavailable
Affected: Login
Timeline · 1 update
- resolved Jan 27, 2025, 02:36 PM UTC
First reported Sunday January 26 at 10 AM ET, customers that utilize the Cloud.gov Identity Provider began receiving “500” errors when attempting to reset their passwords. Cloud.gov Operations became aware of the issue at the start of business Monday, January 27th 2025 and immediately began their investigation. The Cloud.gov team has identified and resolved the issue. Please reach out to [email protected] with any further issues related to password resets.
Cloud.gov failed logins for some saml IdP providers
Timeline · 1 update
- resolved Dec 17, 2024, 05:17 PM UTC
A newer version of UAA is forcing additional validation on some of the IdP saml providers was rolled out as part of a platform upgrade. This caused logins to fail for the impacted organizations leveraging those IdP saml providers. As of 11:55am ET this change was rolled back and we are working with impacted organizations to identify a root cause.
Customer GitHub actions referencing cloud-gov/cg-cli-tools failing
Timeline · 1 update
- resolved Oct 04, 2024, 04:21 PM UTC
As part of a broader project, Cloud.gov renamed the GitHub repository cloud-gov/cg-cli-tools, which hosts a GitHub Action that customers can use to deploy applications to Cloud.gov. When a repository is renamed, GitHub redirects most requests from the old repository name to the new one. However, GitHub Actions does not automatically redirect calls to an action hosted by a renamed repository. This caused Actions referencing this repository to fail. The original repository name has been restored and use of the Action should return to normal.
GSA SecureAuth outage
Affected: GSA SecureAuth
Timeline · 2 updates
- investigating Sep 24, 2024, 06:28 PM UTC
GSA SecureAuth is currently experiencing an outage. GSA customers who log into cloud.gov via SecureAuth may see the error "Invalid User" when attempting to sign in. We are monitoring the outage and will post updates as available.
- resolved Sep 24, 2024, 06:42 PM UTC
SecureAuth availability has been restored. GSA users should be able to sign into cloud.gov. The cloud.gov team will continue to monitor for any further incidents.
Cloud Foundry cf CLI GPG error
Timeline · 2 updates
- investigating Sep 11, 2024, 02:41 PM UTC
Customers who install the Cloud Foundry (cf) CLI using the apt package manager are encountering the following error: W: GPG error: https://cf-cli-debian-repo.s3.amazonaws.com/ stable InRelease: The following signatures were invalid: EXPKEYSIG 172B5989FCD21EF8 CF CLI Team [[email protected]](mailto:[email protected]) E: The repository ' https://cf-cli-debian-repo.s3.amazonaws.com/ stable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. This issue is being tracked upstream with this issue: https://github.com/cloudfoundry/cli/issues/3194 The cloud.gov team recommends installing the CLI using an alternate installation method while the Cloud Foundry team works to resolve the issue. The latest releasees of the CLI are available on GitHub: https://github.com/cloudfoundry/cli/releases
- resolved Sep 11, 2024, 06:51 PM UTC
The Cloud Foundry team has resolved the issue and apt installations are now working normally. https://github.com/cloudfoundry/cli/issues/3194#issuecomment-2344076985
Intermittent issues connecting to S3 buckets
Affected: AWS s3-us-gov-west-1
Timeline · 4 updates
Outage for online CF buildpacks for new application pushes
Affected: Applications
Timeline · 2 updates
- investigating Jul 10, 2024, 01:45 PM UTC
Details: An issue with an upstream dependency affecting new Cloud Foundry (CF) applications was identified around 9 AM ET on July 10, 2024. This issue is causing failures when attempting to push new applications that utilize online buildpacks pointing to ‘buildpacks.cloudfoundry.org’. Current Status: We are actively monitoring the situation and are in communication with the group responsible for the CDN and this URL. Impact: Currently running applications are not impacted. Customers may experience failures when pushing new applications that depend on the affected buildpacks. Next steps: We will provide updates as soon as more information becomes available and as the situation progresses towards resolution. We apologize for any inconvenience caused and appreciate your understanding and patience as we work to resolve this issue.
- resolved Jul 10, 2024, 02:03 PM UTC
The incident has been resolved. Applications which leverage online buildpacks at buildpacks.cloudfoundry.org will now build. Again, thank you for your patience as we worked this problem to resolution.