All Systems Operational

About This Site

Scheduled maintenance and outage information for cloud.gov customers

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
100.0 % uptime
Today
Service - S3 ? Operational
90 days ago
100.0 % uptime
Today
Service - Service account ? Operational
90 days ago
100.0 % uptime
Today
Redis ? Operational
90 days ago
100.0 % uptime
Today
Elasticsearch ? Operational
90 days ago
100.0 % uptime
Today
Service - Custom Domain Service Operational
90 days ago
99.98 % 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
98.68 % uptime
Today
Dashboard ? Operational
90 days ago
100.0 % uptime
Today
Logs front end ? Operational
90 days ago
94.75 % uptime
Today
Login ? Operational
90 days ago
100.0 % uptime
Today
API ? Operational
90 days ago
100.0 % uptime
Today
Services cloud.gov depends on Operational
AWS EC2-us-west-1 ? Operational
AWS EC2-us-west-2 ? Operational
AWS CloudFront ? Operational
AWS ELB-us-west-1 ? Operational
AWS ELB-us-west-2 ? Operational
AWS RDS-us-west-1 ? Operational
AWS RDS-us-west-2 ? Operational
AWS S3-us-standard ? Operational
AWS S3-us-west-1 ? Operational
AWS S3-us-west-2 ? Operational
cloud.gov website ? Operational
90 days ago
100.0 % 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.
Scheduled Maintenance
This message is to let you know about recent and upcoming changes to cloud.gov’s relational database services, which include the following:

-- Deprecation of the shared instance plans
-- Scaling down of under-utilized instances
-- New service plan offerings
-- Ability to modify existing service instances
-- Documentation updates on our website


What is happening and what is the impact to cloud.gov customers?

As of January 24, 2021, shared instance plans will no longer be available as a choice for creating new database instances. Customers will only be able to choose from the dedicated service plans. Sandbox accounts will only have access to the micro-psql and small-mysql service plans.

Within 14 days of this notice, we will also begin scaling down under-utilized database instances to smaller service plans and asking if unused instances are still needed. We will initially target databases with 10 or fewer recent concurrent connections and low CPU usage. Applications that are dependent on database availability may experience a short period of unavailability during the scale operation; please reach out to our team with your org, space, and service name if there are days we should avoid resizing deployed instances. As a cost-recoverable program, we are tasked with being responsible stewards for our operating costs and this will allow us to keep costs under control.


What do cloud.gov customers need to do?

At this time, customers who are currently running shared database server instances will need to begin planning a migration to a dedicated instance plan. To perform a migration, a customer must export their existing database and restore it into a new instance created with a dedicated service plan. We have instructions on how to export a database on our website and will send out more information on how to perform the restore in the near future.

New sandbox users will be able to use the new dedicated instance plans right away, and we will be reaching out to customers about under-utilized instances at the aforementioned date with additional information and instructions for next steps.


Why are the shared instance plans being deprecated?

We are deprecating the shared instance plans in favor of offering new, micro- and small-sized dedicated instance plans. This will enable us to improve our security compliance posture and offer more performant and efficient database server choices for our customers.

It will also enable more flexibility for customers in managing their own database instances and allow both customers and our own platform operators to manage database backups and restorations. This is not currently possible in the shared instance plans.


How can customers leverage the new service plans?

Customers can begin using the new service plans right away when creating a new database service. In addition to this, we have also added the ability to modify existing database services in place. Customers can now switch database service plans by following the update instructions in our documentation. There are a couple of things to note about this:

-- Switching between shared instance plans and dedicated instance plans is not possible; you must manually backup and restore your database
-- Switching between database engines (e.g., PostgreSQL and MySQL) is not possible; you must switch between plans for the same database engine

Furthermore, we have also updated our documentation to include all of the service plans we currently offer in cloud.gov and which plans are available in sandbox accounts.


If you have any questions or concerns, please contact us at support@cloud.gov.
Posted on Aug 7, 14:45 EDT
As part of our reliability and stability enhancements to cloud.gov, the legacy Redis 3.2 and Elasticsearch 5.6 offerings from cloud.gov will be deprecated as of April 5, 2021. In accordance with our deprecation policy, provisioning of new instances will be disabled on December 6, 2020 and on April 5, 2021 we will shut down all active instances. This work is an important step in moving cloud.gov towards a more stable and reliable platform by moving away from a bespoke Kubernetes instances to AWS-hosted services. Learn more about our deprecation policy here: https://cloud.gov/docs/technology/responsibilities/#deprecation-policy

The new services of AWS Elasticache for Redis 5.0.6 and AWS Elasticsearch 7.4 replace the legacy Redis 3.2 and Elasticsearch 5.6 services. These new offerings will offer substantial benefits over our legacy offerings, including:

* Higher availability due to being hosted and managed services from AWS.

* Automatic snapshots with no customer intervention for purposes of data restore/recovery.

* Allowing for future transitions to newer versions of these services as AWS makes them available.

As part of the transition of these new replacement services from beta to production the following will take place:

* The beta plan names will change but the existing services instances created during the beta will remain for now. In general the ‘BETA’ name prefix will be dropped from the plan name

* Beta customers - if you would like to continue using your beta instances as production instances, please contact support via a support ticket or my emailing us at support@cloud.gov. Let us know the org, space, and service instance name that you would like to remain as a production instance.

* Beta customers - If you don’t want to keep your beta instances - after two weeks from this announcement (November 20, 2020) any Beta instances remaining on the platform not converted to production instances via a customer support request will be deleted.

More technical details on these new services can be found below:

* AWS-Elasticache-Redis: https://cloud.gov/docs/services/aws-elasticache/

* AWS-Elasticsearch: https://cloud.gov/docs/services/aws-elasticsearch/

If you have any questions, please contact support@cloud.gov.
Posted on Nov 6, 15:51 EST
Past Incidents
Jan 27, 2021

No incidents reported today.

Jan 26, 2021

No incidents reported.

Jan 25, 2021

No incidents reported.

Jan 24, 2021

No incidents reported.

Jan 23, 2021

No incidents reported.

Jan 22, 2021

No incidents reported.

Jan 21, 2021
Completed - The scheduled maintenance is now completed.
Jan 21, 15:46 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 21, 09:00 EST
Scheduled - The cloud.gov support team will be performing routine maintenance on the platform that services legacy Elasticsearch and Redis instances for customers. During this window customers access to their instances might be interrupted.
Jan 13, 15:29 EST
Jan 20, 2021

No incidents reported.

Jan 19, 2021
Resolved - The issue with the broker has been resolved and service has been restored.
Jan 19, 08:05 EST
Investigating - The cloud.gov domains broker is current unavailable. Support is reviewing the issue.
Jan 19, 07:46 EST
Jan 18, 2021

No incidents reported.

Jan 17, 2021

No incidents reported.

Jan 16, 2021

No incidents reported.

Jan 15, 2021

No incidents reported.

Jan 14, 2021

No incidents reported.

Jan 13, 2021

No incidents reported.