Pulsetic can detect an outage before the provider officially reports it.
98 incidents on record since Aug 2025
Last updated: 2 min ago · 0 user reports (24h)
MAJOR · IDENTIFIED
Connectivity disruption for AWS Bahrain (me-south-1)
Started 7 months ago · Mar 2, 2026 · 6:23 AM UTC
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.
Click an issue to upvote it and help us better indicate the service status.
Service outage0
Degraded performance0
Error messages0
Timeouts / no response0
Authentication issues0
Network / connectivity issues0
Feature not working0
API errors0
Billing or usage issues0
Other0
Have a different problem?
Issue breakdown
0 total votes
Distribution of reported issues over the last 24 hours.
Service outage0%
Degraded performance0%
Error messages0%
Timeouts / no response0%
Authentication issues0%
Network / connectivity issues0%
Feature not working0%
API errors0%
Billing or usage issues0%
Other0%
90-Day Health Summary
Total Incidents
23
Jul 30 to Oct 28, 2026
Major / Critical
22
96% of the total
Minor Incidents
1
Avg. 0.0 per day
Median Resolution
4h 47m
P95: 181h 45m
Across all 4,379 services Pulsetic tracks, the incidents their status pages reported over the last 12 months had a median resolution time of 2h 4m, and 35% were rated major or critical by the provider. These numbers are calculated separately from the 90-day figures for Elastic above.
Check the status badge at the top of this page for the current status. Pulsetic follows the official status page and cross-references it with user reports to give you the most accurate picture.
How often does Elastic go down?
Based on our 90-day data, we've recorded 23 incidents, of which 22 were major or critical. The median resolution time is 4h 47m.
How are outages detected?
Pulsetic follows the official status page and records the incidents the provider posts there. Crowdsourced user reports and Pulsetic's own synthetic checks add an early warning, which can surface an issue before the official status page mentions it.
Is it down for everyone or just me?
The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.
What does "never acknowledged" mean?
"Never acknowledged" means Pulsetic recorded a service disruption from user reports and its own checks, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.
Get an email when Elastic opens, updates or resolves an incident.
Add it as a dependency monitor. The Free plan includes one. See how it works