Replies: 14 comments 6 replies
-
I noticed this issue as well! Showing updates on their website within the last hour, but the API data is > 3 hours old. |
Beta Was this translation helpful? Give feedback.
-
A good portion of the time I check, the data is still hours old. Wish someone from NWS would even acknowledged the issue, they have been ignoring it for months. :( Regards, |
Beta Was this translation helpful? Give feedback.
-
I just checked, and the issue is still present. There's a 2 hour delay in the API values. However, on their https://forecast.weather.gov website, the values are much more recent. |
Beta Was this translation helpful? Give feedback.
-
The Tech control/sec at NOAA informed me that they opened a ticket on this issue as of this morning, after I e-mailed them (and before I saw this thread). Here is what I wrote. I'm sure it's what many of you are seeing: Good morning! I hope you enjoyed a nice 4th of July weekend. I've been experiencing a recurring problem with the api.weather.gov service. It appears that the current observations for an airport such as KFBL are accurate when looking directly at forecast.weather.gov, but they are delayed in upwards of a half hour or more when viewing the same current conditions on the api.weather.gov service. Let me provide some detail. On 7/5/25 at 8:51 a.m., here's a view of the current conditions/weather condition icon directly from forecast.weather.gov for KFBL: Here is the same detail when viewing the information at https://api.weather.gov/stations/KFBL/observations/latest?require_qc=true (with relevant highlights below): ==================================================================
=============================================================== I guess my question is twofold:
I appreciate any insight into the situation, as there must be some explanation why the data appears differently in each source. Obviously, I'd like to get the most updated information that I can. Brian Klier |
Beta Was this translation helpful? Give feedback.
-
By the way, if anybody is looking to use the aviationweather.gov API and not have to change their code very much to make it work with their existing code that uses api.weather.gov, here's somewhat of a converter written in PowerShell that outputs a txt file with a response like you'd get from api.weather.gov, except with updated aviationweather.gov data. Do not use for critical life and safety functions, use at your own risk, etc., etc., common disclaimers apply:
|
Beta Was this translation helpful? Give feedback.
-
I know this is still active, but have there been any updates? For the past month, I've been seeing delays on Station KROC of up to 3 hours. Today I noticed that it hasn't updated in over 7 hours. For the station, I'm using the following curl
Thanks Well .. it just updated with a |
Beta Was this translation helpful? Give feedback.
-
We have exciting news on this. We have been working on this behind the scenes and believe we have ironed a lot of the issues that have been reported. The code update is now publicly available and ready for testing on preview-api.weather.gov |
Beta Was this translation helpful? Give feedback.
-
I just ran a KROC Observation Latest api.weather.gov - Updated 1h:55m ago My Grid Hourly forecast hasn't changed between the 2 - both showing Updated 2h:13m ago. I appreciate you and your team fixing (hopefully) the Station Observation as this is what I use to feed into some other apps edit: just checked again 6 hours later api.weather.gov - Updated 2h:2m ago |
Beta Was this translation helpful? Give feedback.
-
The update was made live this morning. One more thing of note. For larger airports the API is now making the high-frequency METARs available. Example: |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Thanks for the update. I'm currently not seeing the METAR info for KROC nor KBWI from the post above (Is "rawMessage" the correct tag for METAR?). I use the METAR codes to fill in any missing info (dewpoint, windDirection and windSpeed) from KROC/observations/latest.
|
Beta Was this translation helpful? Give feedback.
-
Here's what I have from Home Assistant, which plots everything at the time received rather than the timestamp in the data.
From my few manual tests, it looks like the API is somewhere around 15 minutes delayed while https://www.cnrfc.noaa.gov/metar.php is about 8-13 minutes delayed (I saw two 5-minute observations appear in 1 minute). I'll give it a few days, but so far it looks improved enough that I would no longer consider it woefully unreliable for the current weather. Thanks! There's still room for improvement, but that's my idealist talking. I suspect most of the delay now is upstream of the API and most of the discrepancy with my sensor may be the local environment. |
Beta Was this translation helpful? Give feedback.
-
Now that this has been running for about a week I've noticed that the I guess this is a double edged sword. With the 5-minute updates, 4 days of history takes up just under 5mb of data to transfer which fortunately gzip takes down to under 100k. I don't have the exact data on the old data sizes but I would estimate they're 20x smaller. Was the intention to also reduce the length of the observations history with the recent latency and frequency update? |
Beta Was this translation helpful? Give feedback.
-
Please contact [email protected] with this issue if you haven't already. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
FYI to the general public who may be using this API.
Over the last few months the delay from when a weather observation is made and when it gets updated on the API has been taking longer and longer, it used to be 5-10 minutes not too long ago, but now routinely takes an hour or sometimes as much as 3 hours to update. This is terrible in my opinion for data that is usually updated every hour.
We call these METAR reports in the aviation community. It stands for Meteorological Aerodrome Report, basically the weather at the airport. Sample here:
https://api.weather.gov/stations/KVNY/observations/latest
I've contacted [email protected] several weeks ago and so far they have just pointed out that data may be delayed 20 minutes, ignoring that it usually takes a lot longer. I've emailed them again several times with no response.
I hope they resolve whatever the delay is. Maybe posting here will help.
FYI, the API at aviationweather.gov is updated usually within minutes and I'm transitioning my equipment to be able to use both APIs.
Post your comments I would like to hear if this is bothering anyone else!
Regards,
-Moses
Beta Was this translation helpful? Give feedback.
All reactions