@RKemper restarted wdqs1007 earlier today ([SAL](https://sal.toolforge.org/log/c8vZLIQB6FQ6iqKiM5ua)), and it’s currently catching up on almost two days’ worth of update lag ([Grafana](https://grafana.wikimedia.org/d/000000489/wikidata-query-service?orgId=1&refresh=1m&viewPanel=8&from=1667122858356&to=1667209258356)):
{F35676048}
However, it looks like the server hasn’t been depooled – I got a query response served from it after a few retries:
```lang=shell-session
$ curl -s -i --data-urlencode 'query=ASK{}' https://query.wikidata.org/sparql | grep -i '^x-served-by:'
x-served-by: wdqs1007
```
This means that some users are getting stale query responses; but more importantly, it means that the Wikidata maxlag has shot up ([Grafana](https://grafana.wikimedia.org/d/000000170/wikidata-edits?orgId=1&refresh=1m&from=1667123019189&to=1667209419189&viewPanel=11))
{F35676094}
and the edit rate has plummeted accordingly ([Grafana](https://grafana.wikimedia.org/d/000000170/wikidata-edits?orgId=1&refresh=1m&from=1667123019189&to=1667209419189&viewPanel=1)):
{F35676105}
Thanks to recent work at T238751 and T315423, the maxlag is supposed to no longer take servers like this into account, as long as they’ve been depooled. Please manually depool this server, so that the maxlag can (hopefully) recover.