Healthy Checks
-- / --
Healthy Reporting PoPs
-- / --
Webhook Latency
--ms
DB Latency
--ms
Core Services
Platform
Dashboard API and core services
Checking...
Webhook Ingestion
Incoming webhook receiver and queue
Checking...
Database
PostgreSQL data store
Checking...
Edge Network PoPs
Loading PoP data...
Your Connection
Detecting connection...
Infrastructure Configuration
Primary Origin
EWR — New Jersey
Documented primary role for the dashboard, worker, PostgreSQL, and monitoring. Current health is reported by the checks above.
Container deployment target
PostgreSQL primary role
Configured primary
k3s Failover
MCI — Kansas City
Documented Kubernetes failover target. This static diagram does not prove current readiness or automatic switchover.
Kubernetes deployment target
Failover behavior requires a tested drill
Configured standby
Configured Failover Path
Edge PoP
→
Origin (EWR)
health check fails
→
k3s Failover (MCI)
verify before use
Ingress health depends on reporting telemetry
Recovery behavior is verified separately