billing & credits gateway

node id: 9a115815

regional engine • global cluster

historical telemetry trace

rolling 100 scan window

verification status	pulse latency	diagnostic message	trace timestamp
operational	1601 ms pulse	Node pulse nominal.	2 days ago k8s-node-99
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/dashboard/user/payment	3 days ago k8s-node-42
Critical Node Failure Trace Trace ID: d58072be2820 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/dashboard/user/payment { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-42", "memory_delta": "120MB" } 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 5007 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/dashboard/user/payment	3 days ago k8s-node-14
Critical Node Failure Trace Trace ID: 9e3cfc48eccf cURL error 28: Operation timed out after 5007 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/dashboard/user/payment { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-14", "memory_delta": "183MB" } 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/dashboard/user/payment	3 days ago k8s-node-43
Critical Node Failure Trace Trace ID: b4a528955b84 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/dashboard/user/payment { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-43", "memory_delta": "82MB" } 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/dashboard/user/payment	3 days ago k8s-node-84
Critical Node Failure Trace Trace ID: 996a7fa078cc 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/dashboard/user/payment { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-84", "memory_delta": "173MB" } 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/dashboard/user/payment	3 days ago node-72
Critical Node Failure Trace Trace ID: 3dc4876f3f08 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/dashboard/user/payment { "kernel_ver": "6.4.2-stable", "node_tier": "core", "memory_delta": "71MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5010 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/dashboard/user/payment	3 days ago node-18
Critical Node Failure Trace Trace ID: d1f255a373a3 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/dashboard/user/payment { "kernel_ver": "6.4.2-stable", "node_tier": "core", "memory_delta": "-28MB" } 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/dashboard/user/payment	3 days ago k8s-node-47
Critical Node Failure Trace Trace ID: 839ab46820b5 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/dashboard/user/payment { "worker_id": "k8s-node-47", "load_avg": 6.5 } 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 5000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/dashboard/user/payment	3 days ago k8s-node-62
Critical Node Failure Trace Trace ID: 20f07591c6fc 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/dashboard/user/payment { "worker_id": "k8s-node-62", "load_avg": 3.2 } 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/dashboard/user/payment	3 days ago node-50
Critical Node Failure Trace Trace ID: 9b8619251a19 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/dashboard/user/payment 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/dashboard/user/payment	3 days ago node-35
Critical Node Failure Trace Trace ID: 093f65e080a2 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/dashboard/user/payment Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle