Sign up ×

Both of these are currently returning 404 Not Found. What's up with that?

share|improve this question

3 Answers 3

up vote 2 down vote accepted

StackAuth's new DNS record is propagating, expect some outages as per the blog.

We expect all the DNS issues to shake out well before the recommend /sites cache time elapses.

Associated accounts on the sites themselves will be kind of weird while that record is propagating, so /users/{id}/associated wouldn't really be reliable even if you could get to it.

share|improve this answer
I hope so... I might have to manually patch StackMobile's cache - since it refreshes in a few minutes. –  Nathan Osman Oct 24 '10 at 19:34
I checked out my code and I noticed that I'm using without 1.0 (Not affected by the DNS change).. What's the difference? –  systempuntoout Oct 25 '10 at 6:37
@systempuntoout - /sites basically snuck in when we froze 1.0. There are enough people using it that we can't track down (at least, not without alot of log parsing pain) that I didn't want to just tear it out. The correct way to use the 1.0 API is to hit /1.0/sites directly, we make no guarantees about the lifetime of the raw /sites route. –  Kevin Montrose Oct 25 '10 at 6:40

It has been more than 12 hours since I checked, it is still returning a 404. Does anyone have an idea when will be available?

share|improve this answer
I was just going to ask this myself :P –  Nathan Osman Oct 24 '10 at 22:16
Seems to be working for me now –  Felix Oct 25 '10 at 7:06

They are moving datacenters; could be related with that.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .