CHYP.ai · ORBIT // Cloudy_Day Security Suite

Databases & data

Major outage Elastic Cloud status

elastic.co · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

Elastic Cloud's status page shows “Major outage” in AWS EC2 Health: me-south-1 and APM connectivity: AWS me-south-1; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet. Amazon Web Services, a provider it may run on (inferred), also reports trouble. Coincidence, not causation.

confidence: medium Vendor: major issue · users: normal · routing: no data · upstream providers: major.

Vendor status vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)

Regions mentioned: AWS EC2 Health: me-south-1, APM connectivity: AWS me-south-1, AWS Infrastructure health: me-south-1

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started263 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the change5 h 42 min

Evidence

  • Official page: Major outage (“Partial System Outage”). evidence confidence: high
  • Vendor stage: resolved on “AutoOps node metrics temporarily unavailable in some regions”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • Amazon Web Services reports an issue. Elastic Cloud may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Elastic Cloud's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.

Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: major issue · users: normal · routing: no data · upstream providers: major. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).

Who depends on whom

Elastic Cloud may run on Amazon Web Services, Google Cloud, Microsoft Azure (inferred). We don't map other services that depend on Elastic Cloud. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Elastic Cloud or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Elastic Cloud. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

AutoOps node metrics temporarily unavailable in some regions

major resolved · started · resolved

3 updates

  1. investigating

    We are investigating reports of missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions. This may appear as a "No data" message on the Nodes view. Cluster health, shard, and deployment data are unaffected, and no data loss has occurred. We will provide an update within the next 2 hours or earlier.

  2. identified

    We've identified the cause of the missing node-level metrics (CPU, memory, disk, thread pools) in affected regions. Cluster health, shard, and deployment data were never affected, and no data loss has occurred. A fix has been validated in one region and is now being rolled out to the remaining affected regions. We'll provide a further update once the rollout is complete.

  3. resolved

    The issue causing missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions has been fully resolved. Cluster health, shard, and deployment data were unaffected throughout, and no data was lost.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next