auth & security gateway

node id: c0c7c76d

regional engine • global cluster

historical telemetry trace

rolling 100 scan window

verification status	pulse latency	diagnostic message	trace timestamp
operational	1283 ms pulse	Node pulse nominal.	2 days ago k8s-node-38
major outage	5004 ms pulse	cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago k8s-node-81
Critical Node Failure Trace Trace ID: dc5689792e08 cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-81", "memory_delta": "35MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5003 ms pulse	cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago k8s-node-15
Critical Node Failure Trace Trace ID: 35cf8659cfcb cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-15", "memory_delta": "162MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5005 ms pulse	cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago k8s-node-57
Critical Node Failure Trace Trace ID: 5487315b1286 cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-57", "memory_delta": "41MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5004 ms pulse	cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago k8s-node-16
Critical Node Failure Trace Trace ID: 44c4c17332ca cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-16", "memory_delta": "23MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5009 ms pulse	cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago node-80
Critical Node Failure Trace Trace ID: a760880003e7 cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login { "kernel_ver": "6.4.2-stable", "node_tier": "core", "memory_delta": "-6MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5004 ms pulse	cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago node-65
Critical Node Failure Trace Trace ID: 8fe0093bb30d cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login { "kernel_ver": "6.4.2-stable", "node_tier": "core", "memory_delta": "97MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5005 ms pulse	cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago k8s-node-76
Critical Node Failure Trace Trace ID: 0e01938fc48a cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login { "worker_id": "k8s-node-76", "load_avg": 2.7 } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5003 ms pulse	cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago k8s-node-49
Critical Node Failure Trace Trace ID: 57aeee35c982 cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login { "worker_id": "k8s-node-49", "load_avg": 1.6 } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5006 ms pulse	cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago node-15
Critical Node Failure Trace Trace ID: 069059b7ef84 cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5004 ms pulse	cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login	3 days ago node-94
Critical Node Failure Trace Trace ID: 72b32a1f754b cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/login Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle