Última hora
United States flag Estados Unidos: El demócrata Hakeem Jeffries pronto asumirá la presidencia de la Cámara de Representantes RFI Español · ahora mismo•China flag Arrancó la cumbre entre Xi, Trump y Putin: "Haciendo historia" DW Español · ahora mismo•Réunion flag Xi, Trump y Putin inician una reunión trilateral histórica en Shenzhen El País · ahora mismo•La campaña electoral monopoliza la Asamblea de Madrid con una Ayuso omnipresente en la estrategia del PP El País · ahora mismo•China flag Trump, Putin y Xi Jinping se reúnen en China en una cumbre histórica El Mundo · ahora mismo•China flag Xi, Trump y Putin se reúnen por separado antes de trilateral en APEC DW Español · hace 1 h•Rayman Legends Retold presenta un nuevo e inesperado nivel musical al ritmo de Dynamite Vandal · hace 1 h•China flag 🔴 En directo: comienza en Shenzhen, China, la histórica cumbre trilateral entre Trump, Xi y Putin France 24 Español · hace 1 h•United States flag Estados Unidos: El demócrata Hakeem Jeffries pronto asumirá la presidencia de la Cámara de Representantes RFI Español · ahora mismo•China flag Arrancó la cumbre entre Xi, Trump y Putin: "Haciendo historia" DW Español · ahora mismo•Réunion flag Xi, Trump y Putin inician una reunión trilateral histórica en Shenzhen El País · ahora mismo•La campaña electoral monopoliza la Asamblea de Madrid con una Ayuso omnipresente en la estrategia del PP El País · ahora mismo•China flag Trump, Putin y Xi Jinping se reúnen en China en una cumbre histórica El Mundo · ahora mismo•China flag Xi, Trump y Putin se reúnen por separado antes de trilateral en APEC DW Español · hace 1 h•Rayman Legends Retold presenta un nuevo e inesperado nivel musical al ritmo de Dynamite Vandal · hace 1 h•China flag 🔴 En directo: comienza en Shenzhen, China, la histórica cumbre trilateral entre Trump, Xi y Putin France 24 Español · hace 1 h
Revision 1

This revision as JSON · Prints cleanly from your browser's print command.

1What changed since the last material update?

This is the first record of the incident.

  • First recorded by Spike · incident revision 1
FieldBeforeNow
status—identifiedchanged
provider impact—majorchanged
services—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
+ 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
changed
regions—me-south-1
+ me-south-1
changed
mitigation or recovery—the provider has identified the issue and is working on a fix
From the provider's status term, not from a separate statement.
changed
cause——
Not stated by the provider in a structured field.
same

2Who says so, and when?

ClaimValueEvidence
Incident statusidentifiedProvider statement Elastic Cloud · published 2026-09-21 15:21 UTC · incident revision 1 · fuente ↗
Provider impact levelmajorProvider statement Elastic Cloud · published 2026-09-21 15:21 UTC · incident revision 1 · fuente ↗
Services namedAWS 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-1Provider statement Elastic Cloud · published 2026-09-21 15:21 UTC · incident revision 1 · fuente ↗
Regions namedme-south-1Provider statement Elastic Cloud · published 2026-09-21 15:21 UTC · incident revision 1 · fuente ↗
Latest provider updateUpdate — 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…Provider statement Elastic Cloud · published 2026-09-21 15:21 UTC · incident revision 1 · fuente ↗
Severity used for sorting2Spike inference SpikeTrendWatch · incident revision 1

Independent reporting and observable signals: none attached to this incident. Only the provider's own statements are shown. Public attention (for example a search spike) shows interest only. It is not evidence of cause or impact.

Open questions

  • Cause: not stated by the provider in a structured field.
  • Customer impact: not established. The provider reports its own systems; impact on a specific business needs that business's own evidence.
Began (provider)2026-03-02 06:23 UTC
Published by Elastic Cloud2026-09-21 15:21 UTC
Observed and published by Spike2026-11-18 03:42 UTC
Deliveredper workspace, in its private view

3Which business service should I check?

That depends on what your business runs on. See the private view in a synthetic demo. In Spike Pro (free beta), list the providers and services you depend on; your private view of this brief then shows which business service each revision touches, whether it is a direct match or a possible exposure, and why. Customer impact always needs your own evidence.

4What did we know then?

Revision 1 uses only what Spike had recorded by 2026-11-18 03:42 UTC: incident revisions 1. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 2926a04e44c8148f).

This is the latest revision.

5Who received the correction?

No correction has been published for this incident.

Delivery outcomes are private to each workspace and appear in its own view of this brief.

Handoff summary

Plain text to paste into a ticket or shift handoff.

Schema spike.evidence-brief/1. A brief is built from Spike's append-only incident revisions; it adds no facts of its own beyond the labeled Spike inferences. Incident record · API contract · Open another brief