StackExchange Status

We have made the decision to retire this account. Moving forward, the Stack Status site, stackstatus.net, will be the source of truth for all incident news. There you can also subscribe to updates via email and RSS feed.

With our recent status page improvements (meta.stackexchange.com/q/378941/165455), links to posts on the old site now land on an empty 404 page. To fix your existing links, please change stackstatus . net / post / ... to stackstatus . tumblr . com / post / ...

OK, maintenance is over, and the site is back to normal. We ran into a couple issues with our database maintenance--we'll update the meta post for this incident with details once we have them.

Whoa, something just happened to knock us offline instead of being in read-only. We're investigating that outage while also trying to wrap up our scheduled maintenance. We're working on it.

Reminder that we have some scheduled maintenance starting in a little over an hour. The site will be read-only while we work.

We have some maintenance scheduled for Wednesday, 21 September, 00:30-03:00 UTC. Read details on this Meta post: meta.stackexchange.com/q/382050/314146

And that work is done. Thanks for being patient!

This work is starting now... Stack Exchange Data Explorer will be briefly unavailable.

We're going to be doing some database patching for Stack Exchange Data Explorer (SEDE - data.stackexchange.com), starting in about 15 minutes. SEDE will go offline briefly, but we promise we'll be quick about the disruption.

The server maintenance has now been completed.

We have maintenance scheduled at 00:00 UTC 08-23-2022 to upgrade Redis across the network. You can read the details in the Meta post. meta.stackexchange.com/questions/3813…

We've made some adjustments to our back end systems to try and mitigate the ongoing issues. We will be actively monitoring the situation as it develops.

We are currently investigating unusually high load on our servers that is causing a service interruption at the moment.

We have identified the cause of the site instability and believe we have resolved the issue.

We are actively investigating an issue causing degraded site performance.

We have now resolved the intermittent issues affecting users in the Chicago area.

We've identified an issue with our CDN causing intermittent 503 errors for people in the Chicago area.

We are experiencing elevated DDoS activity, we are investigating user reports of error messages. The site is currently up and running.

We have added an answer on Mathematics meta explaining how the site got stuck in read-only mode, what we learned, and how we can try to prevent a recurrence. math.meta.stackexchange.com/q/34652/13515

Full functionality on Mathematics is restored. Now the fun begins: determine how it happened, and make sure it doesn't happen again.