What FullCup.ai knows about its own health
Facts the system actually produces, each stamped with when. Nothing here is a promise or a target.
Ledger chain
Verified
2 events checked, link by link, 17h ago · 2026-09-28 06:00 UTC
Last request through the proxy
18d ago · 2026-09-10 23:30 UTC
24 signed receipts in the ledger
Reference price
17h ago · 2026-09-28 06:00 UTC
refreshed daily; a stale price makes cost estimates drift, not checkout break
Ledger backup
a copy kept off the ledger's databaseLast backup
17h ago · 2026-09-28 06:00 UTC
225 events copied
Backup check
Confirmed
225 events confirmed, 17h ago · 2026-09-28 06:00 UTC
This check rereads the saved copy and rebuilds its chain from that file alone, without asking the database that produced it. That is what makes it a check, not the system talking about itself.
Why there is no uptime percentage here
the honest answer is that it is not measuredAn uptime figure needs someone probing from outside, over time. FullCup.ai does not collect that, so publishing a number would mean computing it from inside the thing being measured — the same problem as a platform vouching for itself, which this product rejects for receipts and rejects here too.
What you can check instead: the chain above is verifiable by anyone, and every receipt carries a signature you can validate on your own machine.