Ask HN: How is your Apple WeatherKit transition going? | Hacker News Reader

Ask HN: How is your Apple WeatherKit transition going?

6 pointskochb5 comments

We updated our product’s forecast functionality to Apple WeatherKit’s REST API ahead of Apple shutting down DarkSky’s API today.

The API change was mostly straightforward, but the system reliability has been rough so far - yesterday afternoon and this morning, the API is returning high numbers of 502/503/504 errors, and on a large portion of the successful requests we’re seeing latency in the tens of seconds. Apple’s status page[1] indicated an “Available” status for most of this period; it took them over 12 hours to declare an issue that they dated as starting 7:47pm yesterday. Their official support channel has been mostly unresponsive.

How has the experience with the WeatherKit transition been for others? Does anyone have information about the situation and what level of reliability and support we should expect going forward?

[1]: https://developer.apple.com/system-status/

I have heard the same regarding 5xx errors in the past couple of months. I am also working on open-source weather API https://open-meteo.com/. It covers most of WeatherKit features and offers more flexibility. You can either use the public API endpoint or even consider to host your own API endpoint.

Forecast quality should be comparable as the API uses open-data weather forecasts from the American weather service NOAA (GFS and HRRR models) with hourly updates. Depending on the region, weather models from other national weather services are used. Those open-data weather models are commonly used among the most popular weather APIs although without any attribution.

If you have any questions, let me know!

Wrote you a mail. followed the project since a longer time!

Here’s where we ended up:

Apple resolved the issue after 48 hours of performance disruptions. Though I further noted one five minute disruption on 4/3 at 6pm ET. They still haven’t responded to our initial ticket.

We’ve worked around this by implementing Pirate Weather as an emergency fallback (it was an easy option since they are fully compatible with DarkSky’s API). But Pirate’s baseline performance is worse, and they don’t have a plan that supports more than 250k requests/month.

We may have to eventually switch to a different provider.

Catastrophic since the beginning. Has not the same historical data like Darksky and the initial setup was annoying.

It's annoying that one needs an apple device to pay for an subscription of that API..

Because of that having a fallback for all the outages.

The historical limitation should be emphasized - requests for dates before August 1 2021 will return a success status, but always with the data for 8/1.

Reply on news.ycombinator.com