OK, I got some info:
We had some issues on the API of some repositories (clients were seeing a 429) : the rate limit configuration was activated on the reverse proxy stack of the APIDB.
We removed it since we are ratelimiting at the first entry level.