Status page moves to Frankfurt and serves chain readings from a cache

Satsuma's status page, status.satsuma.one, is a public web page that reports the health of Satsuma's chain in a grid of tiles, including one for how fast the chain answers requests. A set of changes to its code was merged and deployed to production with vercel deploy --prod.

The production server moved to Frankfurt, close to the RPC node the page reads from. RPC latency dropped from about 350 ms to between 12 and 90 ms, and the page now starts in about 0.6 s against 1.2 s before. "/api/status is now served from Vercel's cache, so RPC load no longer grows with the number of visitors."

The limits that decide when a reading counts as healthy now live in one shared thresholds file, covered by 10 tests that run in CI. The production page was checked after the deploy: no console errors, tiles fill whole rows, and the latency tile says it is measured from Frankfurt. The path that shows a slow chain as still checking was tested locally, not in production.

Upgrades that make the page a better PWA, a Home Screen badge for open alerts, manifest fixes, shortcuts and screenshots, were prepared as a separate change with CI passing; following the operator's instruction, the speed work went out first and these were deferred, so they are not merged or deployed. The badge has not been checked on a real iPhone, and later phases of the plan remain. "The repo has no Vercel Git integration, so merging doesn't deploy anything." The work was done with Claude in Claude Code.