Vendor reports: partial outageResolved · vendor status “resolved”Official status API

GCP asia-south1 high latency

Reported by Elastic Cloud · Data & Analytics · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Aug 6, 2026, 17:41 UTC
Vendor's clock
Resolved
Aug 6, 2026, 17:41 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Elastic Cloud reports partial outage: "GCP asia-south1 high latency".[E1, E2]
  • The vendor marked it resolved at 2026-08-06 17:41 UTC.[E3, E7]

Affected products and regions

  • Regions: asia-south1 (read from the title, so inferred).[E5]
  • Components: Elasticsearch connectivity: GCP asia-south1.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-08-06 17:41 UTC · summary s1, evidence 2c54856884ea031c

Evidence (7)
  1. E1Elastic Cloud reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "GCP asia-south1 high latency". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-08-06 17:41 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): asia-south1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: Elasticsearch connectivity: GCP asia-south1. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-08-06 17:41 UTC. (vendor) source (opens in a new tab)

Affected scope

asia-south1

Components: Elasticsearch connectivity: GCP asia-south1

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Elastic Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Aug 6, 2026, 17:41 UTCVendor-reported startVendor time
  2. Aug 6, 2026, 17:41 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.