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-09-30 00:37 UTC. Page built 2026-09-30 00:38 UTC.
2.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."
| Day | Worst observed | Samples | ok | degraded | error |
|---|---|---|---|---|---|
| 2026-09-30 | ok | 8 | 8 | 0 | 0 |
| 2026-09-29 | ok | 272 | 272 | 0 | 0 |
| 2026-09-28 | ok | 251 | 251 | 0 | 0 |
| 2026-09-27 | ok | 243 | 243 | 0 | 0 |
| 2026-09-26 | ok | 241 | 241 | 0 | 0 |
| 2026-09-25 | ok | 211 | 211 | 0 | 0 |
| 2026-09-24 | ok | 242 | 242 | 0 | 0 |
| 2026-09-23 | degraded | 246 | 239 | 7 | 0 |
| 2026-09-22 | ok | 128 | 128 | 0 | 0 |
| 2026-09-21 | ok | 89 | 89 | 0 | 0 |
| 2026-09-20 | ok | 72 | 72 | 0 | 0 |
| 2026-09-19 | degraded | 85 | 67 | 18 | 0 |
| 2026-09-18 | degraded | 84 | 53 | 31 | 0 |
| 2026-09-17 | degraded | 77 | 45 | 32 | 0 |
| 2026-09-16 | degraded | 86 | 54 | 32 | 0 |
| 2026-09-15 | degraded | 72 | 39 | 33 | 0 |
| 2026-09-14 | degraded | 79 | 44 | 35 | 0 |
| 2026-09-13 | degraded | 205 | 138 | 67 | 0 |
| 2026-09-12 | degraded | 192 | 120 | 72 | 0 |
| 2026-09-11 | degraded | 182 | 127 | 55 | 0 |
| 2026-09-10 | degraded | 196 | 135 | 61 | 0 |
| 2026-09-09 | degraded | 258 | 213 | 45 | 0 |
| 2026-09-08 | error | 327 | 272 | 18 | 37 |
| 2026-09-07 | error | 278 | 248 | 15 | 15 |
| 2026-09-06 | ok | 55 | 55 | 0 | 0 |
| 2026-09-05 | ok | 73 | 73 | 0 | 0 |
| 2026-09-04 | degraded | 169 | 166 | 3 | 0 |
| 2026-09-03 | error | 54 | 51 | 2 | 1 |
| 2026-09-02 | degraded | 211 | 200 | 11 | 0 |
| 2026-09-01 | ok | 80 | 80 | 0 | 0 |
| 2026-08-31 | ok | 68 | 68 | 0 | 0 |
3.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.