Post-incident update: After investigation, we confirmed that the reported ChargeEye UI downtime on Nov 4 was a false positive. One of our system health monitors incorrectly interpreted downtime, while the ChargeEye UI remained fully operational. We’ve adjusted our monitoring configuration to prevent similar alerts in the future.