It’s expected that the rpm will differ greatly when “zooming out” if you don’t have continuous data.
Eg. if you make a request every second then there will be 60 requests made after minutes. Doing this for 5 minutes will create 300 requests. That is 60rpm for both the 1min interval and the 5 min interval. However, if you look at it over a 24hour interval it would be 0.2rpm (300 requests / 24 hours).
At first, I was confused by the screenshots of your graphs which show 120 rpm for last one hour and 2000 rpm for last minute. But that’s for the same reason - The UI does not show the max rpm for each time bucket but the average. Especially if looking at narrow spikes, the rpm is high when looking at it at high granularity like 5m. But when the granularity is lower like 1h or 24h, one data point represents a larger time span and the spikes even out.