Coralogix: AP1 - delay in frequent search logs
Affected components: AP1 - Ingestion - Logs (Frequent Search)Ingestion - Logs (Frequent Search)
Timeline of updates
- investigating
Customers in AP1 region may observe a small delay relative to ingestion of Frequent Search (high) tier logs. We are actively working towards resolution. Updates will be relayed as soon as they become available.
- identified
The issue has been identified and a fix is being implemented.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3e363bcb4564955e…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Coralogix, started 2026-07-14 18:28 UTC, resolved after 15 min, 4 update(s).
- Title
- AP1 - delay in frequent search logs
- Vendor
- Coralogix
- Date
- URL
- https://rewindex.com/company/coralogix/incidents/6s2vjv5vh0df
Coralogix profileRecent Coralogix incidentsAll outages on July 14, 2026Coralogix in July 2026MarkdownJSON