Model Updates and Data Availability

Overview of Model Timings and Data Availability via Open-Meteo API

Model Updates

This page offers a brief overview of all models integrated into Open-Meteo. These models are typically updated every few hours. Open-Meteo aims to download and process the data as soon as it becomes available, immediately after it is released by national weather services.

Open-Meteo operates with geographically distributed and redundant servers. Data across all Open-Meteo servers is eventually consistent, meaning there may be instances where the API indicates a weather model has been updated, but not all servers have been fully updated yet. If you need access to the most recent forecast, it's recommended to wait an additional 10 minutes after the forecast update has been applied.

Models with a delay exceeding 20 minutes are highlighted in yellow. If multiple weather model updates are missed, the model is marked in red. Minor delays are fairly common.

To report a model issue, please open a ticket on GitHub. Commercial clients can contact us directly via email.

The free and commercial API services of Open-Meteo operate on different servers, leading to slight variations in update times. Please choose the appropriate type below. Note that API calls to the metadata API are not counted toward daily or monthly request limits.

Forecast API

Provider Weather Model Last Model Run Update Available Temporal Resolution Update frequency API
AM ARPAE ARPAP COSMO 2i Loading
COSMO 5m Loading
BOM ACCESS-G 0.15° Loading
CMA GFS Grapes 0.125° Loading
Canadian Weather Service GDPS 0.125° Loading
HRDPS Loading
RDPS Loading
DMI Harmonie AROME Europe Loading
DWD ICON Loading
ICON-D2 Loading
ICON-D2 15min Loading
ICON-EU Loading
ECMWF AIFS 0.25° Loading
IFS 0.25° Loading
JMA GSM 0.5° Loading
MSM 0.05° Loading
KNMI Harmonie AROME Europe Loading
Harmonie AROME Netherlands Loading
Météo-France AROME France 0.025° Loading
AROME France 0.025° 15min Loading
AROME France 0.01 HD° Loading
AROME France 0.01 HD 15min Loading
ARPEGE Europe 0.1° Loading
ARPEGE World 0.25° Loading
MET Norway MET Nordic PP Loading
NOAA NCEP GFS 0.11° Loading
GFS 0.25° Loading
GFS GraphCast 0.25° Loading
HRRR Conus Loading
HRRR Conus 15min Loading
UK Met Office UKMO Global Deterministic 0.09° Loading
UKMO UKV Loading

Historical Weather API

Provider Weather Model Last Model Run Update Available Temporal Resolution Update frequency API
Copernicus ERA5 0.25° Loading
ERA5-Land 0.1° Loading
ERA5-Ensemble 0.25° Loading
ECMWF IFS HRES 9km Loading
IFS Analysis Long-Window 4D Loading

Ensemble API

Provider Weather Model Last Model Run Update Available Temporal Resolution Update frequency API
BOM ACCESS-GE 0.4° Loading
Canadian Weather Service GDPS 0.25° Ensemble Loading
DWD ICON-D2-EPS Loading
ICON-EPS Loading
ICON-EU-EPS Loading
ECMWF IFS 0.25° Ensemble Loading
NOAA NCEP GFS 0.25 Ensemble Loading
GFS 0.25° Ensemble Loading

Air Quality API

Provider Weather Model Last Model Run Update Available Temporal Resolution Update frequency API
CAMS CAMS GLOBAL 0.4° Loading
CAMS Europe 0.1° Loading

Marine API

Provider Weather Model Last Model Run Update Available Temporal Resolution Update frequency API
Météo-France MFWAM 0.08° Loading
SMOC Currents 0.08° Loading
ECMWF WAM 0.25° Loading
NOAA NCEP GFS Wave 0.25° Loading
GFS Wave 0.16 Loading
Copernicus ERA5-Ocean Loading

Metadata API Documentation

You can retrieve the update times for each individual model via the API. However, these times do not directly correlate with the update times in the Forecast API, as Open-Meteo automatically selects the most appropriate weather model for each location (referred to as "Best Match"). The table above provides an API link for each model, returning a JSON object with the following fields:

  • last_run_initialisation_time: The model's initialization time or reference time represented as a Unix timestamp (e.g., 1724796000 for Tue Aug 27, 2024, 22:00:00 GMT+0000).
  • last_run_modification_time: The time when the data download and conversion were completed, which does not indicate when the data became available on the API.
  • last_run_availability_time: The time when the data is actually accessible on the API server. Important: Open-Meteo utilizes multiple redundant API servers, so there may be slight differences between them while the data is being copied. To ensure all API calls use the most recent data, please wait 10 minutes after the availability time.
  • temporal_resolution_seconds: The temporal resolution of the model in seconds. By default, the API interpolates the data to a 1-hour resolution. However, the underlying model may only provide data in 3 or 6-hourly steps. A value of 3600 indicates that the data is 1-hourly.
  • update_interval_seconds: The typical time interval between model updates, such as 3600 seconds for a model that updates every hour.

Additional attributes, such as spatial resolution, area, grid systems, and more, will be added in the future.