All Systems Operational
Global services
Operational
Support portal
?
Operational
AWS GovCloud US-East (aws-us-gov-east-1)
Operational
Elasticsearch connectivity: AWS aws-us-gov-east-1
Operational
Kibana connectivity: AWS aws-us-gov-east-1
Operational
APM connectivity: AWS aws-us-gov-east-1
Operational
Cloud console
?
Operational
Deployment hosts: AWS aws-us-gov-east-1
?
Operational
Deployment logging: AWS aws-us-gov-east-1
Operational
Deployment metrics: AWS aws-us-gov-east-1
Operational
Deployment orchestration (Create/Edit/Restart/Delete): AWS aws-us-gov-east-1
?
Operational
Deployment snapshots: AWS aws-us-gov-east-1
Operational
Email notifications
?
Operational
Watcher email actions
?
Operational
Elastic Maps Service
?
Operational
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
Enable dual-stack connectivity for deployment endpoints Jul 28, 2025 08:00-10:00 UTC
On July 28 2025, starting at 08:00 UTC, we will enable dual-stack connectivity for our GovCloud (FedRamp Moderate) infrastructure. This means that both IPv4 and IPv6 addresses will be supported for connections to your Elastic services in GovCloud (FedRamp Moderate).
More specifically we will enable dual stack configuration on the Load Balancer that handles connections to GovCloud Endpoints. Essentially this means that DNS for hostnames like mydeployment.kb.us-gov-east-1.aws.elastic-cloud.com or mydeployment.es.us-gov-east-1.aws.elastic-cloud.com will start resolving to both IPv4 (A records) as well as IPv6 (AAAA records). Then any connections towards the deployment, to Elasticsearch, Kibana, Integrations Server, APM, etc will be either on IPv4 or IPv6 depending the IP configuration on your side.
If you operate in a firewalled environment or if you employ Elastic Traffic filters you must update your rule set for IPv6.
Please refer to https://support.elastic.co/knowledge/78755aa9 knowledge article for further information and possible actions.
Posted on Jun 30, 2025 - 12:07 UTC
More specifically we will enable dual stack configuration on the Load Balancer that handles connections to GovCloud Endpoints. Essentially this means that DNS for hostnames like mydeployment.kb.us-gov-east-1.aws.elastic-cloud.com or mydeployment.es.us-gov-east-1.aws.elastic-cloud.com will start resolving to both IPv4 (A records) as well as IPv6 (AAAA records). Then any connections towards the deployment, to Elasticsearch, Kibana, Integrations Server, APM, etc will be either on IPv4 or IPv6 depending the IP configuration on your side.
If you operate in a firewalled environment or if you employ Elastic Traffic filters you must update your rule set for IPv6.
Please refer to https://support.elastic.co/knowledge/78755aa9 knowledge article for further information and possible actions.
Posted on Jun 30, 2025 - 12:07 UTC