NodelistDB

Netmail PING — 2:341/200

Every FTS-4010 PING sent to 2:341/200 (fidonet), with the path each one walked.

← All PING/TRACE nodes Node history for 2:341/200

Routed ping · 2026-09-07 00:39 UTC

Answered in 45m

The robot at 2:341/200 bounced it back 45m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e07d4
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 00:39 UTC
Answered
2026-09-07 01:24 UTC by SBBSecho, 2:341/200
Robot
SBBSecho 3.37-Linux master/a680d770bb ago 29 2026 GCC 14.2.0
Transit notices
1

Outbound path

The Via chain the robot quoted back: every system the ping passed through on its way out.

2:5020/715→2:292/854→+1h 4m2:292/854→-23m2:341/66
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 00:39 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 02:41 local – D'Bridge 4
3 2:292/854 2026-09-07 01:43 UTC +1h 4m O/T-Track+ 2.85
4 2:341/66 2026-09-07 01:20 UTC -23m hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:5020/715 @20260907.003949.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.024114 D'Bridge 4
2:292/854@Ward_Dossche @20260907.014359.UTC O/T-Track+ 2.85
2:341/66 @20260907.012002.UTC hpt/lnx 1.9 2024-03-02

Return path

The answer's own Via chain: the way back from the robot to 2:5001/100, as each relay on it recorded itself. The answer need not come back the way the ping went out, and a relay that stamps no Via line of its own leaves no mark here, so this is the relays' account of the trip rather than a verified route.

2:341/200→+3s2:341/66→2:292/854
#NodeStampedElapsedSoftware
1 2:341/200 2026-09-07 01:21 UTC – SBBSecho 3.37-Linux master/a680d770bb
2 2:341/66 2026-09-07 01:21 UTC +3s hpt/lnx 1.9 2024-03-02
3 2:292/854 2026-09-07 03:24 local – D'Bridge 4
Raw Via lines 
2:341/200 @20260907.012103.UTC SBBSecho 3.37-Linux master/a680d770bb
2:341/66 @20260907.012106.UTC hpt/lnx 1.9 2024-03-02
2:292/854 @20260907.032410 D'Bridge 4

Evidence

Replies

Every netmail that came back about a ping to 2:341/200, newest first, as the sending node received it. Pongs and transit notices are matched to the ping they answer.

2026-09-07 01:24 UTC

trace Pong

From RnTrack In-Transit Pong, 2:341/66 · answers 2:5001/100@fidonet 6a9e07d4

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854

This reply's own Via lines

  • 2:341/66 @20260907.012002.UTC hpt/lnx 1.9 2024-03-02
  • 2:292/854 @20260907.032111 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.022359.UTC O/T-Track+ 2.85

2026-09-07 01:24 UTC

pong Pong: PING

From SBBSecho, 2:341/200 · answers 2:5001/100@fidonet 6a9e07d4

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854→-23m2:341/66

This reply's own Via lines

  • 2:341/200 @20260907.012103.UTC SBBSecho 3.37-Linux master/a680d770bb
  • 2:341/66 @20260907.012106.UTC hpt/lnx 1.9 2024-03-02
  • 2:292/854 @20260907.032410 D'Bridge 4

Software

SBBSecho 3.37-Linux master/a680d770bb ago 29 2026 GCC 14.2.0   --- SBBSecho 3.37-Linux