edge gateway (cdn) gateway

node id: 67c6a1e7

regional engine • global cluster

historical telemetry trace

rolling 100 scan window

verification status	pulse latency	diagnostic message	trace timestamp
operational	5342 ms pulse	Node pulse nominal.	2 days ago k8s-node-55
major outage	5142 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/	3 days ago k8s-node-88
Critical Node Failure Trace Trace ID: 1905aedab9bf 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/ { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-88", "memory_delta": "117MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5112 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/	3 days ago k8s-node-61
Critical Node Failure Trace Trace ID: 96ea64f3a1aa 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/ { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-61", "memory_delta": "125MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5102 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/	3 days ago k8s-node-16
Critical Node Failure Trace Trace ID: 5dd9db5e033d 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/ { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-16", "memory_delta": "190MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5103 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/	3 days ago k8s-node-93
Critical Node Failure Trace Trace ID: c3992e9a68c5 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/ { "kernel_ver": "6.4.2-stable", "node_tier": "core", "worker_id": "k8s-node-93", "memory_delta": "98MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5081 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/	3 days ago node-59
Critical Node Failure Trace Trace ID: 2d6cc4b2d139 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/ { "kernel_ver": "6.4.2-stable", "node_tier": "core", "memory_delta": "58MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5292 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/	3 days ago node-73
Critical Node Failure Trace Trace ID: b9228e0962a7 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/ { "kernel_ver": "6.4.2-stable", "node_tier": "core", "memory_delta": "173MB" } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5097 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/	3 days ago k8s-node-51
Critical Node Failure Trace Trace ID: 07cdfd23373b 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/ { "worker_id": "k8s-node-51", "load_avg": 7.5 } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5022 ms pulse	cURL error 28: Resolving timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public	3 days ago k8s-node-76
Critical Node Failure Trace Trace ID: 9cfdf10e8fc0 cURL error 28: Resolving timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public { "worker_id": "k8s-node-76", "load_avg": 6.7 } Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5088 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/	3 days ago node-22
Critical Node Failure Trace Trace ID: da4fb5c6e93e 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/ Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle
major outage	5141 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/	3 days ago node-26
Critical Node Failure Trace Trace ID: a684eceee76f 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/ Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift Awaiting recovery cycle