Cloud.gov Outage History

Cloud.gov is up right now

Cloud.gov had 12 outages in the last 2 years totaling 1234h 22m of downtime — averaging 0.5 incidents per month.

There were 12 Cloud.gov outages since August 14, 2025 totaling 1234h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://cloudgov.statuspage.io

Notice May 28, 2026

Intermittent issue accessing logs.fr.cloud.gov

Detected by Pingoru
May 28, 2026, 12:47 PM UTC
Resolved
May 28, 2026, 02:06 PM UTC
Duration
1h 19m
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
  1. 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

  2. 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.

  3. resolved May 28, 2026, 02:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 8, 2026

Cloud.gov Email Ticket Service Outage

Detected by Pingoru
Apr 08, 2026, 05:34 PM UTC
Resolved
Apr 09, 2026, 11:00 AM UTC
Duration
17h 26m
Timeline · 2 updates
  1. 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/

  2. resolved Apr 09, 2026, 11:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 17, 2025

Resolved - Cloudwatch Logs Ingestion Interruption

Detected by Pingoru
Dec 17, 2025, 06:45 AM UTC
Resolved
Dec 17, 2025, 06:45 AM UTC
Duration
—
Timeline · 1 update
  1. 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.

Read the full incident report →

Notice October 1, 2025

Cloud.gov operations during the FY26 appropriations lapse

Detected by Pingoru
Oct 01, 2025, 05:25 PM UTC
Resolved
Nov 18, 2025, 02:18 PM UTC
Duration
47d 20h
Affected: ApplicationsWeb ApplicationBuildsHosted Sites
Timeline · 2 updates
  1. 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].

  2. resolved Nov 18, 2025, 02:18 PM UTC

    This incident has been resolved.

Read the full incident report →