poztter.net

poztter.net / status

Status.

Network home · Topology · Servers · Ports

Live reachability and version reports for the registered POZ servers. The data below is loaded from status.json, which is written periodically by the network's scrape job.

Loading…
Domain Host Role 7074 7075 7076 Last checked
Loading status…

the status.json schema

{
  "generated_at": "2026-05-03T12:00:00Z",
  "generator": "poz_status_scrape v0.1",
  "servers": [
    {
      "domain":  "poztter.org",
      "host":    "poz1.poztter.org",
      "ip":      "203.0.113.10",
      "role":    "authoritative",
      "ports": {
        "7074": { "open": true,  "version": "poz_server 0.1.0" },
        "7075": { "open": true,  "version": "poz_server 0.1.0" },
        "7076": { "open": true,  "version": "poz_server 0.1.0" }
      },
      "last_checked": "2026-05-03T12:00:00Z"
    }
  ]
}

how the scrape works

  1. Cron job on the poztter.net droplet wakes every N minutes.
  2. For each server in the registry, attempts a TCP connect to each declared port.
  3. For 7075 / 7076, performs a Noise NK handshake and issues a SERIAL query to confirm the server speaks the protocol.
  4. Records the result, including any version string the server reports.
  5. Writes status.json atomically.

Until the scrape job is wired up, this page shows placeholder data from a hand-edited status.json. Treat the indicators as illustrative.

LAST 24 HOURS · poz1.poztter.org · sample data 7074 7075 7076 −24h −18h −12h −6h now reachable unreachable no data populates once the scrape job is wired and writing historical samples to status.json
fig 01 · what the historical view will look like once the scrape job is running. Each port gets one row per server; green is reachable, red is unreachable, the gap shows missing samples.