The forecast for 
Celestia's bridges.
Celestia has ~180 IBC light clients open to other chains, plus Blobstream to Ethereum, Arbitrum and Base. Clients expire silently if nobody relays a header in time — recovering one needs an on-chain governance vote. This tracks every one of them, live, so a problem shows up here before it becomes a proposal.
Top networks by interaction
Ranked by real transfer transactions observed, not just by what has a live channel —
interaction is the signal, connectivity alone isn't. Full breakdown lives in the Chains tab.
Bridge Map
Every dot is a real counterparty chain with a live transfer channel, sized by how
much TIA is actually bridged through it. The feed on the right is built from real signed transfer
transactions — not client health, that's the Chains tab's job.
Blobstream → Ethereum
Read directly from the live SP1Blobstream contract on Ethereum mainnet via
eth_call, cross-checked against Celestia's own current height.
IBC light clients, by counterparty chain
Each card shows its best client — a chain with
one healthy client and ten abandoned ones from old relayer setups is fine, not at risk. Click any card for
the full client list. Abandoned clients are counted, not hidden.
Blobstream lag over time
Every point is this monitor's own reading, taken every 30 minutes — not a
third-party chart. Enough history turns "85 hours behind" from an unexplained number into a trend you can
actually judge. Hover the line for exact values.
Lag growth per hour — last – blobs
Growth rate per hour, full width — flat bars mean the lag's slope never changes, the signature of a relayer that has posted nothing at all rather than one that's merely slow
Real relay events
Not derived from the lag number — this is the actual DataCommitmentStored event
SP1Blobstream emits on Ethereum every time a relayer successfully posts a batch, decoded straight from eth_getLogs.
Public RPC free tiers cap log scans at ~10k blocks per call, so each refresh only scans the last ~1.3 days — but at a 30-min cadence
that window always overlaps the previous one, so no real event is ever missed between runs.
Packets in motion
Client health says a bridge could carry packets; this says whether it does. Every packet relayed into and out of
Celestia on the transfer port, who relays it, how long a round trip takes, and what was sent but never acknowledged.
Channels carrying packets
TIA moving across bridges
Both sides of each bridge
Escrow against supply
Sent, never acknowledged
Who relays Celestia
Transactions
Every real IBC transfer this monitor has observed via tx_search --
not a derived balance delta, each card below is one real signed transaction.