SITE STATUS

What the numbers mean

There is no health checker behind this page. Your browser does what a reader's does: follow each model's latest.json, follow the catalog it points to, and fetch a real frame out of it. That is the test that catches the failures that matter here, which are the ones where nothing errors — a pointer that stops advancing because an ingest is failing quietly upstream, a catalog that resolves but whose frames do not.

Age is the age of the newest cycle, not the time since the last ingest pass: an ingest that runs hourly and correctly finds nothing new is healthy; one whose newest cycle is a day old is not. The healthy peak is adoption lag + one cycle interval, and the lag is not small, because every feed here is adopted only once its cycle is complete and a global run takes hours to finish, reach the source host and render. Measured on 23–24 September 2026, a cycle reached the site 7 to 13 hours after its nominal time, on every model. So a newest cycle nineteen hours old is the ordinary moment just before the next one lands, and twenty is the first number that means a cycle was missed.

All four

Four cycles a day, 00, 06, 12 and 18Z — amber at 20 h, red at 26 h, which is a second cycle missed

Reaches

The valid time of the run's last step. HRES and the ensemble run to +144 h at 06Z and 18Z and +360 h at 00Z and 12Z, so it moves by six days from one run to the next and that is correct

Frames

Steps in the newest run, and images across all its fields

Runs

How many cycles that model's run picker can switch between

Frame

Whether the last image of the newest run answered 200

The page re-checks every five minutes while it is open. The pointers are cached at the edge for about a minute, so a cycle that has just landed can take that long to show here.