status.guardyn.dev
all systems operational
four components, checked from inside the server, once a minute
status unknown
This page last wrote itself at 2026-08-31 17:59 UTC and has not refreshed since. Nothing below has been checked since then. Treat it as unknown, not as green.
checked at 2026-08-31 17:59 UTC · every 60s · all times UTC
components
This pagestatus.guardyn.dev operational
reachableserved
respondingregenerated
this page is a component of itself. ‘served’ means a separate check fetched it from nginx and found it whole.
90 days ago100.00% available · 1m not measuredtoday
Guardyn appguardyn.dev operational
reachableyes, valid certificate
respondinghealth check ok
90 days ago100.00% availabletoday
APIapi.guardyn.dev operational
reachableyes, valid certificate
respondingready, schema current
90 days ago100.00% availabletoday
Edge dashboardweb.guardyn.dev operational
reachableyes, valid certificate
respondingpage loads
checked by page load only — a working shell over a broken data layer would still read as up here.
90 days ago100.00% availabletoday
not yet in service
These run, and they are being recorded from today, but no customer traffic depends on them yet — so they are not part of the state above, and status.json marks them in_service: 0.
· Edge network edge.guardyn.dev — running · no zone is configured, so it answers 404, which is the correct answer
· Authoritative DNS ns1.guardyn.dev — running · not delegated yet

recent changes

2026-08-31 17:21This pageunknown → up2m 40s · brief