Incident reports
This post outlines 2 recent production issues on GOV.UK and how they were resolved. We’ve blogged in the past about what happens when things go wrong on GOV.UK and how we classify and prioritise incidents. What happened From around 2:50pm …
This post is about 2 incidents that affected our travel advice pages, and how they were resolved. We’ve posted before about what happens when things go wrong on GOV.UK, and how we classify and prioritise incidents on GOV.UK.
This post is about two severity 1 incidents caused by problems with our third-party suppliers, and how they were resolved. The incidents affected the availability of GOV.UK.
Between 8 and 9 August 2017, there was a problem with all GOV.UK smart answers that ask users to select a country from a drop-down menu. This post explains what caused the issue and how we solved it.
This post outlines a recent production issue on GOV.UK and how it was resolved. We’ve blogged in the past about what happens when things go wrong on GOV.UK, and also how we categorise and prioritise incidents.
This post is about a severity 2 incident with some of our Smart Answers and how it was resolved. We believe in being open about our mistakes and sharing our learning. This is why we have these incident write ups …
This post outlines a recent production issue on GOV.UK and how it was resolved. We’ve blogged in the past about what happens when things go wrong on GOV.UK, and also how we classify and prioritise incidents.
In February, GOV.UK had 2 consecutive days of errors affecting applications that utilise our publishing platform. This was a severity 2 incident.
This post is about a severity 2 incident affecting the GOV.UK website. We routinely publish incident reports because we believe we should be open about our mistakes and share our learning. We’ve posted before about what happens when things go …
We’ve posted before about what happens when things go wrong on GOV.UK, and how we classify and prioritise incidents on GOV.UK. This post is a roundup of 5 incidents that GOV.UK encountered between August and October 2016. It follows on …