Elastic favicon
Elastic Status elastic.co

Is Elastic down?

We can't confirm the current status of elastic.co right now

Our automated checks for elastic.co have not returned a reliable result for more than 3 days, so we are not showing it as up or down. Check Elastic's official status page and the recent incidents below for the latest information.

The other half

Is it Elastic, or is it you?

This page answers half the question. It tells you about Elastic. It cannot tell you whether your own site is experiencing an incident, and that is the part your users notice. UptimeRobot checks your websites, APIs and servers, and tells you when one of them does.

50 monitors for your own websites. No card.

Current status

Status unavailable

We can't confirm the current status


Last check

Checked every 5 minutes


Last 24 hours

0.000%

Checks on provider website have reported 1 incident, 1d down

Response time

N/A

Average

N/A

Minimum

N/A

Maximum

The response-time chart above shows Elastic's status over time, based on our automated checks. Each point on the chart represents the result of a check run every 5 minutes.

Last 7 days

0.000%

1 incident, 7d down

Last 30 days

0.000%

1 incident, 30d down


Last 365 days

0.001%

1 incident, 4mo, 25d, 1h, 11m, 16s down

Latest incidents

Root cause
Duration

Elastic Cloud: Degraded Performance: Cloud Provisioning Delays
2h 3m

Elastic Cloud: AutoOps node metrics temporarily unavailable in some regions
42m

Elastic Cloud: Elastic Support Portal unavailable
2h 24m

Elastic Cloud: Delayed Metrics in Cloud Console - GCP us-east4
8h 25m

Elastic Cloud: Kibana access restored for UI-assigned Organization Owners on Hosted deployments
21h 1m

Elastic Cloud: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output
7d 13h

Elastic Cloud: Replication bug causing slow recoveries
29d 12h

View 2026 Elastic outage archive →

How our status checker works?

We continuously monitor Elastic from our own infrastructure to give you an objective view of its status. Every every 5 minutes, we send a request to elastic.co from our primary location in the US and verify that the site responds correctly and within a normal time frame.

If the first check fails, we immediately repeat it from a second location to avoid false positives. When that second attempt also fails, we trigger a third confirmation check from a random global location. Only if all three checks confirm a problem, we mark Elastic as having an issue or a major outage.

Frequently asked questions

We can't confirm Elastic's status right now. Our automated checks for elastic.co have not returned a reliable result for more than 3 days, so we are not showing it as up or down.

Check Elastic's official status page and the recent incidents at the top of this page. If you're having trouble reaching elastic.co, the issue may be local to your connection, DNS, VPN, browser, or device.

We can't say for sure right now: our checks for elastic.co have not returned a reliable result for more than 3 days. Elastic's official status page is the best place to confirm whether there is a wider outage.

If others can reach it and you can't, try switching browsers, devices, or networks, and check your DNS or VPN settings.

Try opening elastic.co from another browser, device, or network (e.g., mobile hotspot). You can also disable your VPN, clear DNS cache, 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.

We monitor elastic.co from our own infrastructure. When a check fails, we repeat the test from two other randomly chosen global locations to eliminate false positives. If these checks fail too, we mark Elastic as down.

A Elastic outage means our checks detected that elastic.co was not responding correctly after multiple checks from different global locations. This doesn't always mean every user is affected. Some outages are regional, some affect only certain features, and some appear as slow loading instead of a full failure.

Not exactly. UptimeRobot monitors elastic.co from the outside, so we can detect when something is wrong and show high-level symptoms such as connection timeouts, HTTP errors, or failed responses from specific regions.

However, we don't have visibility into internal systems, so we can't identify the exact root cause (like a failed deployment, database issue, or infrastructure problem).

What we can show you:

  • When the issue started and when it was resolved
  • How long the outage lasted
  • Which regions were affected
  • The type of error observed (for example, timeouts or HTTP status codes like 500 or 404)

For detailed root cause information and official updates, we recommend checking Elastic's official status page.

Yes, UptimeRobot lets you set up your own monitors for elastic.co so you get alerted the moment something goes wrong, and before your users notice. Our free plan includes 50 monitors with 5-minute check intervals. You'll also get details that this public status page doesn't show, such as response headers, response body, region-level results, and a full activity log.

Create a free UptimeRobot account and set up a monitor for elastic.co. You'll receive alerts via email, SMS, Slack, webhooks, and other integrations as soon as we detect an issue, and again when it's resolved. Because we monitor independently from Elastic's own infrastructure, you may be notified even before their official status page acknowledges the issue.

Alternatively, you can check whether Elastic offers notifications on its official status page.

Over the last 5 years, the average resolved outage for Elastic lasted 5d 12h. That average is the mean difference between created_at and resolved_at across 7 resolved incidents we track for this provider.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.