All Systems Operational

About This Site

Scheduled maintenance and outage information for cloud.gov customers

Uptime over the past 90 days. View historical uptime.
cloud.gov customer applications Operational
90 days ago
99.99 % uptime
Today
Applications ? Operational
90 days ago
100.0 % uptime
Today
Logs intake and storage ? Operational
90 days ago
100.0 % uptime
Today
Service - CDN (cdn-route) ? Operational
90 days ago
100.0 % uptime
Today
Service - Relational databases (RDS) ? Operational
90 days ago
99.97 % uptime
Today
Service - S3 ? Operational
90 days ago
100.0 % uptime
Today
Service - Service account ? Operational
90 days ago
100.0 % uptime
Today
Service - Elasticache/Redis ? Operational
90 days ago
99.97 % uptime
Today
Service - Elasticsearch/OpenSearch ? Operational
90 days ago
99.97 % uptime
Today
Service - Custom Domain Service Operational
90 days ago
100.0 % uptime
Today
External domain service ? Operational
90 days ago
100.0 % uptime
Today
External domain service - CDN ? Operational
90 days ago
100.0 % uptime
Today
cloud.gov customer access Operational
90 days ago
99.91 % uptime
Today
Dashboard ? Operational
90 days ago
100.0 % uptime
Today
Logs front end ? Operational
90 days ago
100.0 % uptime
Today
Login ? Operational
90 days ago
99.67 % uptime
Today
API ? Operational
90 days ago
100.0 % uptime
Today
cloud.gov Pages Operational
90 days ago
100.0 % uptime
Today
Web Application ? Operational
90 days ago
100.0 % uptime
Today
Builds ? Operational
90 days ago
100.0 % uptime
Today
Hosted Sites ? Operational
90 days ago
100.0 % uptime
Today
Services cloud.gov depends on Operational
90 days ago
100.0 % uptime
Today
AWS CloudFront ? Operational
AWS elb-us-gov-west-1 ? Operational
AWS s3-us-gov-west-1 ? Operational
AWS rds-us-gov-west-1 ? Operational
AWS ec2-us-gov-west-1 ? Operational
AWS elasticsearch-us-gov-west-1 ? Operational
AWS elasticache-us-gov-west-1 ? Operational
GSA SecureAuth ? Operational
90 days ago
100.0 % uptime
Today
GSA Corporate Email Operational
90 days ago
100.0 % uptime
Today
cloud.gov website ? Operational
90 days ago
100.0 % uptime
Today
cloud.gov compliance notification ? Operational
Services cloud.gov Pages depends on Operational
90 days ago
99.96 % uptime
Today
GitHub Operational
90 days ago
100.0 % uptime
Today
GitHub Webhooks Operational
90 days ago
99.93 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Cloud Foundry Database Upgrade Apr 8, 2025 08:00-09:00 EDT

We’re planning routine maintenance for the cloud.gov API to upgrade the underlying database.

This DOES NOT impact your running user-facing applications. All applications and their databases/services will continue to run as normal.

During this maintenance window, any developer requests that use the cloud.gov API may not work, including:

* CF command-line interface (CLI) commands
* cloud.gov dashboard actions
* cloud.gov API requests

We will send out a notice once the upgrade is complete and developer requests are functional again.

If you have any questions or concerns, please contact us at support@cloud.gov
Posted on Mar 24, 2025 - 15:31 EDT
Mar 25, 2025

No incidents reported today.

Mar 24, 2025

No incidents reported.

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

No incidents reported.

Mar 20, 2025

No incidents reported.

Mar 19, 2025

No incidents reported.

Mar 18, 2025
Security Notice: GitHub Actions supply chain attack targeting Cloud.gov customers
Resolved - We are closing this incident since we have no further updates.

It is a customer responsibility to determine if they were impacted by this vulnerability, but please reach out to Cloud.gov support if you need any assistance in doing so.
Mar 18, 11:45 EDT
Monitoring - We've updated the original notification with the relevant CVE: https://www.cve.org/CVERecord?id=CVE-2025-30066

Since Cloud.gov has strong tenant isolation, the confirmed compromised customer did NOT impact any other Cloud.gov customers. We are providing this notification and updates in the interests of our customers.

INDICATORS OF COMPROMISE

At this time it appears the attacker used the compromised GitHub Action to obtain service account credentials (https://cloud.gov/docs/services/cloud-gov-service-account/), used those credentials to login to Cloud.gov, then used the `cf env` command to view sensitive application variables to enable further movement.

If you used the compromised Github Action, assess all your applications with the command

cf events APP_NAME

If you see entries like the following with the actor service-account@cloud.gov, and the event is not part of a deploy, then it's likely a malicious actor has obtained your application's credentials:

SAMPLE EVENT
time event actor description
2025-03-17T09:08:49.00-0400 audit.app.environment_variables.show service-account@cloud.gov

Regardless of whether there are indicators of compromise or not, if you used the compromise Github Action, you should rotate service account credentials per our documentation: https://cloud.gov/docs/services/cloud-gov-service-account/#rotating-credentials

You should also review GitHub Actions logs for the recent executions of the Action and see if it has leaked secrets. See "Review GitHub Actions Workflow Run Logs" at https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised
Mar 17, 19:36 EDT
Identified - The Cloud.gov customer security and operations team discovered today that malicious actors are leveraging the tj-actions/changed-files supply chain attack against Cloud.gov customers.

See CVE-2025-30066: https://www.cve.org/CVERecord?id=CVE-2025-30066

What you need to do:

If you use GitHub Actions for CI/CD and use the action "tj-actions/changed-files", you should consider your service potentially compromised.

Search your GitHub account for occurrences of the compromised action with a search like this (substitute your organization name for {MY_GITHUB_ORG}):

https://github.com/search?q=org%3A{MY_GITHUB_ORG}+uses%3A+tj-actions%2Fchanged-files%40v+language%3AYAML+path%3A.github%2F&type=code

If you are using this action, and have had any deployments between March 14 and March 15, 2025, consider your service compromised. We recommend these initial response steps:

- Declare an incident using your internal incident response process
- Freeze your GitHub Actions pipelines
- Rotate service-account credentials (Cloud.gov will be providing more guidance later today)
- Check for any other potential malicious code additions/deployments that may have been added with accounts that had potentially leaked credentials
- Notify the Cloud.gov incident team by emailing us your findings to cloud-gov-security@gsa.gov

We will be releasing updates with indicators of compromise (IOC) and further remediation steps.

Notes:
- You would be vulnerable even if your GitHub organization or code repository is private
- The Cloud.gov platform itself is not impacted
- This only applies to Cloud.gov customers using GitHub Actions AND the impacted action.

We are conducting an audit of potential attacks, but Cloud.gov customer development teams should conduct their own code audit. If you require assistance on your investigation, please also email cloud-gov-security@gsa.gov and request help.
Mar 17, 13:36 EDT
Mar 17, 2025
Mar 16, 2025

No incidents reported.

Mar 15, 2025

No incidents reported.

Mar 14, 2025

No incidents reported.

Mar 13, 2025

No incidents reported.

Mar 12, 2025

No incidents reported.

Mar 11, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage