Incident Library

Applied filters ComponentDatabaseSymptomWrites rejectedOrganisationStack ExchangeClear allEvery case under the filters, with no sentence; newest first.

Suggested filters Search, and the values found in your words appear here.

Graph

Root cause
Component
Symptom
Contributing factor
Case

Cases1 case

1 to 1 of 1

IL-0335 A bugcheck in the primary SQL Server put the Stack Exchange network into read-only mode and then offline for 12 minutes
Stack Exchange2017
Symptoms
On January 24, 2017 at 17:53 UTC the Stack Exchange network, including Stack Overflow, went into read-only mode for about 5 minutes and then went offline for 12 minutes. It took the team 2 minutes to notice the problem, 5 minutes to locate its source and 10 minutes to restore service.
Writes rejected Service outage Failover failure Data loss
Trigger
At 17:53 UTC the primary SQL Server, NY-SQL02, triggered a bugcheck in the SQL Server process.
Root cause
unknown
Component
Database
Contributing factor
Single point of failure
Remediation
Restarted the SQL service on NY-SQL02, which brought the network back online in read-only mode
Put the sites back into read-write mode after a sanity check of SQL health
Brought the network online without waiting for the memory dump to complete
Took NY-SQL02 out of production for testing, including a memory test, and ran the normal load on NY-SQL01
Brought the SQL cluster up to 2016 SP1 CU1
View case

Check your cluster for this

This case involves Database. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

Open kubegap

By root cause1

unknown1 case

Component: Database
Contributing factor: Single point of failure
Organisation: Stack Exchange

IL-0335 A bugcheck in the primary SQL Server put the Stack Exchange network into read-only mode and then offline for 12 minutes
Stack Exchange2017