Health endpoint
External monitors can test /healthz without consuming a customer link.
LINKTIMER GUIDE
LinkTimer exposes machine-readable health, public component status, destination monitoring, daily backup automation, and a documented restore drill so reliability can be verified instead of merely claimed.
External monitors can test /healthz without consuming a customer link.
A repeat-safe setup command creates daily Firestore backups with defined retention.
Restore drills use a separate database and preserve evidence before cleanup.
Point an independent monitor at the health endpoint and public status page.
Restore a managed backup into a new database before controlled cutover.
Inspect current targets, evidence, and limitations without assuming a formal SLA.
Run live verification after every production deployment.
Create the daily managed Firestore schedule.
Check health from outside Google Cloud and alert the owner.
Measure recovery time and record the outcome.
These controls do not constitute a contractual SLA or independent certification. Availability history, external monitoring evidence, and restore-drill results must be accumulated in production.
Yes. It returns a no-store JSON response and verifies Firestore reachability.
The supplied default schedule is daily with 14-day retention.
No. The runbook requires restoring into a separate database first.
No formal uptime percentage is claimed until independent monitoring and a contractual support policy exist.
These links provide additional context from the destination provider or recognized security resources. External sites are responsible for their own content and policies.
Choose the expiration rule, confirm the destination, and share the generated LinkTimer URL or QR code.
Open the LinkTimer creator