Status

Abstract

vet402's own uptime, measured the same way the rest of this site measures anything: no claim without a sample behind it. Nothing on a schedule writes these rows — a request to /api/health writes one, at most every five minutes unless the status changed — so a quiet day carries fewer samples and a silent day carries none. Some of those requests are ours: a production check calls the endpoint on the hour and the half hour. It is the sample most likely to be red, because it is the only one certain to outlive the probe's one-minute memo rather than replay it. A missing observation is never reported as "ok."

1.Current status

ok, last sampled 2026-11-14 06:43 UTC. Page built 2026-11-14 06:47 UTC.

2.Data freshness, by chain

Status above says whether the service answers. This says how current the data behind it is. For each chain, when vet402's settlements index last saved its place, how far that place is behind the newest block (the time between the two blocks' own timestamps), and whether the chain's block interval still matches the number vet402's time windows assume. A data lag is not an outage, so it does not change the status above. Read at most two minutes before this page was built.

Settlements index freshness by chain
Chain	Index last saved	Behind the newest block	Block interval
Base	2026-11-14 05:03 UTC	114 min	200 ms measured, 200 ms expected
Arc	2026-11-14 04:21 UTC	2.5 h	506 ms measured, 508 ms expected
Celo	2026-11-14 04:21 UTC	2.5 h	1.00 s measured, 1.00 s expected
Arbitrum One	2026-11-14 04:21 UTC	2.5 h	312 ms measured, 278 ms expected
Avalanche C-Chain	not indexed yet	not measured	831 ms measured, 970 ms expected
BNB Chain	2026-11-14 04:21 UTC	2.4 h	451 ms measured, 450 ms expected
Tempo	2026-11-14 04:21 UTC	2.4 h	538 ms measured, 538 ms expected
Solana	not indexed yet	not measured	—
XRPL	2026-11-12 13:02 UTC	per payee	—

Reading the chains…

3.Last 30 days, by day

Monitoring since 2026-08-15 20:35 UTC. A day with no row below was not observed, which is not the same claim as "ok."

Daily status samples over the last 30 days
Day	Worst observed	Samples	ok	degraded	error
2026-11-14	degraded	83	79	4	0
2026-11-13	degraded	263	246	17	0
2026-11-12	degraded	274	235	39	0
2026-11-11	degraded	289	268	21	0
2026-11-10	degraded	269	259	10	0
2026-11-09	degraded	261	243	18	0
2026-11-08	error	275	246	25	4
2026-11-07	degraded	528	203	325	0
2026-11-06	degraded	394	141	253	0
2026-11-05	degraded	253	226	27	0
2026-11-04	ok	240	240	0	0
2026-11-03	ok	247	247	0	0
2026-11-02	degraded	253	249	4	0
2026-11-01	degraded	244	242	2	0
2026-10-31	ok	240	240	0	0
2026-10-30	ok	243	243	0	0
2026-10-29	degraded	244	240	4	0
2026-10-28	ok	244	244	0	0
2026-10-27	ok	245	245	0	0
2026-10-26	degraded	253	251	2	0
2026-10-25	degraded	269	260	9	0
2026-10-24	degraded	247	245	2	0
2026-10-23	ok	178	178	0	0
2026-10-22	degraded	221	219	2	0
2026-10-21	degraded	284	283	1	0
2026-10-20	ok	261	261	0	0
2026-10-19	ok	247	247	0	0
2026-10-18	ok	255	255	0	0
2026-10-17	ok	245	245	0	0
2026-10-16	degraded	253	251	2	0
2026-10-15	ok	181	181	0	0

4.What ok / degraded / error mean here

The same three values the observatory uses, computed by the same probe /api/health runs: ok — scoring and payee lookups both answered. degraded — the upstream indexer is behind, so a lookup may return "not verifiable" instead of a number. error — scoring is failing outright. A day is marked by its worst sample, not an average, so one bad five minutes is never hidden inside a mostly-good day.