There is no way in which Apple actively checks legalty of OS X, other than DSMOSX.kext. So this error doesn't 'only occur on machines running illegal copies of OS X' as some of us seem to think.
Moreover, my copy of OS X is legal, and still generates this error.
Using Google, I have found resources which suggest that 'NSURLErrorDomain error code =-1100' means that 'the requested file does not exist', but seeing as I have only ever seen this error as of today (i.e. never before today), it would seem that this error lies on Apple's side. Add to that the facts that:
a) there are MANY more persons who experience this error, in all kinds of locations, and;
b) all reports considering this error were started today
and one can be almost 100% sure that the issue IS on Apple's side. I'm not saying it definitely is, as there are some people for whom a 'DNS fix' works (i.e. changing the DNS servers to Google's DNS servers in your internet connectivity device). But there seem to be just as many (me included) for whom this fix does not work. Add to that the afforementioned facts and you'd just have to be sure. And, to conclude, someone mentioned in this topic that his logs show a 503 error (Service Unavailable). This would seem that my explanation of the error mentioned (File not available) could only hold true if this file were to be searched for on a remote location... I guess there's little more to it than just wait...