Well there you go!
More seriously, if the problem wasn't on your machine, it was still likely close to your end. Either between you and your ISP or between your ISP and autopia.org. You might want to do a tracert autopia.org from a cmd line to get an idea of the multiple steps (hops in IT lingo) your data takes between you and autopia. Then if things go bad again, run the same command and compare. That way you can get an idea if one of your ISP's routers is having a brain fart or if the problem is on the other side of your ISP. In any event, if a lot of other people report success reaching the site, it's not very likely that there's a server problem with that site, is it? Another tool to use is nslookup. nslookup autopia.org should spit out a 32 bit address (shown as xxx.xxx.xxx.xxx where xxx=a number between 0 and 254). You can also run tracert on this number. Or tracert -d (this takes DNS out of the picture.) With these tools you should be able to get an idea if a problem is DNS related or a problem somewhere along the path between you and the site ou want to reach.