My statistics have gotten to a point where they update only every few days. I used to grab my last week’s album grid on Monday and show it to my friends on socials, but that now often isn’t ready until Thursday. Today after trying to look at my recent stats on the web site, I got a rate limit after a couple of page flips.
I guess this files under “bots ruin everything.”
Not a dev, but based on the error being rate limit your stats are likely there, the server is just discarding the requests cause it sees too many from you. Do you have multiple tabs open that might be making requests? Behind a VPN where multiple users might be behind showing as the same IP? Script running that is making other requests?
No VPN, no multiple tabs, and I am a dev so I have a process that runs once an hour and asks for a weekly artist list. (It should only have to run once a day, but the time at which they update is so variable that there’s no single time that always works.)
I got there by (I think) seeing that the albums were wrong, flipping to stats, which defaults to Last Week, then flipping to This Week to find that they were really stale, and then This Month gave me that error.
Having waited half a day, I went in and carefully clicked only as many things as I absolutely had to, to establish that This Week stats are there but haven’t been updated since Thursday.
Ideally, a web UI would not direct users to inspect X-RateLimit headers. A developer knows how to open the inspector to look at those headers, but most users wouldn’t. I knew not to do this, because opening the inspector and issuing yet more calls to get those headers would have done heaven-knows-what to the rate limits, or maybe even gotten me locked out. I also don’t know if something on the page itself is pinging, so I got my screenshot and dumped the browser immediately.
General answer: yes.
More specific answer: we are having issues with our database and our stats cluster at the same time.
We are fixing the database issues right now as I type this, and working on replacing our stats cluster that we’re reaching the limits of.
That being said, the rate limit issue should be unrelated to both of these issues, and definitely something that can be improved (both functionally, and with regqard ot the error message).
