"Just spoke with IT, and they told me the root cause is how some ISPs read http headers. A fix is going out for this as we speak – we have modified the header of our ad tag on the back end and are releasing that fix. This issue is very sporadic and depends largely on how downstream ISPs handle the caching of content. By later this afternoon (caching timeouts) this issue will have stopped for the users seeing the error."
If anyone is still having trouble by the end of the day, please let me know.
No!!!!!!!!! How do you make the scream smiley???
Please let me know if you are still having the issue on Tuesday. It seemed to have cleared up immediately for some people.
Thanks -