KCM GRC - 500 Errors Upon Login

We have identified an issue where users may receive a 500 error upon logging into KCM GRC, and our engineering team is looking into a fix.

We have identified an issue where users may receive a 500 error upon logging into KCM GRC. A fix has been implemented, and we will continue to monitor this issue.

We have identified an issue where users may receive a 500 error upon logging into KCM GRC. A fix has been implemented, and users should be able to login without error.

From Tuesday, June 23, 2026, at approximately 10:03 (UTC) to Thursday, June 25, 2026, at approximately 11:54 (UTC), some US and EU customers experienced intermittent 502 errors when logging in to KCM GRC.

This issue was caused by network traffic attempting to connect to invalid multilevel subdomains, which overwhelmed the cache serving KCM GRC and resulted in login errors. Our team initially updated the configuration of our content delivery network, which temporarily resolved the errors, but they returned later that day. After further investigation, we identified the caching issue as the root cause and deployed an infrastructure-level fix to prevent multi-level subdomain traffic from affecting the cache. KCM GRC returned to normal performance by 11:54 (UTC) on June 25, 2026.

To prevent this type of issue in the future, we are evaluating additional protections to guard against similar traffic that could affect the cache.

No data loss occurred as a result of this issue.