Thanks so much for the fast response! Yes. This behavior is very consistent at 7:00:00. And this is the only peak period when it happens. (For example, a similar number of calls are made at 7:00:00 London time, with no timeouts. I'm happy to share detailed traffic logs on a non public forum.

How do you determine if it's the final waxing or the first waning day that should be a full moon?

yep. Just when I think maybe they've actually fixed the problem, the 502's start coming again. WeatheKit was finally okay today (4/5) during the day. But now in the evening, a huge percentage of calls are returning 502. It would be nice if Apple acknowledged the situation. The system status only seem to indicate a problem if it affects Apple's weather app. If the API is just borked, it's always green.

But is it? Issue: Today, 12:54 PM - ongoing Some users are affected Users are experiencing a problem with this service. We are working to resolve this issue. I'm just sayin: Dark Sky was down less in the entire time it wasn't under Apple's control, than WeatherKit has been down, slow, buggy in the last couple weeks.

What for what? Why didn't Apple wait to shut down Dark Sky? Wait to pay for the product? Also, what does 16.4.1 have to do with the REST API?

Open Weather has a "one call" replacement for Dark Sky. But 1) still requires a lot of work to get going. It's not a "plug in" replacement. 2) Extremely expensive. Call are 15x more expensive than Dark Sky. My Radar is basically a plug in replacement. I think 99% of the fields, field names, JSON structure, etc is exactly the same as Dark Sky. It's also cheaper than Dark Sky. However, it's rate limited at 120 calls/minute. So, you mileage may vary.

It's still slow and buggy, though. And it's the absolute silence in Apple's part that makes the whole thing feel sketchy.

Yes. I wish I had put my time migrating over to another API. So many reports of errors (404,401,502) and generally slow response times. Apple should do the right thing and keep Dark Sky available until they actually have a production ready API in place. They said they would, and developers put trust in that expectation.

It's too early to say for sure, but @Hi_Thomas seems to have found the solution for me. Implemented his suggested change and haven't seen a 401 since. I think this is an error on Apple's part, since the "issued at time" shouldn't have to be set to a time in the past. The docs say - what else? - that the iat value "indicates the time at which the token was generated."

I was making a dumb mistake. I had Weatherkit enabled under "Capacites" - which seemed to be fine until a few weeks ago. Had to add it to "App Services" as indicated earlier in this thread.

Same here. That code had been working until I returned to it today.

I believe you! But, I think that wind bearing is still the direction the wind moving, right?