Update: this problem is now fixed. See here for more details or read on for a description of the original problem.
Since around 09:30 GMT today the API has been having some intermittent problems:
- Requests for stations for which we have detailed temperature data stored are sometimes taking much longer than usual to complete (on the website this may cause a timeout).
- For the stations for which we have detailed temperature data stored, the most recent data (last few days) might not always be available. If you’re waiting for recent data, we’d suggest trying again every few minutes until it appears (which should typically happen after a couple of attempts).
- Requests for the lower-quality stations for which we do not have detailed temperature data stored are sometimes failing (through the API you’ll get a
ServiceTemporarilyDownfailure), though those same requests may work just seconds later. You’re unlikely to be using these stations if you’re using the API, as they are never selected automatically by requests for data from geographic locations.
Apologies for this. We’re hoping that, as only a small proportion of requests are being affected, it won’t affect too many API customers or website users. But we’re looking into it right now and hoping to get it resolved as quickly as possible.