rewindex

CompaniesCoralogixIncidents

Coralogix: Switching NLB endpoints at Coralogix

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.coralogix.com (opens in new tab)

Timeline of updates

  1. resolved

    Due to AWS limitation of 250 connected instances per NLB, we are switching our NLB configuration. The change might affect customers who are whitelisting specific IPs. Make sure you have the new IPs whitelisted in your account. 54.229.120.114 52.17.104.47 52.212.205.202

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 2019-12-12 14:10 UTC, resolved after 0 min, 1 update(s).

Title
Switching NLB endpoints at Coralogix
Vendor
Coralogix
Date
URL
https://rewindex.com/company/coralogix/incidents/mhbl4qtdsgrl

Coralogix profileRecent Coralogix incidentsAll outages on December 12, 2019Coralogix in December 2019MarkdownJSON