Skip to content

mailchimp gateway

node id: d2ddea18

regional engine • edge-node

historical telemetry trace

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

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

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

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

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

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

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

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

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-62",
    "memory_delta": "159MB"
}
Resolver Suggestion: check upstream gateway for drift in node b0b183
Awaiting recovery cycle
partial outage
3004 ms pulse
Integrity Threshold Crossed: lang_missing • endpoint_unreachable
3 days ago k8s-node-16
Critical Node Failure Trace
Trace ID: e995f98d5696

Integrity Threshold Crossed: lang_missing • endpoint_unreachable 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-16",
    "memory_delta": "192MB"
}
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-98
Critical Node Failure Trace
Trace ID: 10a5ab2db37f

Integrity Threshold Crossed: lang_missing • endpoint_unreachable 

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "worker_id": "k8s-node-98",
    "memory_delta": "-32MB"
}
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-88
Critical Node Failure Trace
Trace ID: 97e8527feaf7

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

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

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

{
    "kernel_ver": "6.4.2-stable",
    "node_tier": "edge",
    "memory_delta": "41MB"
}
Resolver Suggestion: check upstream gateway for drift in node d61e4b
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/mailchimp
3 days ago k8s-node-7
Critical Node Failure Trace
Trace ID: 371bce7dc838

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

{
    "worker_id": "k8s-node-7",
    "load_avg": 4
}
Resolver Suggestion: check upstream gateway for drift in node 371bce
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/mailchimp
3 days ago k8s-node-77
Critical Node Failure Trace
Trace ID: 357a6fdf7642

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

{
    "worker_id": "k8s-node-77",
    "load_avg": 5.3
}
Resolver Suggestion: check upstream gateway for drift in node 357a6f
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/mailchimp
3 days ago node-50
Critical Node Failure Trace
Trace ID: 149e9677a598

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

Resolver Suggestion: internal kernel panic • inspect upstream server logs for process drift
Awaiting recovery cycle
major outage
5316 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/dashboard/user/mailchimp
3 days ago node-76
Critical Node Failure Trace
Trace ID: 9fc3d7152ba9

cURL error 28: Resolving timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nexly.biz/public/dashboard/user/mailchimp

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

2028ms

peak drift

5316ms

node resource flux

cpu load 4.0%

node stability index

47% confidence
24h pulse trend

deep throughput

14,289 total reqs

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