Probably just a network hiccup.

I ran into the same thing earlier, but it worked fine after a couple refreshes.