Did you observe it on one particular project and on that projects API calls also, where it is impossible to get an organization’s listings of vector stores because of damaged listings inside. Then switch to another project, see success in listing or an empty list with no errors, then go back to the original project and again get a broken vector store listing?
It is not a platform site issue, it is not platform site code or making bad requests or the URL showing wrong info: it is a data corruption issue. Multiple forum reports, no remedy.
Those experiencing the issue by platform site API call, that is exactly mirrored on the API endpoint when called by project API keys, can sometimes work around what appears to be a damaged vector store ID index by making API calls and listing with a very low limit or limit=1, or by changing descending order to ascending to avoid where the listing issue occurs. That demonstrates it is the DATA.
If you did not identify this issue instead of a happenstance “we saw something too”, track organizations and replicate the fault on their projects, and deliver a solution to the database itself, it cannot be considered repaired. You are just waiting for even more developers to enter the realm of failure, when their own store listing gets messed up. Developers that have continued to have issues must be pinged. Like: