[b][u]Brief Summary of the Error[/b][/u]: The first outbreak of the error was late June 23. The error then stopped for most and slowed down intensely for all others, although Achronos posted [url=http://www.bungie.net/Forums/posts.aspx?postID=34068728&postRepeater1-p=6#34081317]this[/url] before it started again, revealing the nature of the issue (the report button). The error began again en mass shortly after Achronos posted (on June 24), but was then not seen again until early in the morning July 3. It has re-appeared July 9 and 10 in the early morning and on July 12 in the early evening. The July 12 event was reported to be the worst yet, and lasted from around 4:00 PM PST to (at least) 2:00 AM PST on the 13. Early in the afternoon on the 13, Achronos posted [url=http://www.bungie.net/Forums/posts.aspx?postID=34068728&viewreplies=true&postRepeater1-p=15#34699411]this[/url], confirming that the error was fully known and that a fix was on the way. [b][u]What we know[/u][/b]: - The error stems from the report button, which is why the moderators do not have the error and why the error does not appear in private groups. - No sub-domains of bungie.net offer protection from the error. - Refreshing a page [i]will[/i] get rid of the error, but there have been reports of a page being refreshed over 100 times and the error still not going away. Also keep in mind that, if you post and get the error, the post might have gone through. [i]Do not[/i] post again until you get through and see if the post was made! - A fix is set for late on the 13 or 14 of July: no more errors! [b][u]How to get rid of the Error[/b][/u]: - Hit the report button until it goes away. - If you use FireFox, download [url=http://macro-halo.110mb.com/GreaseGrunty%20-%200.6.4.7-fx.xpi]GreaseGrunty[/url] (a specialty version of GreaseMonkey by PKF_647) and then download the [url=http://userscripts.org/scripts/show/52298]Friendly B.net System.Web.HttpException Re-direct[/url] script, also by PKF_647. For best effect, go to Tools->Greasemonkey->Manage User Scripts and place the Friendly B.net System.Web.HttpException Re-direct script at the very top of the list, so it will load first and re-direct ASAP. [Edited on 07.13.2009 12:54 PM PDT]