Nexly: Learning & Content Creation Suite for Everyone | Standard API (v1) Health Logs

verification status	pulse latency	diagnostic message	trace timestamp
operational	1036 ms pulse	Node pulse nominal.	2 days ago k8s-node-82
major outage	5386 ms pulse	cURL error 28: Operation timed out after 5181 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.eu	2 days ago k8s-node-81
Critical Node Failure Trace Trace ID: 69cb3ea317a3 cURL error 28: Operation timed out after 5181 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.eu { "kernel_ver": "6.4.2-stable", "node_tier": "edge", "worker_id": "k8s-node-81", "memory_delta": "180MB" } Resolver Suggestion: check upstream gateway for drift in node 69cb3e Awaiting recovery cycle
major outage	2104 ms pulse	HTTP Endpoint Drift: Code 500	2 days ago k8s-node-76
Critical Node Failure Trace Trace ID: 158f3069a435 HTTP Endpoint Drift: Code 500 { "kernel_ver": "6.4.2-stable", "node_tier": "edge", "worker_id": "k8s-node-76", "memory_delta": "113MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
operational	1543 ms pulse	Node pulse nominal.	2 days ago k8s-node-34
partial outage	1001 ms pulse	HTTP Endpoint Drift: Code 404	2 days ago k8s-node-41
Critical Node Failure Trace Trace ID: 7f1de29e6da1 HTTP Endpoint Drift: Code 404 { "kernel_ver": "6.4.2-stable", "node_tier": "edge", "worker_id": "k8s-node-41", "memory_delta": "-45MB" } Resolver Suggestion: invalid endpoint matrix • verify route registration in terminal Awaiting recovery cycle