Topic: stale NWS API data in at least one cache

[Jasiu]

Seems like we've visited this before. Ken probably remembers better than I do.

When my 1&1 web server fetches data from api.weather.com, the DNS resolves to an akamai server/cache at 23.200.224.17. Currently, this returns stale forecast data from this afternoon (about six hours old now).

The same fetch from my browser at home, which resolves to 104.117.188.17, gives me good data.

I've sent in an email to the NWS to let them know. I'd be interested to know if others are seeing stale forecasts right now.

[Jasiu]

....annnnnnnd, just after sending that, I heard back from the NWS.

We are experiencing some issues from an earlier update, so we're rolling it back, therefore you will likely see some inconsistent results until the process is fully completed. Thank you for sharing your observations. I'm hopeful it'll all be resolved and restored within the next few hours, at the latest.

So they do know about it and are at work fixing it.

[colonieweather]

I noticed forecast was doing that for me yesterday and again this afternoon.   Just updated to “tonight” for me about an hour or so ago.  Current conditions in the API seemed to be lagging today as well.  I also sent a notification to them.  I'm using Hostgator.