Notice the readTime and reportedTime are 2+ hrs appart. { "currentWeather": { "name": "CurrentWeather", "metadata": { "attributionURL": "https://weatherkit.apple.com/legal-attribution.html", "expireTime": "2023-03-07T20:17:00Z", "latitude": 26.090, "longitude": -80.380, "readTime": "2023-03-07T20:12:00Z", "reportedTime": "2023-03-07T18:00:00Z", "units": "m", "version": 1 },

This is not actually something we can control. Apple technical support has confirmed it's a bug and that there is no workaround. No time frame on when it would be resolved was given. We are currently transitioning the currentWeather data set to another API as a temporary fix. It's definitely hurting our product and we are losing users. The whole thing is actually kind of crazy to me. How can you have a successful weather app that delivers current weather that is always 2 hrs old?

We have been getting harmed all day with complaints. This is the longest outage we have seen since we started with Dark Sky in 2017.

We are also experiencing a high number of timeouts today. As weather app developers our livelihoods are dependent on the accuracy and reliability of our weather apps, which was in great hands with Dark Sky. We mistakenly assumed that Weather Kit would be a seamless replacement.

It's a shame. From Darksky to this? We are almost transited off but I guess the damage has been done. I will definitely sleep better at night knowing that our business no longer depends on Weather Kit.