Skip to content

open router gateway

node id: 68d30a95

regional engine • edge-node

historical telemetry trace

rolling 100 scan window
verification status pulse latency diagnostic message trace timestamp
degraded
0 ms pulse
Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive.
2 days ago k8s-node-65
Critical Node Failure Trace
Trace ID: 8d6dc35e506f

Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive. 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-65",
    "memory_delta": "-49MB"
}
Resolver Suggestion: check upstream gateway for drift in node 8d6dc3
Awaiting recovery cycle
degraded
0 ms pulse
Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive.
3 days ago k8s-node-5
Critical Node Failure Trace
Trace ID: 1e056d2b0ebd

Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive. 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-5",
    "memory_delta": "111MB"
}
Resolver Suggestion: check upstream gateway for drift in node 1e056d
Awaiting recovery cycle
degraded
0 ms pulse
Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive.
3 days ago k8s-node-85
Critical Node Failure Trace
Trace ID: dd8eb9f23fbd

Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive. 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-85",
    "memory_delta": "-11MB"
}
Resolver Suggestion: check upstream gateway for drift in node dd8eb9
Awaiting recovery cycle
degraded
0 ms pulse
Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive.
3 days ago k8s-node-19
Critical Node Failure Trace
Trace ID: 81e74d678581

Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive. 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-19",
    "memory_delta": "98MB"
}
Resolver Suggestion: check upstream gateway for drift in node 81e74d
Awaiting recovery cycle
partial outage
3005 ms pulse
Integrity Threshold Crossed: lang_missing • endpoint_unreachable
3 days ago k8s-node-80
Critical Node Failure Trace
Trace ID: 1ecfb463472e

Integrity Threshold Crossed: lang_missing • endpoint_unreachable 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-80",
    "memory_delta": "51MB"
}
Resolver Suggestion: filesystem reachability failure • check module installation path
Awaiting recovery cycle
partial outage
3004 ms pulse
Integrity Threshold Crossed: lang_missing • endpoint_unreachable
3 days ago k8s-node-17
Critical Node Failure Trace
Trace ID: 851ddf5058cf

Integrity Threshold Crossed: lang_missing • endpoint_unreachable 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-17",
    "memory_delta": "182MB"
}
Resolver Suggestion: filesystem reachability failure • check module installation path
Awaiting recovery cycle
degraded
0 ms pulse
Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive.
3 days ago node-87
Critical Node Failure Trace
Trace ID: 63538fe6ef33

Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive. 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "memory_delta": "106MB"
}
Resolver Suggestion: check upstream gateway for drift in node 63538f
Awaiting recovery cycle
degraded
8 ms pulse
Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive.
3 days ago node-60
Critical Node Failure Trace
Trace ID: 3c7781a36bcd

Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive. 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "memory_delta": "8MB"
}
Resolver Suggestion: check upstream gateway for drift in node 3c7781
Awaiting recovery cycle
major outage
4004 ms pulse
cURL error 28: Operation timed out after 4001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/dashboard/user/openrouter
3 days ago k8s-node-4
Critical Node Failure Trace
Trace ID: 34ed066df378

cURL error 28: Operation timed out after 4001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/dashboard/user/openrouter 

{
    "worker_id": "k8s-node-4",
    "load_avg": 7.6
}
Resolver Suggestion: check upstream gateway for drift in node 34ed06
Awaiting recovery cycle
major outage
4003 ms pulse
cURL error 28: Operation timed out after 4000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/dashboard/user/openrouter
3 days ago k8s-node-3
Critical Node Failure Trace
Trace ID: 48aedb8880ca

cURL error 28: Operation timed out after 4000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/dashboard/user/openrouter 

{
    "worker_id": "k8s-node-3",
    "load_avg": 6.4
}
Resolver Suggestion: check upstream gateway for drift in node 48aedb
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/openrouter
3 days ago node-18
Critical Node Failure Trace
Trace ID: a8baa56554f9

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/openrouter

Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift
Awaiting recovery cycle

integrity analysis

historical telemetry suggests this node maintains a 0.0% availability factor across the active 30-day window. autonomous cycling active.

real-time node metrics

current verification state

degraded

avg pulse

1730ms

peak drift

5004ms

node resource flux

cpu load 1.0%

node stability index

43% confidence
24h pulse trend

deep throughput

10,963 total reqs

+5% variance from baseline

operational success rate

0.0%

ai diagnostic synopsis

anomaly detected: the last verification trace encountered a critical timeout protocol. this typically indicates high egress congestion or an unmanaged upstream drop.

raw_trace: Upstream Cluster Dependency Alert: [Standard API (v1)] is currently unresponsive.
Cart