You made no requests to our webserver from the hours of 06:34 PDT until 08:54 PDT (so about 2.5 hours). These are the requests in our logs -- and we log everything, so any oddities on the webserver side would have shown up here.
These two GET requests are literally in sequential order -- nothing from your IP address arrived at our webserver between these two requests.
Code:
24.89.xxx - - [24/Mar/2012:06:34:59 -0700] "GET /bbs/templates/subSilver/images/icon_mini_search.gif HTTP/1.1" 200 237 "http://nesdev.com/bbs/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/534.52.7 (KHTML, like Gecko) Version/5.1.2 Safari/534.52.7"
24.89.xxx - - [24/Mar/2012:08:54:48 -0700] "GET / HTTP/1.1" 200 22313 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/534.52.7 (KHTML, like Gecko) Version/5.1.2 Safari/534.52.7"
The requests also landed at and were answered by the 72.20.98.77 IP address.
Based on the fact that you posted the problem at 09:09 PDT, I would say the issue was with your ISP, some kind of man-in-the-middle compromise, or a very serious/catastrophic router bug. I do not believe the problem was DNS-related (barring things like severely broken DNS caching proxies) because as I said, the wiki and main nesdev sites are on two completely different IP addresses.
If I had to take a guess, I'd say your ISP (Access Communications in Canada) either uses a form of transparent HTTP caching/proxying or does some form of transparent layer 7 packet manipulation and their shit broke badly for a couple hours. Whether or not you saw anomalies to other websites during that ~2 hour timeframe is irrelevant. I have seen caching proxies (transparent or configurable) completely break before, and in very bad ways. ISPs here in the states, like Comcast, have
screwed things up similarly and despite customers noticing the problem the issue disappears mysteriously a few hours later with no mention of it anywhere.
TL;DR -- whatever happened was purely unrelated to anything hosted here.