[BUG] Spectator-v5 returns 500 Internal Server Error.

[hackoh]

Bug Description
Most requests made to the spectator-v5 API are returning a 500 Internal Server Error.

Problem Description
Since patch 14.21, nearly every request to the spectator-v5 API returns a 500 Internal Server Error. This issue seems to affect most environments, preventing reliable use of the spectator API for various applications.

Expected Result
The API should return the requested data for live games or throw a documented error code that can be handled gracefully.

Actual Result
Instead, the API is returning a 500 Internal Server Error for the majority of requests, making it impossible to retrieve live game data. Logs show consistent 500 responses with no further error details.

Developer Impact
This issue significantly affects my ability to operate my site, Lolimo, which relies on the spectator-v5 API to provide real-time game data. The impact includes:

Frequency: Almost every API call is affected.
Severity: My website crashes when this issue occurs due to the inability to handle the 500 responses.
Efficiency: I’m forced to make repeated API calls, increasing the load and complexity of error handling.

Preconditions
To reproduce this issue, the following conditions must be met:

The user must request live game data via the spectator-v5 API.
The request is made after patch 14.21.