Trace ID

trace_cb370d8f-8b74-4574-b99c-04bc2c4e955b

replayed

Amount: 140 CKB
Mode: sandbox
Latency: 73ms
Failure stage: peer_connect
Sender: fiber-devnet-sender-01
Receiver: fiber-devnet-receiver-09

PEER_OFFLINE

Required peer offline

The payment reached a route execution step that depended on a peer that was not reachable.

Likely Causes

Peer process is down or restarting
Network connectivity between peers is broken
Peer identity or address data is stale

Suggested Fixes

Restore the peer and retry
Use an alternate route that avoids the peer
Refresh peer address data

Failure Timeline

Lifecycle events captured in milliseconds.

5 events

0ms
request_receivedinfo
Payment attempt created for 140 CKB
8ms
invoice_validationsuccess
Invoice fields parsed
18ms
route_discoveryinfo
Candidate routes loaded from sandbox graph
39ms
policy_checkinfo
Route policies evaluated
73ms
peer_connecterror
Peer offline during route execution

Replay-to-Fix Results

same_conditions

Original amount, route, peer state, fee limit, timeout, and asset unchanged

failed

The original failure reproduces under the same conditions, confirming the fingerprint is stable.

80ms

restored_peer

Restored unreachable peer before retry

success

Restoring peer reachability gives FNN a usable route again.

53msSmallest-fix recommendation

alternate_route

Selected alternate route excluding the failing condition

success

A route with different hops avoids the original failure point with slightly higher latency.

91ms

retry_after_delay

Retried after peer health delay

success

A delayed retry succeeds after the peer returns to the reachable set.

94ms

Exportable Debug Report

Markdown and JSON report output for trace reviews and operator handoff.

# FiberTracebox Report

## Trace Summary

- Trace ID: trace_cb370d8f-8b74-4574-b99c-04bc2c4e955b
- Payment status: replayed
- Amount: 140 CKB
- Sender: fiber-devnet-sender-01
- Receiver: fiber-devnet-receiver-09
- Mode: sandbox
- Latency: 73ms
- Failure time: 73ms
- Failure stage: peer_connect
- Failure fingerprint: PEER_OFFLINE


## Root Cause

The payment reached a route execution step that depended on a peer that was not reachable.



## Evidence Source

- Trace source: sandbox
- Replay mode: deterministic sandbox replay
- Live mutation: no
- RPC methods observed: not applicable
- Observed failure: not applicable
- Sandbox events are deterministic and safe for repeatable demos and CI.
- Replay-to-Fix changes simulated route conditions without moving funds.

## Timeline

| ms | stage | severity | message |
| --- | --- | --- | --- |
| 0 | request_received | info | Payment attempt created for 140 CKB |
| 8 | invoice_validation | success | Invoice fields parsed |
| 18 | route_discovery | info | Candidate routes loaded from sandbox graph |
| 39 | policy_check | info | Route policies evaluated |
| 73 | peer_connect | error | Peer offline during route execution |

## Replay Results

| strategy | changed condition | result | latency ms | recommended |
| --- | --- | --- | --- | --- |
| same_conditions | Original amount, route, peer state, fee limit, timeout, and asset unchanged | failed | 80 | no |
| restored_peer | Restored unreachable peer before retry | success | 53 | yes |
| alternate_route | Selected alternate route excluding the failing condition | success | 91 | no |
| retry_after_delay | Retried after peer health delay | success | 94 | no |

## Smallest-Fix Recommendation

Restore peer or route around it: Restore peer reachability, then retry. If restoration is outside your control, route around the peer.



Confidence: high

## Suggested Next Actions

- Restore the peer and retry
- Use an alternate route that avoids the peer
- Refresh peer address data
- Restore peer reachability, then retry. If restoration is outside your control, route around the peer.

## Mode Disclosure

Sandbox mode: deterministic simulated Fiber payment conditions are used for repeatable diagnostics.

Open JSON report