WDQS Blazegraph applies token-bucket based throttling per (ip, UA) pairs.
Under service load, the streaming-updater-consumer client gets throttled (status code 429) too: https://logstash.wikimedia.org/app/discover#/doc/logstash-*/logstash-default-1-7.0.0-1-2026.05.08?id=qz_pBp4BIM7hdzulB9Wh.
An agents.txt file groups known clients into shared buckets. Requests that do not match any pattern fall back to a generic (ip, UA) bucket. The consumer updater UA is not currently included in agents.txt, but is treated as an unclassified client and still throttled.
We should handle the consumer IP (localhost) and User-Agent (default Jetty string?) more explicitly, and prioritize it over read-heavy query traffic.
Related.