We're switching back to Fastly momentarily. Hang on.

Hey Y'all, we're aware Stack Overflow is up and down due to the Fastly issues right now. We're working to temporarily re-route traffic directly to out data center any bypass their network until things are stable again. And of course, #hugops to the @fastly crew!

And we're back - have a good evening!

We're about to take the Stack Overflow/Stack Exchange network down briefly for a server swap - we'll be right back!

Heads up: we're having some network issues behind Stack Overflow resulting in an elevated error rate. If you hit something, please try again. We're investigating the source of these timeouts now.

We're aware of a SQL blocking issue on Stack Overflow. Please stand by, working on clearing it out now.

We have turned off the problematic ISP causing high loss to some Stack Overflow properties. We're investigating the cause with them.

We are back up - search is offline while we investigate an issue.

We're aware of an issue affecting Stack Overflow - we're digging in now.

We're going to take Stack Overflow and Stack Exchange network read-only for a SQL failover shortly. There will be a brief outage while we cut traffic to the primary cluster to reduce failover time.

Search has been re-enabled across the Stack Exchange network. Apologies for the interruption.

Search on Stack Overflow and Stack Exchange will be back as soon as the cluster gods cooperate, thanks for hanging in there for a bit.

And we're back - we've got dumps for Microsoft to investigate the SQL Server 2019 log growth issue. Thanks for your patience.

Sorry that took a bit - we hit a deadlock issue on 12 databases in the Stack Exchange Network AG that we had to resolve (removing, offlining them, and re-joining to the AG) to get the last of the network online. All sites are not up in read-write, thanks for bearing with us!

A few network databases didn't come up properly after the failover (12 total) - we're investigating now.

Bringing Stack Overflow back online now - network sites to follow shortly.

We're about to perform database failovers for Stack Overflow and Stack Exchange for the SQL 2019 upgrade, hang tight!

Here are some more details about our deprecation of TLS 1.0 and 1.1 for Stack Overflow & Stack Exchange starting next Wednesday: meta.stackexchange.com/quest…

SQL is very, very angry. We're aware and working it.

We are back at read-write for all sites, enjoy your evening!