Twitter | Søg | |
StackExchange Status
Status updates for the Stack Exchange network, including . You can also find more detailed updates on .
758
Tweets
0
Følger
8.211
Følgere
Tweets
StackExchange Status retweetede
Nick Craver 11. sep.
Svarer @Nick_Craver
We are back at read-write for all sites, enjoy your evening!
Reply Retweet Like
StackExchange Status retweetede
Nick Craver 11. sep.
Heads up: we'll be failing over some Stack Overflow SQL servers in the next 10-30 minutes, users should see read-only for a brief period followed by a very short maintenance and a return of read-write afterwards.
Reply Retweet Like
StackExchange Status 10. sep.
Reminder: We have maintenance starting later today.
Reply Retweet Like
StackExchange Status 5. sep.
Heads up: We have maintenance scheduled for September 11th. More details can be found at
Reply Retweet Like
StackExchange Status 4. sep.
Svarer @StackStatus
Sites are back to normal, you may resume your normally scheduled Wednesday/Thursday!
Reply Retweet Like
StackExchange Status 4. sep.
Svarer @StackStatus
We’re up and running for all sites except those with non-English localization; our next build should fix those shortly.
Reply Retweet Like
StackExchange Status 4. sep.
We’re aware of the issue impacting our sites and are working to get them back up and running!
Reply Retweet Like
StackExchange Status 12. aug.
If you're interested in that sort of thing, we have posted a postmortem about the outage we had on 2019-07-30.
Reply Retweet Like
StackExchange Status 8. aug.
Done patching. SEDE should be back up and stable.
Reply Retweet Like
StackExchange Status 8. aug.
Data Explorer is up next in the rotation for some patching. Connectivity will be spotty over the next hour, while it's being worked on.
Reply Retweet Like
StackExchange Status retweetede
Nick Craver 30. jul.
All systems are green now - a non-yielding scheduler inside our primary SQL Server caused a cascade failure of systems that depend upon it. We'll follow-up with vendors and increase our resiliency in several systems here.
Reply Retweet Like
StackExchange Status retweetede
Nick Craver 30. jul.
We are bringing the network up in read-only mode while we investigate what locked a SQL up hard. We'll return to read-write mode shortly.
Reply Retweet Like
StackExchange Status retweetede
Nick Craver 30. jul.
We're having a SQL Server instability issue and digging into it now.
Reply Retweet Like
StackExchange Status 26. jun.
Svarer @StackStatus
We’ve had some strong words with the badly timed reindexing job that locked up our databases - should be stable once again!
Reply Retweet Like
StackExchange Status 26. jun.
We’re aware of an issue with our sites and we’re working to resolve it now.
Reply Retweet Like
StackExchange Status 6. jun.
We're aware of an issue with Elasticsearch and are working to bring it back online now.
Reply Retweet Like
StackExchange Status 29. maj
Svarer @letsencrypt
We’re again live on an updated certificate from with our OCSP issues worked around for now, let us know if you see any issues!
Reply Retweet Like
StackExchange Status 29. maj
Update: The rollback has been completed and will be visible globally over the next 10-15 minutes.
Reply Retweet Like
StackExchange Status 29. maj
A new TLS certificate is failing to send certificate status data that’s required when using Firefox. We’re working with our CDN provider to roll back the change.
Reply Retweet Like
StackExchange Status retweetede
Nick Craver 22. maj
There's a thread leak affecting some Stack Overflow web servers sporadically. We're aware and are investigating it now:
Reply Retweet Like