AGSIST Status
Whether each AGSIST data feed is current, checked from your browser when the page opens. If a number on the site looks old, this page tells you whether it is. Where each feed comes from is on the data sources page.
Everything else the site publishes
Checked live from your browser, the same way. Each row says who writes it, how often, and, when a feed is meant to sit still, why.
How this page works. Everything above is checked live, in your browser, when the page loads. Each feed publishes a timestamp; this page reads it and compares it to how often that feed is supposed to update. “Delayed” and “Idle” account for normal rhythms: grain prices don’t move when the board is closed, and there’s no weekday briefing on a Sunday, so neither one shows as a problem.
What it can and can’t see. If this page loaded at all, the AGSIST website is online. What it checks is whether the data behind each tool is current. It cannot see GitHub’s build system directly, so when several feeds go “Delayed” together, it usually means an upstream provider (often GitHub, which builds and publishes the site) is catching up. For GitHub’s own status, see githubstatus.com.
Something looks wrong that this page says is fine? Tell Sig: sig@farmers1st.com.
What it can and can’t see. If this page loaded at all, the AGSIST website is online. What it checks is whether the data behind each tool is current. It cannot see GitHub’s build system directly, so when several feeds go “Delayed” together, it usually means an upstream provider (often GitHub, which builds and publishes the site) is catching up. For GitHub’s own status, see githubstatus.com.
Something looks wrong that this page says is fine? Tell Sig: sig@farmers1st.com.