Elastic Cloud Outage History
Daily status observations, past incidents, and reported issue history for Elastic Cloud.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 0% | 23 | 23 |
| July 2026 | 0% | 31 | 31 |
| June 2026 | 0% | 30 | 30 |
| May 2026 | 0% | 7 | 7 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 25
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Elevated Error Rates Affecting Managed OTLP
Started:
identified
We have identified the root cause of the elevated error rates affecting serverless managed OTLP. A mitigation has been applied and we are monitoring to confirm error rates return to baseline.
Based on our investigation, customer workloads were not affected.
investigating
We are continuing to investigate elevated error rates affecting the managed OTLP on Elastic Cloud Serverless.
We will provide an update within 1 hour.
investigating
We are currently investigating elevated error rates affecting the managed OTLP on Elastic Cloud Serverless.
Our team is actively investigating the root cause.
We will provide an update within 30 minutes.
Issue when creating Serverless projects in Azure eastus region
Started:
Elastic Cloud Serverless
monitoring
We have determined that the issue stems from an upstream problem with Azure's storage component. Upon examination, the impact is limited strictly to new project initialization times, resulting in longer creation times for Serverless projects in the Azure eastus region.
We will provide a further update once the issue has been resolved.
investigating
An issue affecting the creation of new Serverless projects in Azure's eastus region has been identified. Our team is actively investigating to determine the root cause.
We will provide a follow-up status update within the next hour or as soon as the root cause is established, whichever occurs first.
Elasticsearch 9.5.1: false-positive matches in certain boolean queries
Started:
identified
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 Ser...
Increased error rates for microsoft-multilingual-e5-large
Started:
monitoring
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.
investigating
We're seeing some improvement in availability but are continuing to monitor the situation. We will follow up with more information in due course.
investigating
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
Serverless project creation delayed or failing
Started:
monitoring
We've identified and resolved the issue affecting Serverless project creation and modifications. Our fix has been deployed, and all services are operating normally.
Current status:
- Creating and modifying Serverless projects is fully operational
- All systems are performing as expected
We're continuing to monitor closely for any recurrence.
investigating
We're currently investigating an issue affecting Serverless project creation and modifications. You may experience delays or failures when creating new projects or updating existing project settings.
What's affected:
- Creating new Serverless projects
- Modifying project settings in the Cloud UI or over the API
What's not affected:
- Running Serverless projects continue to operate normally
- Existing project workloads are unimpacted
We'll provide an update within 2 hours, or sooner if the ...
investigating
We are investigating failures with Serverless project creation.
Elasticsearch 9.5.0 contains a query-correctness defect
Started:
identified
A patch release containing the fix is in progress and it is expected to be available within the next week. Our recommendation to defer upgrading to 9.5.0 until 9.5.1 is available remains unchanged.
identified
Further investigation confirmed the impact of this issue was limited to boolean queries containing a must, filter, or should clause, along with a must_not clause on unindexed fields. Such queries can return false-positives returning documents that should have been excluded and report higher document counts than expected.
We have identified the root cause, a fix is in progress, and we are preparing a patch release. We will provide a further update by 10:00 UTC August 6.
identified
Elasticsearch 9.5.0 contains a defect that can cause searches to return incorrect results for any index or data stream that disables indexing on a queried field . A query that excludes values using a must_not clause may fail to exclude them when the targeted field has doc values enabled but is not indexed for search. Affected searches can return documents that should have been excluded and report higher document counts than expected, and results may vary between runs of the same query.
No er...
July 2026
Metering issue with Elastic Cloud Hosted Deployments
Started:
investigating
We are still investigating the metering issue impacting a small number of customers.
We'll provide a further update when new information is available.
investigating
We are still investigating the metering issue impacting a small number of customers. We will proactively issue billing corrections where necessary.
We'll provide another update when new information is available.
investigating
We have identified an issue with our metering of Instance Capacity for Hosted Deployments that affects a subset of customers.
We currently believe the impact to be limited to a small number of customers but are still working to identify and correct all occurrences of this issue. We will proactively issue billing corrections where necessary.
AutoOps monitoring data not ingested for subset of deployments
Started:
identified
RESOLVED - Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe.
Note this incident has already been resolved, and is being posted retroactively.
Elastic Cloud - Email MFA Delivery Delays (Gmail)
Started:
monitoring
Delivery delays have been mitigated. We will continue to monitor to ensure delivery remains stable.
investigating
Update: This incident is still ongoing and we are continuing to investigate.
investigating
Update: This incident is still ongoing and we are continuing to investigate.
We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code.
Available Workarounds:
- Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn).
- Authenticate using the "Log in with Google" social login button.
Note: API K...
investigating
We are currently investigating an issue affecting multi-factor authentication (MFA) via email for Elastic Cloud users with Gmail accounts. Affected users may experience long delays or failures when receiving their email MFA code.
Available Workarounds:
- Use an alternative MFA factor if registered (Authenticator App / TOTP or WebAuthn).
- Authenticate using the "Log in with Google" social login button.
Note: API Key access to your projects and deployments remains fully operational.
We are a...
Cloud Console Deployment Errors
Started:
monitoring
The ability to manage Elastic Cloud Hosted deployments via the Cloud Console has been restored
investigating
We are investigating errors with our cloud console affecting access to create, update, delete and view Elastic Cloud Hosted deployments. Our team is actively investigating the cause so that they can mitigate and restore the service.
Regional outage - Elastic Inference Service (EIS)
Started:
monitoring
The issue affecting a subset of customers with EIS in EMEA regions has been mitigated and the service have been restored.
investigating
We have identified continued impact for a subset of affected customers using EIS. Our team is investigating an issue with the previous remediation and is working to ensure all affected environments are fully restored.
Partial outage - Elastic Inference Service (EIS)
Started:
investigating
We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
investigating
We are currently investigating a partial outage affecting the Elastic Inference Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
investigating
We are currently investigating a partial outage affecting the Elastic Integration Service (EIS) for Elastic Cloud customers with deployments in GCP and Azure in EMEA regions.
Internal Monitoring Data Delay
Started:
monitoring
The system has recovered and we are continuing to monitor the situation.
identified
We have identified the issue and implemented a fix. We are seeing signs of system recovery and are continuing to monitor the situation closely.
investigating
We're experiencing a monitoring data delay affecting a limited number of Azure regions. Elastic Cloud's internal metrics for these regions are being ingested more slowly than usual.
What you may notice: Deployment metrics and instance utilization data may not appear in the Elastic Cloud UI for Hosted Deployments and Serverless Projects in affected regions.
What's not affected: Your deployments and projects are running normally. Data ingestion and all functionality remain unimpacted besides la...
June 2026
Issues delivering static assets to products
Started:
identified
We are continuing to work on a fix for this issue.
identified
We have identified an issue with our ability to deliver certain static assets to our products. We have identified and are working to implement a fix.
Issues with creating/updating Deployments in several regions
Started:
monitoring
We have identified and deployed a fix for this issue and are continuing to closely monitor the situation.
identified
We are currently investigating an issue when creating/updating Deployments in several regions.
We've identified the issue and working on applying a fix.
We will provide an update when one is available or within the hour, whichever comes first.
Ingestion issues for Managed OTLP and Managed Intake Service endpoints in the Azure Australia East region
Started:
identified
This incident is ongoing. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.
identified
We are currently experiencing an issue impacting the ability to ingest data into mOTLP and .amp endpoints in the Azure Australia East region. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.
Failure to authenticate to Kibana with SSO
Started:
identified
We have detected an issue with the Kibana authentication flow. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure. A workaround is to access Kibana using the link inside the Elastic Cloud console. We are currently working on a resolution. We will post an update in 30 minutes, or sooner if there is a change in status.
Issue with Kibana authentication flow
Started:
investigating
We are continuing to investigate this issue.
investigating
We have detected an issue with the Kibana authentication flow for both Deployments and Projects. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure.
A workaround is to access Kibana using the link inside the Elastic Cloud console. We are currently working on a resolution.
Our team is currently identifying the root cause to resolve the issue.
We will share another update in the next hour.
Intermittent Elastic Cloud Serverless Availability Issues in AWS us-east-1
Started:
monitoring
This issue has been mitigated, and we are continuing to monitor the situation.
investigating
We are currently investigating an intermittent issue which may cause unavailability of Elastic Cloud Serverless projects or the inability to create new Serverless projects in AWS us-east-1. We will continue to update status as we learn more.
Customers may see delays with creating Azure serverless projects
Started:
monitoring
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable.
We are seeing increased recovery across as we monitor the situation. Services are being restored.
Monitoring is continuing, and we will provide further updates as we progress.
monitoring
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable.
Recovery has started and we will provide further updates as we progress.
investigating
Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable.
We are currently investigating the issue.
Missing Metrics in Cloud Console - Azure North Europe
Started:
investigating
We are seeing some signs of recovery, and have taken action to mitigate the impact and speed up recovery.
Some users will still see seeing missing metrics visualizations in the Cloud console, for deployments in the Azure North Europe region.
We are actively investigating and will provide another update within 1 hour
investigating
Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 1 hour
May 2026
Issue creating new projects in AWS ap-southeast-2
Started:
investigating
We're aware of an issue with creating Serverless projects in the AWS ap-southeast-2 region. The engineering team is investigating the problem. We will post the next update in 2 hours.
Upstream Azure Outage Causing Service Degradation
Started:
monitoring
We continue to monitor the situation which has mostly recovered. A small number of deployments are still not healthy.
Our support team is working on resolving these on a case-by-case basis.
monitoring
Remediation is underway and systems are recovering. We continue to monitor the situation and will post an update in the next 2 hours or earlier.
identified
We continue to remediate the impact of an upstream Azure outage in Azure West US 2 (azure-westus2), limited to availability zone westus2-2.
Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors, degraded performance, or delays when performing deployment operations.
Deployments configured for high availability across multiple availability zones are not expected to be affected.
Our teams remain actively enga...
identified
We continue to respond to an upstream Microsoft Azure outage in Azure West US 2 (azure-westus2), caused by a datacenter power event reported by Azure. Elastic impact remains limited to availability zone westus2-2.
Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors, degraded performance, or delays when performing deployment operations (including create, edit, restart, and delete).
Deployments configured ...
identified
We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region.
We have confirmed that impact to our service is limited to a single availability zone (westus2-2). Customers whose deployments are not configured for high availability may experience intermittent errors, delays, or inability to access certain features.
Deployments configured for high avail...
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region.
We have confirmed that impact to our service is limited to a single availability zone (westus2-2). Customers whose deployments are not configured for high availability may experience intermittent errors, delays, or inability to access certain features.
Deployments configured for high avail...
Missing Metrics in Cloud Console - Azure North Europe
Started:
identified
The problem has been identified and is being stabilized, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.
investigating
Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 1 hour.
AutoOps Login Issues for New Customers
Started:
monitoring
We continue to actively monitor the implemented mitigation actions. All new user logins are functioning as expected. A permanent resolution is scheduled to be implemented early next week. Our next update will be once the resolution actions are complete, or sooner if the situation changes.
monitoring
We have mitigated the issue preventing new Elastic Cloud customers and trial users from accessing AutoOps by restarting a backend service. We are actively monitoring to confirm the fix remains stable and that all new user logins are functioning as expected. We will provide a final update once we have confirmed full resolution.
investigating
We are investigating an issue that prevents new Elastic Cloud customers, including trial users, from accessing AutoOps across all regions.
Impact: New customers and trial accounts are currently unable to access the AutoOps dashboard.
Existing Customers: Service is unaffected. AutoOps continues to function normally for all existing deployments.
Our team is actively working to identify the root cause. We will provide our next update within the next hour or as soon as more information becomes...
Temporarily unavailability of Serverless Projects Functionality
Started:
monitoring
We are aware of issues resulting in temporary unavailability across multiple Serverless projects. From 08:00 UTC to 09:40 UTC on May 11, Search, Ingest and EIS functionality may have been unavailable.
The root cause of this issue has been identified and resolved - we are currently monitoring, and expect no further impact.
Issues with Email Alerts
Started:
monitoring
A solution has been implemented, and email delivery has resumed. We are continuing to track the situation closely and will provide another update once considered resolved.
investigating
We are currently investigating reports that some customers may be facing issues with email alerts.
April 2026
Delayed AutoOps Metrics in AWS us-east-1
Started:
monitoring
This issue has now been resolved and we are continuing to monitor the system.
identified
We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.
Missing Metrics in Cloud Console — US East (us-east-1)
Started:
identified
We are continuing to see signs of stabilization and monitoring as the system recovers, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.
investigating
Our investigation is ongoing. We continue to see early signs of stabilization, but metrics visualizations in the Cloud console remain impacted. We will provide a further update in 1 hour, or when there is a change in status.
investigating
Our investigation is ongoing. Some early signs of stabilisation have been observed, but metrics visualizations in the Cloud console remain impacted. We will provide a further update within 30 minutes.
investigating
Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the us-east-1 (US East) region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 30 minutes.
Elevated Error Rates and Latency — EU West Region
Started:
monitoring
Our monitoring system reports that AWS EU West 3 (Paris) region ingress layer traffic has recovered to normal levels as of 11:36 UTC and our SLO alerts have resolved. We are continuing to monitor and will update once we are confident the issue is fully resolved.
identified
We are continuing to work on a fix for this issue.
identified
We are currently investigating connectivity issues affecting a subset of customers in our AWS EU West 3 (Paris) region. Some requests may be experiencing elevated latency or failures. Our team is actively investigating, and we are working with our cloud infrastructure provider on the underlying issue. Other regions are not affected at this time. We will provide updates as the situation develops.
EIS elevated 5xx error rates for model google-gemini-embedding-001
Started:
investigating
Errors are coming from the provider API (Google). The incident has been escalated to them, and we are still waiting for a response.
investigating
We're seeing elevated 5xx error rates for the Gemini Embedding v1 model in EIS. The following default inference endpoint is affected:
- .google-gemini-embedding-001
We're investigating and will update again in 2 hours or if there's a change in status.
Privatelink hostnames reported by API are incorrect
Started:
identified
We are still working on moving the fix to production as we experienced some testing issues.
identified
We have merged a fix and are working on deploying it to production
identified
A recent change to our Privatelink implementation resulted in the URLs reported by the deployment API being incorrect in some cases, causing connectivity issues for customers who relied on those URLs. We have identified the issue and are working on a fix.
Connection issue to Kibana via the Cloud UI SSO
Started:
investigating
We have rolled out the fix and there should be no more customer impact
investigating
We have identified the issue and are working on a fix. We will update again in 3 hours or earlier.
investigating
We have identified that only PrivateLink customers are impacted and no other Hosted Cloud Deployments should see any issues.
investigating
We are aware of an issue when connecting to Kibana through the Elastic Cloud UI via SAML SSO, impacting hosted Cloud deployments. Our team is actively investigating. We will post an update to this status within the next hour.
Synthetics service may not run on schedule (us-east-4)
Started:
identified
We have identified the problem and are working on a solution. We should have an update within the next 2-3 hours.
investigating
We are investigating an issue in our Synthetics service on us-east-4. Some customer monitor jobs may not run on their expected schedule. We will provide an update in an hour or earlier.
March 2026
Elevated error rates for Claude Sonnet 4.5 EIS inference endpoints
Started:
investigating
We're seeing elevated 5xx error rates for the Claude Sonnet 4.5 model in EIS. The following default inference endpoints are affected:
- .anthropic-claude-4.5-sonnet-chat_completion
- .anthropic-claude-4.5-sonnet-completion
- .gp-llm-v2-chat_completion
- .gp-llm-v2-completion
We're investigating and will update again in 2 hours or if there's a change in status.
AutoOps deployments marked as Inactive in AWS us-east-1 region
Started:
monitoring
We have mitigated the issue, and AutoOps is back to full functionality in the AWS us-east-1 region. We will continue monitoring the signals from the region to ensure AutoOps remains fully functional, and will share another update once the issue is fully resolved.
monitoring
We have identified the issue and applied mitigations to bring AutoOps in the AWS us-east-1 region back to functionality. Customer deployments may still be marked as inactive, and recent metrics may still not be available. We expect AutoOps to return to full functionality within the next hour. We will provide an update when one is available or within the hour, whichever comes first.
investigating
We are currently investigating an outage of AutoOps in AWS us-east-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.
Issue creating new projects in GCP europe-west3
Started:
identified
The engineering team is validating the fix to restore project creation in the GCP europe-west3 region. We will post another update in 2 hours or sooner if needed
identified
We are aware of problems creating new Serverless projects in the GCP europe-west3 region. The engineering team has identified the problem and we are working on mitigating it. We will post the next updated in 2 hours.
Connectivity disruption for AWS Bahrain (me-south-1)
Started:
AWS EC2 Health: me-south-1
Snapshot Storage Infrastructure (S3): me-south-1
Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1
APM connectivity: AWS me-south-1
AWS Infrastructure health: me-south-1
Elasticsearch connectivity: AWS me-south-1
Kibana connectivity: AWS me-south-1
identified
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.
identified
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.
identified
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.elastic.co) or email mailto:mailto:support@elastic.co.
identified
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.elastic.co) or email mailto:support@elastic.co.
identified
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.
identified
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.
identified
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 unavailable for the foreseeable future.
We continue to support impacted customers individually through...
identified
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 work through Elastic support channels.
For assistance, please open a case in our Support portal (http...
identified
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 out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or...
identified
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.
identified
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, please feel free to reach out to Elastic support by either opening a case in our Support portal (http...
identified
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 out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or...
identified
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 out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or...
identified
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.