All Systems Operational

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
Service - Elasticache/Redis Operational
90 days ago
100.0 % uptime
Today
Service - Elasticsearch/OpenSearch 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
100.0 % 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
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Cloud.gov Logs Operational
90 days ago
100.0 % uptime
Today
Application logs - Intake and storage Operational
90 days ago
100.0 % uptime
Today
Application metrics - Intake and storage Operational
90 days ago
100.0 % uptime
Today
Brokered database logs - Intake and storage Operational
90 days ago
100.0 % uptime
Today
Brokered service metrics - Intake and storage Operational
90 days ago
100.0 % uptime
Today
Audit events - Intake and storage 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
Cloud.gov Workshop Operational
90 days ago
100.0 % uptime
Today
User interface Operational
90 days ago
100.0 % uptime
Today
Runner service 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.59 % uptime
Today
GitHub Operational
90 days ago
100.0 % uptime
Today
GitHub Webhooks Operational
90 days ago
99.18 % 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.
Mar 25, 2026

No incidents reported today.

Mar 24, 2026

No incidents reported.

Mar 23, 2026

No incidents reported.

Mar 22, 2026

No incidents reported.

Mar 21, 2026

No incidents reported.

Mar 20, 2026

No incidents reported.

Mar 19, 2026

No incidents reported.

Mar 18, 2026

No incidents reported.

Mar 17, 2026
Resolved - Summary

From March 17, 2026 around 9:30 AM ET to March 19, 2026 around 3:10 PM ET, some application JSON logs were not ingested successfully to Cloud.gov Logs.

Timeline

- March 6, 2026, 10:25 AM ET - Changes were merged to the logging system configuration to make some subfields of application JSON logs searchable and aggregatable
- March 17, 2026, 9:30 AM ET - Changes to JSON log field parsing begin deploying to Cloud.gov Logs system. Some JSON application logs began to fail ingestion at this point
- March 19, 2026, 2:39 PM ET - Automated testing alerts Cloud.gov engineers to ingestion failures in Cloud.gov Logs. Engineers begin to investigate.
- March 19, 2026, 2:59 PM ET - A Cloud.gov engineer determines that updated JSON application log parsing of timestamp fields is causing some logs to fail ingestion and slowing the overall log ingestion rate
- March 19, 2026, 3:06 PM ET - A fix is deployed to change the field type to “string” for JSON log timestamp fields March 19, 2026, 3:10 PM ET - JSON log ingestion errors are resolved and logs are ingesting successfully

Impact

Only JSON application logs that included a “ts” field or a “timestamp” field which could not be properly parsed as a date (e.g. “1.8543923523”) failed to ingest to Cloud.gov Logs during the incident.

While these logs were not ingested to Cloud.gov Logs successfully, they were ingested to offline storage that is not accessible to customers, but can be accessed by the Cloud.gov engineers if necessary.

Resolution

The type of the timestamp field for JSON application logs was changed to “string”, which allows even values that aren’t valid timestamps or dates to be ingested.

Next Steps

The Cloud.gov team will hold a retrospective to further analyze the causes of this incident and how to improve our operations. We will post our findings as a post-mortem to this incident.

Thank you for your patience. If you have any questions, please contact us at support@cloud.gov.

Mar 17, 09:30 EDT
Mar 16, 2026

No incidents reported.

Mar 15, 2026

No incidents reported.

Mar 14, 2026

No incidents reported.

Mar 13, 2026

No incidents reported.

Mar 12, 2026

No incidents reported.

Mar 11, 2026

No incidents reported.