Games API not functioning correctly [The universe IDs specified are invalid.] [ERROR 400

When fetching universe ids using the games.roblox.com/v1/ api when sending low range IDs it functions perfectly.
This API is supposed to support up to 50 IDs, and it does for low digit games.

This bug initially occurred to me when fetching 15 games, and sometimes it outputted with status 200, and sometimes 400

Here is the following URL that I used that works 50/50 each time you refresh: (either 200 or 400 status code)
https://games.roblox.com/v1/games?universeIds=5995470825,1408435782,8639693426,9141743926,1408435785,1408435786,1408435787,8507699752,1408435789,1176784616,7745138677,6504986360,9141743928,9141743930,9141743923,9141743921

WORKING:
https://games.roblox.com/v1/games?universeIds=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50

Then I made more of the following test to see what could be the root of this problem and tested with 2 billion to 2 billion and 11

NOT working
https://games.roblox.com/v1/games?universeIds=2000000000,2000000001,2000000002,2000000003,2000000004,2000000005,2000000006,2000000007,2000000008,2000000010,2000000011

But when you remove the 11th id it supports only up to 10 ids…

WORKING
https://games.roblox.com/v1/games?universeIds=2000000000,2000000001,2000000002,2000000003,2000000004,2000000005,2000000006,2000000007,2000000008,2000000010

Extremely weird bug, should be easily able to reproduce

Expected behavior

I expected it to properly work with any id range along as it is within if its 0-50 max array[integers], it worked perfectly for the 1-50th universe id.

I’ve been experiencing the same issue here @ roblox…

What you’re seeing is not related to the numeric value of the universe IDs themselves, but to recent protective changes we rolled out to mitigate abnormal traffic patterns that were putting significant load on the service. These protections can cause requests with certain request shapes to be rejected, even if they are technically within documented limits.

We recognize that this can impact legitimate developers, and we’re actively working on a better solution.