Skip to content

Elastic status · elastic.co

Is Elastic Down Today?

Search and observability platform.

Cloudelastic.co
Report an issue

Partially — some Elastic services are down

elastic.co is experiencing a partial outage. Some features or regions may be affected while others still work. The latest automated check was run 2026-08-14 17:17 UTC from primary location.

Current status
Partial outage

Current issue started 1h 30m ago

Last check
Checked every 10 minutes

Latest 2026-08-14 17:17 UTC · Primary location

Last 24 hours
50.000%

3 incidents, 2d 7h down

Official status
Partial outage
Our check
Operational
Active incident
Elasticsearch 9.5.1: false-positive matches in certain boolean queries
Last outage
2026-08-14
Response time
440 ms
User reports
Normal

None today

Elastic live status

644 of 661 operational · 17 with issues

  • APM connectivity: AWS me-south-1Major outage
  • AWS Bahrain (me-south-1)Major outage
  • AWS EC2 Health: me-south-1Major outage
  • AWS Infrastructure health: me-south-1Major outage
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1Major outage
  • Elasticsearch connectivity: AWS me-south-1Major outage
  • Kibana connectivity: AWS me-south-1Major outage
  • Snapshot Storage Infrastructure (S3): me-south-1Major outage
  • APM connectivity: Azure azure-westus2Possible issues
  • Azure - Washington (azure-westus2)Possible issues
  • Azure Infrastructure HealthPossible issues
  • Azure Infrastructure health: azure-westus2Possible issues
  • Azure Washington (azure-westus2)Possible issues
  • Elasticsearch connectivity: Azure azure-westus2Possible issues
  • Elasticsearch connectivity: GCP asia-south1Possible issues
  • GCP Mumbai (asia-south1)Possible issues
  • Kibana connectivity: Azure azure-westus2Possible issues
  • APM connectivity: AWS af-south-1Operational
  • APM connectivity: AWS ap-east-1Operational
  • APM connectivity: AWS ap-northeast-1Operational
  • APM connectivity: AWS ap-northeast-2Operational
  • APM connectivity: AWS ap-south-1Operational
  • APM connectivity: AWS ap-southeast-1Operational
  • APM connectivity: AWS ap-southeast-2Operational
  • APM connectivity: AWS ca-central-1Operational
  • APM connectivity: AWS eu-central-1Operational
  • APM connectivity: AWS eu-central-2Operational
  • APM connectivity: AWS eu-north-1Operational
  • APM connectivity: AWS eu-south-1Operational
  • APM connectivity: AWS eu-west-1Operational
  • APM connectivity: AWS eu-west-2Operational
  • APM connectivity: AWS eu-west-3Operational
  • APM connectivity: AWS sa-east-1Operational
  • APM connectivity: AWS us-east-1Operational
  • APM connectivity: AWS us-east-2Operational
  • APM connectivity: AWS us-west-1Operational
  • APM connectivity: AWS us-west-2Operational
  • APM connectivity: Azure azure-australiaeastOperational
  • APM connectivity: Azure azure-brazilsouthOperational
  • APM connectivity: Azure azure-canadacentralOperational
  • APM connectivity: Azure azure-centralindiaOperational
  • APM connectivity: Azure azure-centralusOperational
  • APM connectivity: Azure azure-eastusOperational
  • APM connectivity: Azure azure-eastus2Operational
  • APM connectivity: Azure azure-francecentralOperational
  • APM connectivity: Azure azure-japaneastOperational
  • APM connectivity: Azure azure-northeuropeOperational
  • APM connectivity: Azure azure-southafricanorthOperational
  • APM connectivity: Azure azure-southcentralusOperational
  • APM connectivity: Azure azure-southeastasiaOperational
  • APM connectivity: Azure azure-uksouthOperational
  • APM connectivity: Azure azure-westeuropeOperational
  • APM connectivity: GCP asia-east1Operational
  • APM connectivity: GCP asia-northeast1Operational
  • APM connectivity: GCP asia-northeast3Operational
  • APM connectivity: GCP asia-south1Operational
  • APM connectivity: GCP asia-southeast1Operational
  • APM connectivity: GCP asia-southeast2Operational
  • APM connectivity: GCP australia-southeast1Operational
  • APM connectivity: GCP europe-north1Operational
  • APM connectivity: GCP europe-west1Operational
  • APM connectivity: GCP europe-west2Operational
  • APM connectivity: GCP europe-west3Operational
  • APM connectivity: GCP europe-west4Operational
  • APM connectivity: GCP europe-west9Operational
  • APM connectivity: GCP me-west1Operational
  • APM connectivity: GCP northamerica-northeast1Operational
  • APM connectivity: GCP southamerica-east1Operational
  • APM connectivity: GCP us-central1Operational
  • APM connectivity: GCP us-east1Operational
  • APM connectivity: GCP us-east4Operational
  • APM connectivity: GCP us-west1Operational
  • App Search connectivity: AWS ap-southeast-1Operational
  • App Search connectivity: Azure azure-southeastasiaOperational
  • Asia/Pacific - Australia EastOperational
  • Asia/Pacific - IndiaOperational
  • Asia/Pacific - JapanOperational
  • Asia/Pacific - SingaporeOperational
  • AutoOpsOperational
  • AWS - Central (ca-central-1)Operational
  • AWS - Frankfurt (eu-central-1)Operational
  • AWS - Ireland (eu-west-1)Operational
  • AWS - London (eu-west-2)Operational
  • AWS - N.Virginia (us-east-1)Operational
  • AWS - Ohio (us-east-2)Operational
  • AWS - Oregon (us-west-2)Operational
  • AWS - Singapore (ap-southeast-1)Operational
  • AWS - Sydney (ap-southeast-2)Operational
  • AWS - Tokyo (ap-northeast-1)Operational
  • AWS Cape Town (af-south-1)Operational
  • AWS Central (ca-central-1)Operational
  • AWS EC2 Health: af-south-1Operational
  • AWS EC2 Health: ap-northeast-1Operational
  • AWS EC2 Health: ap-south-1Operational
  • AWS EC2 Health: ap-southeast-1Operational
  • AWS EC2 Health: ap-southeast-2Operational
  • AWS EC2 Health: ca-central-1Operational
  • AWS EC2 Health: eu-central-1Operational
  • AWS EC2 Health: eu-central-2Operational
  • AWS EC2 Health: eu-north-1Operational
  • AWS EC2 Health: eu-south-1Operational
  • AWS EC2 Health: eu-west-1Operational
  • AWS EC2 Health: eu-west-2Operational
  • AWS EC2 Health: sa-east-1Operational
  • AWS EC2 Health: us-east-1Operational
  • AWS EC2 Health: us-east-2Operational
  • AWS EC2 Health: us-west-1Operational
  • AWS EC2 Health: us-west-2Operational
  • AWS ec2-ap-east-1Operational
  • AWS ec2-ap-northeast-2Operational
  • AWS Frankfurt (eu-central-1)Operational
  • AWS Hong Kong (ap-east-1)Operational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure HealthOperational
  • AWS Infrastructure health: af-south-1Operational
  • AWS Infrastructure health: ap-east-1Operational
  • AWS Infrastructure health: ap-northeast-1Operational
  • AWS Infrastructure health: ap-northeast-2Operational
  • AWS Infrastructure health: ap-south-1Operational
  • AWS Infrastructure health: ap-southeast-2Operational
  • AWS Infrastructure health: ca-central-1Operational
  • AWS Infrastructure health: eu-central-1Operational
  • AWS Infrastructure health: eu-central-2Operational
  • AWS Infrastructure health: eu-north-1Operational
  • AWS Infrastructure health: eu-south-1Operational
  • AWS Infrastructure health: eu-west-1Operational
  • AWS Infrastructure health: eu-west-2Operational
  • AWS Infrastructure health: eu-west-3Operational
  • AWS Infrastructure health: sa-east-1Operational
  • AWS Infrastructure health: us-east-1Operational
  • AWS Infrastructure health: us-east-2Operational
  • AWS Infrastructure health: us-west-1Operational
  • AWS Infrastructure health: us-west-2Operational
  • AWS Ireland (eu-west-1)Operational
  • AWS London (eu-west-2)Operational
  • AWS MarketplaceOperational
  • AWS Milan (eu-south-1)Operational
  • AWS Mumbai (ap-south-1)Operational
  • AWS N. California (us-west-1)Operational
  • AWS N. Virginia (us-east-1)Operational
  • AWS Ohio (us-east-2)Operational
  • AWS Oregon (us-west-2)Operational
  • AWS Paris (eu-west-3)Operational
  • AWS s3-ap-east-1Operational
  • AWS s3-ap-northeast-2Operational
  • AWS São Paulo (sa-east-1)Operational
  • AWS Seoul (ap-northeast-2)Operational
  • AWS Singapore (ap-southeast-1)Operational
  • AWS Stockholm (eu-north-1)Operational
  • AWS Sydney (ap-southeast-2)Operational
  • AWS Tokyo (ap-northeast-1)Operational
  • AWS Zurich (eu-central-2)Operational
  • Azure - Dubai (uaenorth)Operational
  • Azure - Ireland (azure-northeurope)Operational
  • Azure - New South Wales (azure-australiaeast)Operational
  • Azure - São Paulo (azure-brazilsouth)Operational
  • Azure - Sweden (azure-swedencentral)Operational
  • Azure - Virginia (azure-eastus)Operational
  • Azure France (azure-francecentral)Operational
  • Azure Infrastructure HealthOperational
  • Azure Infrastructure HealthOperational
  • Azure Infrastructure HealthOperational
  • Azure Infrastructure HealthOperational
  • Azure Infrastructure HealthOperational
  • Azure Infrastructure HealthOperational
  • Azure Infrastructure health: azure-australiaeastOperational
  • Azure Infrastructure health: azure-brazilsouthOperational
  • Azure Infrastructure health: azure-canadacentralOperational
  • Azure Infrastructure health: azure-centralindiaOperational
  • Azure Infrastructure health: azure-centralusOperational
  • Azure Infrastructure health: azure-eastusOperational
  • Azure Infrastructure health: azure-eastus2Operational
  • Azure Infrastructure health: azure-francecentralOperational
  • Azure Infrastructure health: azure-japaneastOperational
  • Azure Infrastructure health: azure-northeuropeOperational
  • Azure Infrastructure health: azure-southafricanorthOperational
  • Azure Infrastructure health: azure-southcentralusOperational
  • Azure Infrastructure health: azure-uksouthOperational
  • Azure Infrastructure health: azure-westeuropeOperational
  • Azure Iowa (azure-centralus)Operational
  • Azure Ireland (azure-northeurope)Operational
  • Azure johannesburg (azure-southafricanorth)Operational
  • Azure London (azure-uksouth)Operational
  • Azure MarketplaceOperational
  • Azure Netherlands (azure-westeurope)Operational
  • Azure New South Wales (azure-australiaeast)Operational
  • Azure Pune (azure-centralindia)Operational
  • Azure São Paulo (azure-brazilsouth)Operational
  • Azure Singapore (azure-southeastasia)Operational
  • Azure Texas (azure-southcentralus)Operational
  • Azure Tokyo (azure-japaneast)Operational
  • Azure Toronto (azure-canadacentral)Operational
  • Azure Virginia (azure-eastus)Operational
  • Azure Virginia (azure-eastus2)Operational
  • Cloud Connect HealthOperational
  • Cloud consoleOperational
  • CSP Infrastructure Health: GCP us-west1Operational
  • Deployment hosts: AWS ap-southeast-1Operational
  • Deployment hosts: Azure azure-southeastasiaOperational
  • Deployment logging: AWS ap-southeast-1Operational
  • Deployment logging: Azure azure-southeastasiaOperational
  • Deployment metrics: AWS ap-southeast-1Operational
  • Deployment metrics: Azure azure-southeastasiaOperational
  • Deployment orchestration (Create/Edit/Restart/Delete)Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS af-south-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS ap-east-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS ap-northeast-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS ap-northeast-2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS ap-south-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS ap-southeast-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS ap-southeast-2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS ca-central-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-central-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-central-2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-north-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-south-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-west-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-west-2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-west-3Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS sa-east-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS us-east-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS us-east-2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS us-west-1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): AWS us-west-2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-australiaeastOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-brazilsouthOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-canadacentralOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-centralindiaOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-centralusOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastusOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-francecentralOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-japaneastOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-northeuropeOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-southafricanorthOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-southcentralusOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-southeastasiaOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-uksouthOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westeuropeOperational
  • Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP asia-east1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP asia-northeast1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP asia-northeast3Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP asia-south1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP asia-southeast1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP asia-southeast2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP australia-southeast1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-north1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west2Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west3Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west4Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west9Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP me-west1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP northamerica-northeast1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP southamerica-east1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP us-central1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP us-east1Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP us-east4Operational
  • Deployment orchestration (Create/Edit/Restart/Delete): GCP us-west1Operational
  • Deployment snapshots: AWS ap-southeast-1Operational
  • Deployment snapshots: Azure azure-southeastasiaOperational
  • EC2 Health: AWS ap-northeast-2Operational
  • EC2 Health: AWS eu-west-3Operational
  • Elastic Cloud ConnectOperational
  • Elastic Cloud HostedOperational
  • Elastic Cloud ServerlessOperational
  • Elastic Docker RegistryOperational
  • Elastic DownloadsOperational
  • Elastic Inference ServiceOperational
  • Elastic Maps ServiceOperational
  • Elastic website - elastic.coOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch AvailabilityOperational
  • Elasticsearch connectivity: AWS af-south-1Operational
  • Elasticsearch connectivity: AWS ap-east-1Operational
  • Elasticsearch connectivity: AWS ap-northeast-1Operational
  • Elasticsearch connectivity: AWS ap-northeast-2Operational
  • Elasticsearch connectivity: AWS ap-south-1Operational
  • Elasticsearch connectivity: AWS ap-southeast-1Operational
  • Elasticsearch connectivity: AWS ap-southeast-2Operational
  • Elasticsearch connectivity: AWS ca-central-1Operational
  • Elasticsearch connectivity: AWS eu-central-1Operational
  • Elasticsearch connectivity: AWS eu-central-2Operational
  • Elasticsearch connectivity: AWS eu-north-1Operational
  • Elasticsearch connectivity: AWS eu-south-1Operational
  • Elasticsearch connectivity: AWS eu-west-1Operational
  • Elasticsearch connectivity: AWS eu-west-2Operational
  • Elasticsearch connectivity: AWS eu-west-3Operational
  • Elasticsearch connectivity: AWS sa-east-1Operational
  • Elasticsearch connectivity: AWS us-east-1Operational
  • Elasticsearch connectivity: AWS us-east-2Operational
  • Elasticsearch connectivity: AWS us-west-1Operational
  • Elasticsearch connectivity: AWS us-west-2Operational
  • Elasticsearch connectivity: Azure azure-australiaeastOperational
  • Elasticsearch connectivity: Azure azure-brazilsouthOperational
  • Elasticsearch connectivity: Azure azure-canadacentralOperational
  • Elasticsearch connectivity: Azure azure-centralindiaOperational
  • Elasticsearch connectivity: Azure azure-centralusOperational
  • Elasticsearch connectivity: Azure azure-eastusOperational
  • Elasticsearch connectivity: Azure azure-eastus2Operational
  • Elasticsearch connectivity: Azure azure-francecentralOperational
  • Elasticsearch connectivity: Azure azure-japaneastOperational
  • Elasticsearch connectivity: Azure azure-northeuropeOperational
  • Elasticsearch connectivity: Azure azure-southafricanorthOperational
  • Elasticsearch connectivity: Azure azure-southcentralusOperational
  • Elasticsearch connectivity: Azure azure-southeastasiaOperational
  • Elasticsearch connectivity: Azure azure-uksouthOperational
  • Elasticsearch connectivity: Azure azure-westeuropeOperational
  • Elasticsearch connectivity: GCP asia-east1Operational
  • Elasticsearch connectivity: GCP asia-northeast1Operational
  • Elasticsearch connectivity: GCP asia-northeast3Operational
  • Elasticsearch connectivity: GCP asia-southeast1Operational
  • Elasticsearch connectivity: GCP asia-southeast2Operational
  • Elasticsearch connectivity: GCP australia-southeast1Operational
  • Elasticsearch connectivity: GCP europe-north1Operational
  • Elasticsearch connectivity: GCP europe-west1Operational
  • Elasticsearch connectivity: GCP europe-west2Operational
  • Elasticsearch connectivity: GCP europe-west3Operational
  • Elasticsearch connectivity: GCP europe-west4Operational
  • Elasticsearch connectivity: GCP europe-west9Operational
  • Elasticsearch connectivity: GCP me-west1Operational
  • Elasticsearch connectivity: GCP northamerica-northeast1Operational
  • Elasticsearch connectivity: GCP southamerica-east1Operational
  • Elasticsearch connectivity: GCP us-central1Operational
  • Elasticsearch connectivity: GCP us-east1Operational
  • Elasticsearch connectivity: GCP us-east4Operational
  • Elasticsearch connectivity: GCP us-west1Operational
  • Email notificationsOperational
  • Enterprise Search connectivity: AWS ap-southeast-1Operational
  • Enterprise Search connectivity: Azure azure-southeastasiaOperational
  • Europe - GermanyOperational
  • Europe - United KingdomOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • Fleet AvailabilityOperational
  • GCP - Belgium (europe-west1)Operational
  • GCP - Frankfurt (europe-west3)Operational
  • GCP - Iowa (us-central1)Operational
  • GCP - London (europe-west2)Operational
  • GCP - Madrid (europe-southwest1)Operational
  • GCP - Mumbai (asia-south1)Operational
  • GCP - N. Virginia (us-east4)Operational
  • GCP - Netherlands (europe-west4)Operational
  • GCP - Oregon (us-west1)Operational
  • GCP - Singapore (asia-southeast1)Operational
  • GCP - South Carolina (us-east1)Operational
  • GCP - Tokyo (asia-northeast1)Operational
  • GCP Belgium (europe-west1)Operational
  • GCP Finland (europe-north1)Operational
  • GCP Frankfurt (europe-west3)Operational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure HealthOperational
  • GCP Infrastructure health: asia-east1Operational
  • GCP Infrastructure health: asia-northeast1Operational
  • GCP Infrastructure health: asia-northeast3Operational
  • GCP Infrastructure health: asia-south1Operational
  • GCP Infrastructure health: asia-southeast1Operational
  • GCP Infrastructure health: asia-southeast2Operational
  • GCP Infrastructure health: australia-southeast1Operational
  • GCP Infrastructure health: europe-north1Operational
  • GCP Infrastructure health: europe-west1Operational
  • GCP Infrastructure health: europe-west2Operational
  • GCP Infrastructure health: europe-west3Operational
  • GCP Infrastructure health: europe-west4Operational
  • GCP Infrastructure health: europe-west9Operational
  • GCP Infrastructure health: me-west1Operational
  • GCP Infrastructure health: northamerica-northeast1Operational
  • GCP Infrastructure health: southamerica-east1Operational
  • GCP Infrastructure health: us-central1Operational
  • GCP Infrastructure health: us-east1Operational
  • GCP Infrastructure health: us-east4Operational
  • GCP Infrastructure Health: us-east4Operational
  • GCP Infrastructure health: us-west1Operational
  • GCP Iowa (us-central1)Operational
  • GCP Jakarta (asia-southeast2)Operational
  • GCP London (europe-west2)Operational
  • GCP MarketplaceOperational
  • GCP Montreal (northamerica-northeast1)Operational
  • GCP N. Virginia (us-east4)Operational
  • GCP Netherlands (europe-west4)Operational
  • GCP Oregon (us-west1)Operational
  • GCP Paris (europe-west9)Operational
  • GCP São Paulo (southamerica-east1)Operational
  • GCP Seoul (asia-northeast3)Operational
  • GCP Singapore (asia-southeast1)Operational
  • GCP South Carolina (us-east1)Operational
  • GCP Sydney (australia-southeast1)Operational
  • GCP Taiwan (asia-east1)Operational
  • GCP Tel Aviv (me-west1)Operational
  • GCP Tokyo (asia-northeast1)Operational
  • Global servicesOperational
  • Global Services - Cloud ConnectOperational
  • HerokuOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana AvailabilityOperational
  • Kibana connectivity: AWS af-south-1Operational
  • Kibana connectivity: AWS ap-east-1Operational
  • Kibana connectivity: AWS ap-northeast-1Operational
  • Kibana connectivity: AWS ap-northeast-2Operational
  • Kibana connectivity: AWS ap-south-1Operational
  • Kibana connectivity: AWS ap-southeast-1Operational
  • Kibana connectivity: AWS ap-southeast-2Operational
  • Kibana connectivity: AWS ap-southeast-2Operational
  • Kibana connectivity: AWS ca-central-1Operational
  • Kibana connectivity: AWS eu-central-1Operational
  • Kibana connectivity: AWS eu-central-2Operational
  • Kibana connectivity: AWS eu-north-1Operational
  • Kibana connectivity: AWS eu-south-1Operational
  • Kibana connectivity: AWS eu-west-1Operational
  • Kibana connectivity: AWS eu-west-2Operational
  • Kibana connectivity: AWS eu-west-3Operational
  • Kibana connectivity: AWS sa-east-1Operational
  • Kibana connectivity: AWS us-east-1Operational
  • Kibana connectivity: AWS us-east-2Operational
  • Kibana connectivity: AWS us-west-1Operational
  • Kibana connectivity: AWS us-west-2Operational
  • Kibana connectivity: Azure azure-australiaeastOperational
  • Kibana connectivity: Azure azure-brazilsouthOperational
  • Kibana connectivity: Azure azure-canadacentralOperational
  • Kibana connectivity: Azure azure-centralindiaOperational
  • Kibana connectivity: Azure azure-centralusOperational
  • Kibana connectivity: Azure azure-eastusOperational
  • Kibana connectivity: Azure azure-eastus2Operational
  • Kibana connectivity: Azure azure-francecentralOperational
  • Kibana connectivity: Azure azure-japaneastOperational
  • Kibana connectivity: Azure azure-northeuropeOperational
  • Kibana connectivity: Azure azure-southafricanorthOperational
  • Kibana connectivity: Azure azure-southcentralusOperational
  • Kibana connectivity: Azure azure-southeastasiaOperational
  • Kibana connectivity: Azure azure-uksouthOperational
  • Kibana connectivity: Azure azure-westeuropeOperational
  • Kibana connectivity: GCP asia-east1Operational
  • Kibana connectivity: GCP asia-northeast1Operational
  • Kibana connectivity: GCP asia-northeast3Operational
  • Kibana connectivity: GCP asia-south1Operational
  • Kibana connectivity: GCP asia-southeast1Operational
  • Kibana connectivity: GCP asia-southeast2Operational
  • Kibana connectivity: GCP australia-southeast1Operational
  • Kibana connectivity: GCP europe-north1Operational
  • Kibana connectivity: GCP europe-west1Operational
  • Kibana connectivity: GCP europe-west2Operational
  • Kibana connectivity: GCP europe-west3Operational
  • Kibana connectivity: GCP europe-west4Operational
  • Kibana connectivity: GCP europe-west9Operational
  • Kibana connectivity: GCP me-west1Operational
  • Kibana connectivity: GCP northamerica-northeast1Operational
  • Kibana connectivity: GCP southamerica-east1Operational
  • Kibana connectivity: GCP us-central1Operational
  • Kibana connectivity: GCP us-east1Operational
  • Kibana connectivity: GCP us-east4Operational
  • Kibana connectivity: GCP us-west1Operational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed Intake Service AvailabilityOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • Managed OTLP EndpointOperational
  • North America - Canada EastOperational
  • North America - US EastOperational
  • North America - US WestOperational
  • Project orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Serverless - Project Orchestration (Create/Edit/Restart/Delete)Operational
  • Snapshot Storage Infrastructure (S3): ap-south-1Operational
  • Snapshot Storage Infrastructure (S3): af-south-1Operational
  • Snapshot Storage Infrastructure (S3): ap-northeast-1Operational
  • Snapshot Storage Infrastructure (S3): ap-southeast-1Operational
  • Snapshot Storage Infrastructure (S3): ap-southeast-2Operational
  • Snapshot Storage Infrastructure (S3): AWS ap-northeast-2Operational
  • Snapshot Storage Infrastructure (S3): AWS eu-west-3Operational
  • Snapshot Storage Infrastructure (S3): ca-central-1Operational
  • Snapshot Storage Infrastructure (S3): eu-central-1Operational
  • Snapshot Storage Infrastructure (S3): eu-central-2Operational
  • Snapshot Storage Infrastructure (S3): eu-north-1Operational
  • Snapshot Storage Infrastructure (S3): eu-south-1Operational
  • Snapshot Storage Infrastructure (S3): eu-west-1Operational
  • Snapshot Storage Infrastructure (S3): eu-west-2Operational
  • Snapshot Storage Infrastructure (S3): sa-east-1Operational
  • Snapshot Storage Infrastructure (S3): us-east-1Operational
  • Snapshot Storage Infrastructure (S3): us-east-2Operational
  • Snapshot Storage Infrastructure (S3): us-west-1Operational
  • South America - BrazilOperational
  • Support portalOperational
  • Synthetics - Global Managed Testing InfrastructureOperational

Current incidents

  • Elasticsearch 9.5.1: false-positive matches in certain boolean queries

    IdentifiedPartial outage

    Elasticsearch 9.5.1 contains a known issue where boolean queries containing a must, filter, or should clause using a multi-value terms query, alongside a must_not clause on fields with disabled indexing, can still return false-positive matches. While the patch in 9.5.1 (https://github.com/elastic/elasticsearch/pull/155936) resolved the bulk-scorer defect for term and range query paths; multi-v...

    Started · 2026-08-14 09:22 UTC

    Official incident update

    1. 2026-08-14 09:22 UTCIdentified

      Elasticsearch 9.5.1 contains a known issue where boolean queries containing a must, filter, or should clause using a multi-value terms query, alongside a must_not clause on fields with disabled indexing, can still return false-positive matches. While the patch in 9.5.1 (https://github.com/elastic/elasticsearch/pull/155936) resolved the bulk-scorer defect for term and range query paths; multi-v...

  • Increased error rates for microsoft-multilingual-e5-large

    MonitoringPartial outage

    Unfortunately, we can no longer support the E5 Multilingual Large model on the Elastic Inference Service due to continued upstream provider issues. Any customers requiring this model should set up custom inference endpoints using their own API keys.

    Started · 2026-08-13 08:32 UTC

    Official incident update

    1. 2026-08-13 08:32 UTCInvestigating

      We are seeing elevated error rates from the upstream provider for the microsoft-multilingual-e5-large embedding model. Search embedding requests to this model may fail. We are investigating

    2. 2026-08-13 14:45 UTCInvestigating

      We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.

    3. 2026-08-13 18:26 UTCMonitoring

      Unfortunately, we can no longer support the E5 Multilingual Large model on the Elastic Inference Service due to continued upstream provider issues. Any customers requiring this model should set up custom inference endpoints using their own API keys.

  • Connectivity disruption for AWS Bahrain (me-south-1)

    IdentifiedPartial outage

    Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or...

    Started · 2026-03-02 06:23 UTC

    Official incident update

    1. 2026-03-02 06:23 UTCIdentified

      We are aware of connectivity and power issues affecting AWS Bahrain (me-south-1) due to localized power issues. We are awaiting further updates from AWS and will update here once we have more information.

    2. 2026-03-09 15:01 UTCIdentified

      This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach ou...

    3. 2026-03-16 19:46 UTCIdentified

      This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach ou...

    4. 2026-03-23 16:20 UTCIdentified

      There are no new updates. This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, pl...

    5. 2026-03-24 09:29 UTCIdentified

      We have identified a further potential disruption to our services hosted in the AWS Bahrain (me-south-1) region. We are working to determine the scope of this impact, and have engaged with AWS as the providers in this investigation. Further updates will be posted within the hour, or when we have further information.

    6. 2026-03-24 11:09 UTCIdentified

      This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach ou...

    7. 2026-04-02 00:00 UTCIdentified

      As this incident remains ongoing with no recovery timeline provided by AWS, we have removed AWS Bahrain (me-south-1) from the available region selection on cloud.elastic.co. The region is currently unavailable for the creation of new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS connectivity disruption. Customers in this region should continue to wo...

    8. 2026-04-20 17:46 UTCIdentified

      Update — This incident remains ongoing. AWS Bahrain (me-south-1) has been removed from the available region selection on cloud.elastic.co and is unavailable for new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS infrastructure disruption. AWS has not provided a recovery timeline for the region. Customers should continue to assume the region is unava...

    9. 2026-05-18 16:33 UTCIdentified

      Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or...

    10. 2026-06-01 17:13 UTCIdentified

      Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or...

    11. 2026-06-15 19:27 UTCIdentified

      Update — This incident is still ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support....

    12. 2026-06-29 17:14 UTCIdentified

      Update — This incident is still ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support....

    13. 2026-07-13 16:42 UTCIdentified

      Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or...

    14. 2026-08-10 16:46 UTCIdentified

      Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or...

Response time

Latest 327 ms

Loading response-time chart…

Uptime

Availability from independent checks, with recorded incidents and downtime in each window.

Today

50.000%

3 incidents, 1d 18h down

Last 7 days

50.000%

3 incidents, 8d 16h down

Last 30 days

50.000%

3 incidents, 31d 16h down

Last 365 days

50.000%

3 incidents, 167d 3h down

Latest Elastic incidents

Recorded outages with duration and start time.

Last recorded 2026-08-14 09:22 UTC

IncidentDurationStarted

Elasticsearch 9.5.1: false-positive matches in certain boolean queries

Identified
Ongoing2026-08-14 09:22 UTC

Increased error rates for microsoft-multilingual-e5-large

Monitoring
Ongoing2026-08-13 08:32 UTC

Connectivity disruption for AWS Bahrain (me-south-1)

Identified
Ongoing2026-03-02 06:23 UTC

How this status checker works

Who's Down Today monitors Elastic independently of the company that runs it. We send reachability checks from our primary location every 10 minutes and record response time, HTTP errors, and timeouts.

When Elastic publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.

This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.

Frequently asked questions

Is Elastic down right now?

Partially — some Elastic services are down. Who's Down Today currently shows Elastic as partial outage. Check the live status, recent incidents, and response-time chart on this page. If the site works for you, the issue may be regional or limited to some features.

Is Elastic down for everyone or just me?

A confirmed issue on this page means our sources detected a problem, but that does not always mean every user is affected. Some incidents are regional, affect only some features, or appear as slow loading instead of a full outage.

What should I do if elastic.co is up but I still cannot access it?

Try opening elastic.co from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Elastic outage.

How does Who's Down Today check if Elastic is down?

We combine independent HTTP reachability checks with public status information where it exists. When Elastic publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.

What does a Elastic outage mean?

An outage on this page means recorded incidents or failed checks indicated that Elastic was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.

Can this page tell me the root cause of a Elastic outage?

Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to Elastic's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.

How do I report an issue with Elastic?

Use the report form on this page if Elastic looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.