August 16: this desk's own pages stopped answering, and the alert named the wrong line.
This site publishes how long public bodies take to answer a documented request. Today its own pages answered nothing. What happened At 17:15 UTC an alert opened on the route that serves account profile pages —…
Read record summary
For roughly a quarter of an hour today, every account profile page on this site returned an error instead of a record. The database behind them could not be reached. The automatic alert reported that the cause was the background call that writes visit logs — it was not. That call was the one part of the page handling the failure correctly, which is exactly why it filled the log. Two other reads, with no handling at all, took the page down.
Matched in article text
