Elastic Cloud · Partial Outage
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Elastic status

Elastic Cloud · Atlassian Statuspage
Partial Outage
Atlassian Statuspage reports Partial System Outage.
Cloud services by region
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

Elasticsearch 9.5.1: false-positive matches in certain boolean queries

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-value terms queries utilize a different Lucene query type that was not covered by that fix. Time Series Data Streams (TSDB) and columnar indices/data streams remain affected for this query pattern, as indexing is disabled by default on those fields. Affected terms queries may return false-positive matches (including documents that should have been excluded) and report higher document counts than expected. No error is raised, so queries will appear to complete successfully. What you can do: - If you have not yet upgraded to 9.5.*, we recommend deferring the upgrade until version 9.5.2 is availab

Status identified Impact partial_outage Updated

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

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 email support@elastic.co.

Status identified Impact partial_outage Updated

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
572
Retained
100
Affected retained
13
Projection scope: complete · 100 retained of 572 reported components across 89 source groups · bounded/truncated source projection.
AWS EC2 Health: us-east-1 Group: AWS N. Virginia (us-east-1) Operational
AWS EC2 Health: sa-east-1 Group: AWS São Paulo (sa-east-1) Operational
AWS EC2 Health: us-west-1 Group: AWS N. California (us-west-1) Operational
AWS EC2 Health: eu-west-1 Group: AWS Ireland (eu-west-1) Operational
AWS EC2 Health: ap-southeast-1 Group: AWS Singapore (ap-southeast-1) Operational
AWS EC2 Health: ap-southeast-2 Group: AWS Sydney (ap-southeast-2) Operational
AWS EC2 Health: us-west-2 Group: AWS Oregon (us-west-2) Operational
AWS EC2 Health: eu-central-1 Group: AWS Frankfurt (eu-central-1) Operational
AWS EC2 Health: eu-west-2 Group: AWS London (eu-west-2) Operational
Cloud console Group: Global services Operational
Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west3 Group: GCP Frankfurt (europe-west3) Operational
Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west1 Group: GCP Belgium (europe-west1) Operational
Elasticsearch connectivity: GCP us-east4 Group: GCP N. Virginia (us-east4) Operational
Kibana connectivity: GCP australia-southeast1 Group: GCP Sydney (australia-southeast1) Operational
Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west2 Group: GCP London (europe-west2) Operational
Elasticsearch connectivity: Azure azure-southeastasia Group: Azure Singapore (azure-southeastasia) Operational
Azure Infrastructure health: azure-westeurope Group: Azure Netherlands (azure-westeurope) Operational
Elasticsearch connectivity: Azure azure-westus2 Group: Azure Washington (azure-westus2) Degraded
Elasticsearch connectivity: GCP northamerica-northeast1 Group: GCP Montreal (northamerica-northeast1) Operational
GCP Infrastructure health: asia-south1 Group: GCP Mumbai (asia-south1) Operational
Showing 20 of 100 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Partial Outage
HTTP 200 · 231.66 ms feed latency
Partial Outage
HTTP 200 · 271.11 ms feed latency
Partial Outage
HTTP 200 · 248.04 ms feed latency
Partial Outage
HTTP 200 · 237.68 ms feed latency
Partial Outage
HTTP 200 · 94.2 ms feed latency
Partial Outage
HTTP 200 · 187.86 ms feed latency
Partial Outage
HTTP 200 · 332.24 ms feed latency
Partial Outage
HTTP 200 · 220.98 ms feed latency
Partial Outage
HTTP 200 · 124.31 ms feed latency
Partial Outage
HTTP 200 · 259.41 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
140.01 ms