Skip to content

ai video pro gateway

node id: d1fe173d

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-77
Critical Node Failure Trace
Trace ID: ca75910166da

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

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

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

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

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

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

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

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-53",
    "memory_delta": "158MB"
}
Resolver Suggestion: check upstream gateway for drift in node b86e8d
Awaiting recovery cycle
partial outage
3008 ms pulse
Integrity Threshold Crossed: lang_missing • endpoint_unreachable
3 days ago k8s-node-5
Critical Node Failure Trace
Trace ID: 2dace78f80bc

Integrity Threshold Crossed: lang_missing • endpoint_unreachable 

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

Integrity Threshold Crossed: lang_missing • endpoint_unreachable 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-41",
    "memory_delta": "-35MB"
}
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-22
Critical Node Failure Trace
Trace ID: 94c7bb58efc3

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

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

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

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "memory_delta": "44MB"
}
Resolver Suggestion: check upstream gateway for drift in node 42998c
Awaiting recovery cycle
major outage
4004 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/aivideopro
3 days ago k8s-node-74
Critical Node Failure Trace
Trace ID: c3e878e27f52

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

{
    "worker_id": "k8s-node-74",
    "load_avg": 5.5
}
Resolver Suggestion: check upstream gateway for drift in node c3e878
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/aivideopro
3 days ago k8s-node-38
Critical Node Failure Trace
Trace ID: 138bb0696595

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

{
    "worker_id": "k8s-node-38",
    "load_avg": 4.3
}
Resolver Suggestion: check upstream gateway for drift in node 138bb0
Awaiting recovery cycle
major outage
5012 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/aivideopro
3 days ago node-37
Critical Node Failure Trace
Trace ID: 8f8551796779

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

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/aivideopro
3 days ago node-75
Critical Node Failure Trace
Trace ID: 2b24d495052a

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

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

2004ms

peak drift

5012ms

node resource flux

cpu load 3.0%

node stability index

47% confidence
24h pulse trend

deep throughput

7,053 total reqs

+3% 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