# Vucod · Durum

This is a status page, run by nabiz (https://github.com/productdevbook/nabiz).
It probes the services listed on it every minute and keeps ninety days of
history. Monitors marked as a group ("N/M up") stand for hosts that are
served here but named elsewhere; they are counted, never listed.

## Endpoints

- https://status.vucod.com/                 the page, HTML
- https://status.vucod.com/api/status.json  current state, per-monitor uptime and latency, recent events
- https://status.vucod.com/api/history.json ninety days of daily totals per monitor
- https://status.vucod.com/badge.svg        the overall state as a badge
- https://status.vucod.com/feed.xml         state changes and notices as RSS
- https://status.vucod.com/api/notices.json operator-written notices, markdown and rendered
- https://status.vucod.com/health           204 when the status page itself is alive

Every read endpoint takes ?lang= (en, tr, de, es, fr): the page and the
feed translate their words, and notices written for one language are
served only to it — a notice with no language speaks to everyone.

All JSON is read-only, CORS-open, and uncached: what you get is what is
true at the moment you asked. Writing exists too, for the operator:
POST /api/notice with Authorization: Bearer <token> and a JSON body of
{"body": "markdown", "severity": "info|maintenance|degraded|outage",
"lang": "all|en|tr|de|es|fr"}; POST /api/notice/resolve with {"id": n}.

## Reading status.json

"status" is "up", "degraded" or "down" for the whole page. Each monitor
carries "status", "uptime_90d" (percent, null before the first day of
data), and "latency_ms" from the most recent successful probe. Grouped
monitors carry "up" as a tally like "5/6" instead of a latency.