Open the load balancer → Activity tab in my.cubepath.com.

A paginated history of every action taken on this load balancer, filtered to this resource only: listeners created, edited or deleted; targets added or removed; health checks configured or changed; certificates issued, renewed or deleted; algorithm and sticky-session settings; floating IP assignment; and resizes.

Each entry records what changed, who changed it, and when.

What to look for

A load balancer sits directly in the request path, so its configuration changes are felt immediately and by everyone. When something broke and nothing was deployed, this log is usually the answer:

  • "Traffic stopped reaching one server." A target removed, or a health check tightened until that backend stopped passing it.
  • "HTTPS started failing." A certificate deleted, or one that expired without auto-renew.
  • "Some users lost their session." A sticky-session change, or a target removal with stickiness on.
  • "It got slow at peak." Compare a resize (or the absence of one) against the Metrics connections-per-second chart.