Update - We are continuing to monitor the upgrade status and system performance.
Oct 28, 16:24 EDT
Monitoring - We have received reports of degraded performance while accessing logs in the system. We continue to investigate these reports and ask customers to please contact support@cloud.gov if you experience issues.

While currently undergoing a scaling upgrade, the logging system does appear healthy. We do not expect the scaling actions to have any impact on the system. We did observe a fairly significant spike in traffic flowing through the load balancers as well as an increase in latency during a 15 minute period this morning.

We are continuing to monitor system health and accessibility and again ask customers to reach out with any further issues.
Oct 28, 13:53 EDT

About This Site

Scheduled maintenance and outage information for cloud.gov customers

cloud.gov customer applications Operational
90 days ago
100.0 % 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
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.73 % uptime
Today
Dashboard ? Operational
90 days ago
100.0 % uptime
Today
Logs front end ? Operational
90 days ago
98.92 % 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
fr.cloud.gov Deprecation Dec 3, 00:00-01:00 EDT
As part of our upcoming security enhancements to cloud.gov, we intend to deprecate customer usage of the *.fr.cloud.gov domain as of December 3, 2020. Customer applications will remain accessible on the newer *.app.cloud.gov domain, which has been available for usage since October 2016. The purpose of the deprecation is to allow additional WAF hardening of core components within cloud.gov’s administrative tooling.

Customers can check their current application routes by running the following command in each organization and space they have access to (a space must be set for this command to work):

$ cf routes

Customers that are currently using the *.app.cloud.gov routes should not make any changes and will not be impacted by this update.

For applications operating under *.fr.cloud.gov routes, a replacement route under *.app.cloud.gov should be created. All traffic including browser, API, and CDN should be reconfigured to point at the new endpoint URL.

Create and map a new route using the *.app.cloud.gov domain with the following command:
$ cf map-route $APP_NAME app.cloud.gov

If you need to specify a host name, path, and/or a port, you can do so with additional options. Please refer to the Cloud Foundry documentation on mapping routes.

Once the new route is configured for any of your affected applications, remove the old route in each organization and space with the following command:
$ cf delete-route fr.cloud.gov

For more information, please refer to the Cloud Foundry documentation on deleting routes.

Traffic that is currently routed through *.fr.cloud.gov must be reconfigured by December 3, 2020 to avoid experiencing downtime from enhanced security configurations.

If you have any questions, please contact support@cloud.gov.
Posted on Aug 3, 12:25 EDT
Past Incidents
Oct 28, 2020

Unresolved incident: Reported log system degradation.

Oct 27, 2020

No incidents reported.

Oct 26, 2020

No incidents reported.

Oct 25, 2020

No incidents reported.

Oct 24, 2020

No incidents reported.

Oct 23, 2020

No incidents reported.

Oct 22, 2020

No incidents reported.

Oct 21, 2020

No incidents reported.

Oct 20, 2020

No incidents reported.

Oct 19, 2020

No incidents reported.

Oct 18, 2020

No incidents reported.

Oct 17, 2020

No incidents reported.

Oct 16, 2020

No incidents reported.

Oct 15, 2020

No incidents reported.

Oct 14, 2020

No incidents reported.