Elastic Status · History · Incident #6258
RESOLVEDGCP asia-south1 high latency
Major · Started Aug 6, 2026 · 5:41 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Elastic Status · History · Incident #6258
RESOLVEDMajor · Started Aug 6, 2026 · 5:41 PM
Duration
< 1m
Severity
Major
Detection lead
—
User reports
—
Summary
On 2026-08-06 between 0900 - 1200 UTC, customers in GCP asia-south1 may have experienced high latency when communicating with their Elasticsearch deployments during this window. The cause has been identified and mitigated.
Started
Aug 6, 2026 · 5:41 PM
Resolved
Aug 6, 2026 · 5:41 PM
Duration
< 1m
Severity
Major
Event timeline
Resolved
Aug 6 · 5:41 PM ElasticOn 2026-08-06 between 0900 - 1200 UTC, customers in GCP asia-south1 may have experienced high latency when communicating with their Elasticsearch deployments during this window. The cause has been identified and mitigated.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.