Stack Overflow had 59 outages in the last 2 years totaling 503h 0m of downtime — averaging 2.4 incidents per month.
There were 59 Stack Overflow outages since April 27, 2026 totaling 503h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.
Incident: We're currently aware of intermittent database connectivity. This appears to be impacting the following database hosts: sdb-83, shareddb47, and shareddb48. Our System Administrators are currently investigating, and updates will be provided as we have more information available.
Incident Update: Our system administrators have identified the cause of the connectivity issues seen and have deployed a fix to restore database connectivity.
Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.
Incident: We're currently aware of intermittent database connectivity. This appears to be impacting the following database host: wordpressdb-a. Our System Administrators are currently investigating, and updates will be provided as we have more information available.
Incident Update: Our system administrators have identified the cause of the intermittent connectivity and have deployed a fix to restore database connectivity.
Incident Update: All services at our Frankfurt location have remained stable overnight, with no further disruption observed. The facility operator has confirmed that cooling has now been fully restored across all affected areas, with temperatures remaining stable and within normal operating thresholds. Cooling redundancy has also been restored. We are therefore marking this incident as resolved. We have requested a full Root Cause Analysis (RFO) from the facility operator and will review this once available. We apologise for the disruption caused.
Incident: Due to problems with cooling in the Franktfurt DC, kvmhosts are being temporarily shut down to protect hardware. Frankfurt based websites may be unavailable. This will affect sites hosted on kvmhost135, kvmhost136, and kvmhost137.
Incident Update: All infrastructure at our Frankfurt location has now been restored and services are operating normally. Cloud Servers are back online and our network infrastructure has been fully restored. We are continuing to closely monitor the environment and our systems to ensure stability following the earlier cooling incident. We apologise for the disruption this incident has caused and would like to thank everyone affected for their patience and understanding while recovery work was carried out. We will be requesting a full Root Cause Analysis (RFO) from the facility operator to understand the circumstances surrounding the incident and the actions being taken to prevent a recurrence. We will continue monitoring before marking this incident as resolved.
Incident: We're currently receiving reports of packages on the US shared hosting platform experiencing 500 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available. Apologies for any inconvenience caused.
Incident Update: The issue has now been resolved by our system administrators, and all affected services are operating normally.
Incident Update: The issue with the intermittent 502 errors has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.
Incident: We are receiving reports of intermittent connectivity to our hosting platform via the SIN1 CDN node. Our system administrators are investigating this matter, and we will provide further updates as soon as we have more information available.
Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.
Incident: We're currently receiving reports of some websites experiencing 503 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available. 1 Updates
Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.
Incident Update: The issues regarding intermittent 503 errors on some websites have now been fixed. The issue originated from an upstream network transit provider and has now been resolved.
Incident: We're currently receiving reports of some websites experiencing 503 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available.
Incident: We are aware of potential performance degradation on a number of websites using our shared hosting platform in London. Our team are investigating, and we will provide another update as soon as possible.
Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.
Incident: We are currently aware of some reports of slow websites using storage "40a" and "40b" on our shared hosting platform. Our team are investigating, and we will provide another update as soon as possible.
Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.
Incident: We're currently aware of intermittent database connectivity. Our System Administrators are currently investigating, and updates will be provided as we have more information available.
Incident Update: Our system administrators have identified the cause of the connectivity issues seen and have deployed a fix to restore database connectivity.
Incident Update: Shared database connectivity affecting sdb-63.hosting.stackcp.net, sdb-64.hosting.stackcp.net, sdb-65.hosting.stackcp.net, sdb-66.hosting.stackcp.net, wpdb-31.hosting.stackcp.net & wpdb-32.hosting.stackcp.net have now been resolved. Our System Administrators have identified the cause of the database connectivity issue and are now monitoring the situation.
Incident Update: Our system administrators have identified an issue affecting NAS storage 26a on our shared hosting platform in London. Investigations are ongoing, and we are working to restore normal performance as quickly as possible.