Replies: 11 comments 31 replies
-
Interesting. Nothing during the daylight hours AEST TZ UTC+10 and all forecast updates fine, but a re-start hit a 429 on sites load for me just now. Five additional re-starts also hit 429. So yes, @Ben00793. It's them, not us. (I think the false declaration of presumption of death has been fixed in v4.3.3, BTW. That rings a bell. The log below is from v4.3.3 code running on my prod instance.)
|
Beta Was this translation helpful? Give feedback.
-
Quickly altering the user agent string ( |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
My most recent scheduled (via an automation) call seems to have been missed, I don't have any logging in the automation (it just calls update). So I assume it is the same issue as reported here. It does one call in the early hours so that the overnight cheap rate import can be adjusted appropriately, and the other 4 calls are spread out evenly through the sunlit hours (east/west arrays so I get 5 rather than 10). Next & final call should happen in about an hour, fingers crossed that they resolve it at some point, the solcast forecasts are super useful :-)
I wonder if it might be worth having some sort of fall-back forecasting method if enough API calls fail in a row. A lot of my automations rely on it, and assume it'll always work, which is obviously a risky assumption. |
Beta Was this translation helpful? Give feedback.
-
Same here. I noticed repeated 429s a few weeks ago and contacted Solcast support who found a rogue account that was somehow hammering the API. Just emailed them again to see if this is something similar. |
Beta Was this translation helpful? Give feedback.
-
Hey Team, Just giving a quick update here, as a few of you have emailed in. There was one user that caused the issue with excessive API requests. They've now been restricted, so the API should return to normal shortly. |
Beta Was this translation helpful? Give feedback.
-
@billy-solcast still no luck here nearly 2 hours later: No updates at all today, including four or five since you indicated that it should start coming good and your status update on your website indicated that service has returned to normal https://status.solcast.com/incidents/288675. That makes me think that you're still blocking legitimate requests. Just in case it was my box, I've reloaded the integration:
|
Beta Was this translation helpful? Give feedback.
-
v4.3.3 is in the wild. Enjoy. (And thanks again for the feeedback @billy-solcast. 😘 The failed-state optimisation is in the v4.3.3 payload.) |
Beta Was this translation helpful? Give feedback.
-
Bumping this as I've had repeated 429s today since around 9am UK time. Anything you can see @billy-solcast? |
Beta Was this translation helpful? Give feedback.
-
Same here. Last successful update was at 9:55 UK time. |
Beta Was this translation helpful? Give feedback.
-
@billy-solcast I've been getting 429s since 2025-05-23T08:19:31.671+10 (2025-05-22T22:19:31.671Z) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Anyone else having issues today with API calls?

I'm in the UK.
Beta Was this translation helpful? Give feedback.
All reactions