IsobarNWP archive

Model archive

Every cycle, kept, and actually queryable

Operational forecasts and reanalyses from nine centres, rechunked into Zarr so you can ask for one variable over one basin instead of pulling a 4 TB run.

 18 PB archive 9 TB added daily cycles online in 12 min
Traffic · last 24hstreaming
9.0Tbps
peak egress
88.0%
cache hit
11101111110110
01ingest-ams-236 nodes · 4.9 Gbpslive
02shard-ams-826 nodes · 39.6 Gbpslive
03ingest-fra-718 nodes · 41.6 Gbpslive
04shard-gru-833 nodes · 10.4 Gbpslive
18.2PB
archive size
9.1TB
added every day
9
forecast centres
12min
cycle to queryable

Why this is not just a file server

Rechunked for the question you ask

GRIB is chunked by field. Time-series questions want the opposite. We store both layouts, so a 40-year series at one point is 200 ms, not 200 hours.

Subset before you transfer

Variable, level, time range, bounding box, ensemble member. The API returns exactly that, in Zarr, NetCDF or GRIB2.

Complete cycles

Not a rolling ten-day window. Every operational cycle since 2016 is retained, including the ones the originating centre has deleted.

Ensembles included

All members, all perturbations, not just the control run and the mean.

Reanalyses too

ERA5 and its land and single-level products, regional reanalyses, and the CMIP6 subset most people actually use.

Metadata that survives

CF conventions, original GRIB keys retained as attributes, and a provenance record for every rechunking step.

Ingest

Daily volume by centre
1ECMWF1NCEP1DWD1MF1UKMO1JMA1CMC0BOM1CMA1ERA51CERRA0COSMO1HARMONIE0other
9.1 TB
Daily
38
Cycles per day
4.2 TB
Largest single run
since 2016
Retention

Common questions

Most of it, yes — for the last few days, in GRIB, one file at a time, with per-centre quotas. We keep the whole history and make it queryable. That is the difference you are paying for.