sourcegraph.com searcher errors regularly high, does it include context timeouts?

Created by: slimsag

From the searcher dashboard:

Possibly this includes context timeouts when searcher gives up, and thus the number is artificially inflated currently? The query is:

(sum by (instance)(increase(searcher_service_request_total{code=~"2.."}[5m]))) OR on() vector(0)

If yes, I will need to figure out how to exclude such timeouts.