Health & Connectivity
Can we reach it, does it answer, and is the answer correct — the checks that run before you trust any other dashboard
Endpoints checked
96
Reachable
92
Failing
4
Median RTT
38ms
Platform self-check
What the backend reports about its own dependencies. A store falling back to memory is the check worth watching — writes look successful and vanish on the next cold start.
| API | ok |
| Record store (DynamoDB) | persistent |
| User store (DynamoDB) | persistent |
| Elasticsearch | green |
| Kafka event spine | no broker |
| Service graph (Neo4j) | connected |
Ad-hoc probe
Run a one-off reachability check from the platform's network, not your laptop's — useful when a connector claims a host is unreachable.
connect payments-prod.cluster-us-east-1.rds.amazonaws.com:5432
resolved 10.42.8.19 in 4ms
tcp established in 11ms
tls handshake 24ms · total 39ms
Monitored endpoints
Health checks and reachability probes across every environment this organization runs
No matching results
