Coralogix: "All Logs" screen didn't load for some Asia Pacific (Mumbai) ap-south-1 region customers (customer-name.app.coralogix.in)
Timeline of updates
- resolved
We identified a problem wherein the operation of grouping by an extracted field led to errors, causing runtime instability. To mitigate this issue, we have temporarily reverted the recent change and intend to provide a permanent resolution in forthcoming updates.
From Coralogix’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.coralogix.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Coralogix, started 2024-03-18 05:30 UTC, resolved after 0 min, 1 update(s).
- Title
- "All Logs" screen didn't load for some Asia Pacific (Mumbai) ap-south-1 region customers (customer-name.app.coralogix.in)
- Vendor
- Coralogix
- Date
- URL
- https://rewindex.com/company/coralogix/incidents/qkwlmn8c68c6
Coralogix profileRecent Coralogix incidentsAll outages on March 18, 2024Coralogix in March 2024MarkdownJSON