*edit* seems like it was temporary... as now it seems to be fine...
nesdev.com points to 184.108.40.206
www.nesdev.com points to 220.127.116.11
nesdev.com points to 18.104.22.168
wiki.nesdev.com points to 22.214.171.124
nesdev.com will always point directly to the main nesdev site (never the Wiki). Ever. Period.
nesdev.com permanently redirects any URL to http://nesdev.com/, so a visit to http://nesdev.com/bbs/ will redirect you to http://nesdev.com/bbs/
The Wiki portion of nesdev is on a completely separate IP address. If you were to connect to 126.96.36.199 and issue a GET request and a Host: header of wiki.nesdev.com, you will get a very informative error page that tells you "you're doing something naughty" and give you details about what it is your web browser submit to our server.
I'll see if I can figure out what happened based on your IP address and the time frame you submit GET requests to our server, but overall this does not look to be a problem with any part of our infrastructure.
Edit: Looks like 24.89.xxx, since there's nothing in our logs today for 207.195.xxx.
These two GET requests are literally in sequential order -- nothing from your IP address arrived at our webserver between these two requests.
Code: Select all
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"
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.
The weirdest part was that nesdev.com went to the wiki and nesdev.com/bbs didn't go anywhere. I don't have much faith in my isp either, but for the price I pay it's the fastest I can get around here.
Like I said, we didn't see any HTTP requests from your IP for over 2 hours, yet there were lots of other people visiting both sites (wiki and the nesdev sites) during that time frame. I'm forced to believe the issue was somehow centric to you or your ISP, sad to say. :(
Here's an example run for sake of what gets analysed.