Hi,
We’ve been getting a lot of intermittent 503 errors from the /api/v2/profile endpoint and wanted to see if there’s anything going on on your side.
We’re using it for player profile indexing on R6Intel. The affected key is limited to 5 requests per minute and only sends one request at a time.
What we’re seeing:
* Requests reach R6Data normally
* They usually take around 13 seconds before returning
* A lot of them come back as HTTP 503
* We’re also getting some successful 200 responses in between
* We are not seeing 429, 401, or 403 errors on this indexing key
On October 7 we got successful 200 responses around 10:47–10:54 UTC, then it started returning 503s again afterward.
We’ve already lowered the request rate and made sure there aren’t multiple requests hitting the same key at once, but the issue is still happening.
Could you check if there are any issues with /api/v2/profile, our API key/account, or the backend handling those requests?
I can send timestamps or sanitized logs if needed.
Thanks,
Zachary
R6Intel
r6intel.cc