0

Current Conditions delay

Aleksey Kovtun

February 18, 2026 22:25

None

Follow

Hello, 

I am seeing a delay of 30-45 minutes in the "Current Conditions" date time in response to this type of query: 

https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline/34.053819,-118.243698/<CURRENT DATE>
  ?key=<API KEY>
  &unitGroup=us
  &contentType=json
  &include=current

The delay is the same when using the Query Builder on the website and the API in an external program (which makes sense).

I don't expect minute-by-minute updates.

When the current conditions response changes, it seems like there is a 15-20 minute update interval in the timestamps, but they are always delayed by 30 or more minutes. So, instead of seeing the latest "current conditions" from the time that is shown in the timestamp to 15 minutes after the timestamp, I'm seeing the previous "current conditions" from 15 or more minutes after the timestamp to 30 or more minutes after the timestamp.

Is there a way to get more current data?

Thanks!

• Facebook
• Twitter
• LinkedIn

2 comments

• 
  info April 28, 2026 14:34 Official comment

  Thank you for your question.

  We’ve recently upgraded our current conditions ingestion pipeline, which significantly improves how quickly new observations are reflected in the API. With this update, we are now typically seeing 10–20 minutes between the observation time and when it becomes available in our system.

  Previously, it was common to see delays of 30–45 minutes, like the behavior you’re describing. This was due to a combination of factors including station reporting intervals (often 15–60 minutes), upstream data distribution delays, and processing time.

  Even with the improvements, some variation is still expected depending on the station network and location. For example, stations that report less frequently or operate in regions with slower data distribution may still show longer gaps between updates.

  However, overall you should now see noticeably fresher “current conditions” timestamps compared to before, and we are continuing to optimize this further.

  Please let us know if you have any further questions.

  Regards,
  Visual Crossing Support

• 0
  
  Aleksey Kovtun April 28, 2026 16:19

  Thank you for the update!