I just rolled to the floor. I love South Park.

I'm going with everybody else, it's an encrypted stack trace. Every reload is entirely different rather than small portions changing, so we can assume it's something like AES rather than a simple XOR. If it were a simpler encoding we would see largely similar areas with just small sections changed for server IDs and timestamps. The distribution of the data is for all intents random, and it's too big to be an identifier on it's own, so that's the only logical explanation I can come up with.

It's probably an encrypted stacktrace

It looks like it's a url-safe base64 encoding of an encrypted blob (perhaps a stack trace). They're using '-', and '_' instead of '/' and '+'. Replace these characters and base64 will succeed, leaving with ~3k bytes randomly distributed between 0x00 and 0xFF.

I am confused why they need to include that if there is little customer support.

the decoded data has a frequency distribution similar to random output so probably encrypted :) maybe that did something lolzy like stream cipher with the same key.

could easily be encrypted data

And now it's back on for me