Skip to content

flux pro gateway

node id: fc490ca4

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-84
Critical Node Failure Trace
Trace ID: 6395ebd0f4b4

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

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

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

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

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

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

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

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-1",
    "memory_delta": "178MB"
}
Resolver Suggestion: check upstream gateway for drift in node 795c7a
Awaiting recovery cycle
partial outage
3019 ms pulse
Integrity Threshold Crossed: lang_missing • endpoint_unreachable
3 days ago k8s-node-72
Critical Node Failure Trace
Trace ID: 08419be89740

Integrity Threshold Crossed: lang_missing • endpoint_unreachable 

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

Integrity Threshold Crossed: lang_missing • endpoint_unreachable 

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

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

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

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

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "memory_delta": "10MB"
}
Resolver Suggestion: check upstream gateway for drift in node 1651cf
Awaiting recovery cycle
major outage
4008 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/fluxpro
3 days ago k8s-node-84
Critical Node Failure Trace
Trace ID: fe73f687e5bc

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

{
    "worker_id": "k8s-node-84",
    "load_avg": 3.1
}
Resolver Suggestion: check upstream gateway for drift in node fe73f6
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/fluxpro
3 days ago k8s-node-26
Critical Node Failure Trace
Trace ID: ad13a2a07ca4

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

{
    "worker_id": "k8s-node-26",
    "load_avg": 6.1
}
Resolver Suggestion: check upstream gateway for drift in node ad13a2
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/dashboard/user/fluxpro
3 days ago node-55
Critical Node Failure Trace
Trace ID: 140f6969d521

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

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/fluxpro
3 days ago node-55
Critical Node Failure Trace
Trace ID: 32bb90e8976a

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

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

5004ms

node resource flux

cpu load 1.0%

node stability index

48% confidence
24h pulse trend

deep throughput

6,767 total reqs

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