Openweathermap gotcha

[freddie]

I received this last month (all spelling mistakes copied as received ):

Dear Customer,
Your OpenWeatherMap API key <redacted> is temporary blocked due to the continual sufficient exceeding of the calls per minute limit by performing 607 requests within a minute but the limit for the Free account is 60 rpm.

To unblock your API key and restore the normal operation with the weather API we ask you to surpress the loading from your API keys or upgrade your subscription. Contact us at info@openweathermap.org for any help with choosing the proper type of the subscription.

This was after Cumulus had been shut down for a day and a half, and then performed catch-up operations.

One to watch out for if you have an extended catch-up to do.

[mcrossley]

How long did it take to recovery after the block?

And yes maybe people with free accounts may want to think about disabling the catch-up feature for Openweathermap.

[mcrossley]

I have noticed a similar issue with the MetOffice WoW on catch-up too.

[freddie]

How long did it take to recovery after the block?

I don't know as I have only just seen the email - nightmare hard disk fail on my server on 20th August, involving the boot partition and the partition containing LVM metadata I just happened to notice the email in the old mailbox that I recovered from the disk at the weekend. All that aside, I've never been able to find my data on their system so I wouldn't have known how to check anyway.

And yes maybe people with free accounts may want to think about disabling the catch-up feature for Openweathermap.

Yep, that was my main reason for posting.

I have noticed a similar issue with the MetOffice WoW on catch-up too.

If you mean the 429 responses, then yes I've seen those too. They appear to be generated partly on your request history and partly on system load, as I occasionally get away with catch-up on WOW, but not often!