Is cloud.gov down?
No reported issues
From cloudgov.statuspage.io · checked 5 minutes ago · every 5 minutes
An email when it goes down, and when it’s back.
As of 03:31 UTC on 12 November 2026, cloud.gov's status page reports no issues. Its last reported problem was on 11 November 2026: “Partially Degraded Service”, issue, for 30 min from 20:56 UTC.
- Last problem
- 11 Nov · 30 min
- Problems, last 30 days
- 8
- Typical incident
- 35 min
- Longest in 90 days
- 2 h 6 min · 21 Oct
Uptime
cloud.gov, last 30 days
97.07 %
Biggest dip: cloud.gov, 2.1 h of issue on Oct 21.
Incidents
Started in the last 7 days
4
This week Week before
Latest: cloud.gov, issue on Nov 11.
Recovery
Median time back online
40 min
5 of 8 were over within an hour. Each dot is one incident; the dashed line is the median.
Components 36
All online
- Cloud.gov website
- Cloud.gov compliance notification
Cloud.gov customer access 4
parts 
- Dashboard
- Logs front end
- Login
- API
Cloud.gov customer applications 9
parts 
- Applications
- Service Broker - CDN and external domain services
- Service Broker - Cloud.gov credentials
- Service Broker - Elasticsearch/OpenSearch
- Service Broker - Elasticache/Redis
- Service Broker - Relational databases (RDS)
- Service Broker - SES
- Service Broker - S3
- Other Component
Cloud.gov Pages 3
parts 
- Web Application
- Builds
- Hosted Sites
Services Cloud.gov Pages depends on 2
parts 
- GitHub
- GitHub Webhooks
Cloud.gov Logs 5
parts 
- Application logs - Intake and storage
- Application metrics - Intake and storage
- Brokered database logs - Intake and storage
- Brokered service metrics - Intake and storage
- Audit events - Intake and storage
Cloud.gov Workshop 2
parts 
- User interface
- Runner service
Services Cloud.gov depends on 9
parts 
- AWS CloudFront
- AWS elb-us-gov-west-1
- AWS s3-us-gov-west-1
- AWS rds-us-gov-west-1
- AWS ec2-us-gov-west-1
- AWS elasticsearch-us-gov-west-1
- AWS elasticache-us-gov-west-1
- GSA SecureAuth
- GSA Corporate Email
Last 90 days
9 incidents in 48 days tracked · no reported issues 99.4% of the time · typical incident 35 min
Recent incidents
Times in UTC
- Partially Degraded Service 30 min
Issue
- Partially Degraded Service 6 min
Issue
- Partially Degraded Service 25 min
Issue
- Partially Degraded Service and 1 more 1 h 43 min
Issue
- Partially Degraded Service 35 min
Issue
- Partially Degraded Service 45 min
Issue
- Cloud Foundry API (CAPI) V2 - Brownout Window #2 6 h 18 min
Maintenance
- Partially Degraded Service 2 h 6 min
Issue
- Cloud.gov IDP Maintenance 1 h
Maintenance
- Partially Degraded Service 1 h 1 min
Issue
Having issues right now
Paribu Humanity (H) Yatırma ve Çekme İşlemleri
Critical
AWS · Bahrain (me-south-1) Region Availability
Critical
AWS · UAE (me-central-1) Region Availability
Critical
GW Sistemas O componente “SAAS Webtrans” e alguns outros componentes estão Inativos
Critical
Popular services
All servicesWhere this comes from
Stackpulse reads cloud.gov’s official status page at cloudgov.statuspage.io every 5 minutes and keeps 90 days of what changed. We don’t test cloud.gov ourselves, so a problem shows here once cloud.gov reports it.
Stackpulse isn’t affiliated with cloud.gov. Names and logos belong to their owners.
For agents and scripts
The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.