Cox Community Forums display a white screen

BiPolaris, currently we do not have any details on this but when we find out, I'm sure something will be posted about it. 
-Shariel

@BiPolaris​ Looks like the site goes through a CDN on a SaaS called Sprinklr. That new? I had AI look at the source code and errors and it suggested this; 

An HTTP 400 (Bad Request) and 403 (Forbidden) error combo that is resolved by clearing temporary files (cookies/cache) usually points to a few specific issues related to how the server handles your session and security tokens.

Based on the inspection of your browser state, here are the likely causes:

1. Request Header Fields Too Large (HTTP 400)
The most common reason a 400 error is fixed by deleting cookies is that the Cookie header has become too large.

The Cause: Servers have a limit (often 8KB or 16KB) on how large the HTTP headers can be. Your browser is currently sending several large tracking and security cookies (like reese84 and incap_ses).
Why it happens: Over time, sites or 3rd party scripts (like Google Analytics or security providers) can accumulate many small cookies or a few very large ones. When the total size exceeds the server's limit, the server rejects the request immediately with a 400 error.
2. Corrupted or Expired Security Tokens (HTTP 403)
Your site is using Incapsula/Imperva (seen via the incap_ses cookie) and a bot detection system (seen via the reese84 cookie).

The Cause: These cookies are used to verify that you are a human and have a valid session. If these tokens become "stale," corrupted, or mismatched with your current IP address, the security Firewall (WAF) will trigger a 403 Forbidden error.
Why deleting files works: Deleting temporary files forces the security system to issue you a brand new "clean" token, which allows you back in.
3. AWS Load Balancer Desync
I see AWSALB and AWSALBCORS cookies. These are used for "sticky sessions," ensuring your browser keeps talking to the same backend server. If that specific backend server goes down or your cookie points to an old instance that no longer exists, the load balancer might return an error until the cookie is cleared.

Something about this smells of AI. 

@BiPolaris​

I haven't tried deleting cookies by viewing site information recently using the icon to the left of the address bar, but it didn't fix the issue for me back then.  The white screen still happens occasionally, but I don't come into Cox's forums much anymore.  The fix through settings takes less than a minute and it always works for me.   

The user vs moderator sign in was in use for quite a while before the white screen issue started.  Cox developers probably changed something on the website that caused this issue to occur periodically.  But it may only be an issue for people who come back to the forum a few days later.  There may not be many of those people left, so it's probably not a big enough problem at Cox for anybody to care enough to allocate resources to fix it.