How it works

Whether Terra is running, and if not, what is wrong. Read from the chain through public endpoints; nothing is signed.

When something counts as a problem

Blocks: The age of the latest block. Up to 30 seconds is normal (a block takes about six), up to 120 seconds is slow, longer means the chain has stopped. At a scheduled upgrade height a stop is expected and named as such.
Upgrades: A software upgrade that has passed (the chain’s current plan), or one still in a vote. The countdown is the blocks left times the average block time of the last 1,000 blocks, so it drifts a little. At that height blocks pause until validators holding two thirds of the stake restart on the new version, usually within minutes. Transactions wait until blocks resume; nothing is lost.
Validators: Each active validator’s missed blocks in the slashing window, against the allowance before it is jailed: out of the active set for a while, with a small part of its stake slashed. A validator past 50% of its allowance is near jail. Validators jailed lately and still leaving the active set are listed too; one that signed twice is tombstoned, removed for good.
Bridges: Per IBC channel: whether it is open and its light client active, when a relayer last brought a packet in and an acknowledgement back, how many packets Terra sent that are still unacknowledged, and when the light client expires if nobody updates it. A main bridge needs attention when its client expires within three days, or packets have waited more than an hour but less than a week. Packets waiting for weeks were usually abandoned: their timeout passed and nobody cleared them.
Endpoints: Every RPC and REST endpoint in the Cosmos chain registry, plus a few that apps use and it does not list, asked for the latest block. More than 20 blocks behind the best answer counts as behind. Browser apps: whether web pages on other sites may call it (CORS). Keeps blocks since: how far back its history goes, and so which old transactions it can look up.
Openfields apps: Each app’s page and data route, from outside.

Where it is read from

Blocks and software: /cosmos/base/tendermint/v1beta1/blocks/latest, /node_info
Upgrades: /cosmos/upgrade/v1beta1/current_plan, /cosmos/gov/v1/proposals?proposal_status=2 and the proposal’s tally
Validators: /cosmos/staking/v1beta1/validators, /cosmos/slashing/v1beta1/signing_infos, /cosmos/slashing/v1beta1/params
Bridges: /ibc/core/channel/v1/channels/…/client_state, /ibc/core/client/v1/client_status/…, /packet_commitments, and transaction searches for recv_packet, acknowledge_packet and send_packet. Channels come from the Cosmos chain registry.
Endpoint list: github.com/cosmos/chain-registry/terra2/chain.json

Two vantage points

The page reads live from this site’s server: the chain every 30 seconds, validators and endpoints every two minutes, bridges every four. A hidden tab, or one left untouched for ten minutes, stops asking and catches up when you return.

Separately, every ten minutes a check on GitHub’s machines reads the chain, every endpoint and each Openfields app from outside and writes one line to a public log in git. The last seven days and the apps’ uptime are that log; any later edit to it would show in git.

The browser test sends requests from your browser straight to each endpoint, so those providers see them.

API

/api/status: The whole picture in one answer, open to any origin.
Per group: /api/chain, /api/validators, /api/ibc, /api/endpoints, /api/apps, /api/history
/api/badge: An SVG badge, for a README or a website.

Who runs it

Openfields runs it independently. It is not affiliated with Terraform Labs, the Phoenix Directive, or any validator, relayer or endpoint provider named on it. People behind Openfields also run a Terra validator; it is shown by the same rules as every other. No cookies, no accounts, no analytics. The code is open, MIT licensed.