NodelistDB

Netmail PING — 2:341/66

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

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

Routed ping · 2026-10-18 12:39 UTC

Answered in 41m

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

Answered
MSGID
2:5001/100@fidonet 6ad4be0e
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-18 12:39 UTC
Answered
2026-10-18 13:21 UTC by RnTrack Pong, 2:341/66

Outbound path

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

2:5001/100→+1s2:5020/715→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-18 12:39 UTC – FidoMail b956abfb
2 2:5020/715 2026-10-18 12:39 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-18 14:41 local – D'Bridge 4
4 2:292/854 2026-10-18 13:44 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261018.123942.UTC FidoMail b956abfb
2:5020/715 @20261018.123943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261018.144111 D'Bridge 4
2:292/854@Ward_Dossche @20261018.134400.UTC O/T-Track+ 2.85

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/66
#NodeStampedElapsedSoftware
1 2:341/66 2026-10-18 13:20 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:341/66 @20261018.132007.UTC hpt/lnx 1.9 2024-03-02

Routed ping · 2026-10-04 12:39 UTC

Answered in 44m

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

Answered
MSGID
2:5001/100@fidonet 6ac2490e
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-04 12:39 UTC
Answered
2026-10-04 13:23 UTC by RnTrack Pong, 2:341/66

Outbound path

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

2:5001/100→+1s2:5020/715→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-04 12:39 UTC – FidoMail 199808a3
2 2:5020/715 2026-10-04 12:39 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-04 14:41 local – D'Bridge 4
4 2:292/854 2026-10-04 13:43 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261004.123942.UTC FidoMail 199808a3
2:5020/715 @20261004.123943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261004.144104 D'Bridge 4
2:292/854@Ward_Dossche @20261004.134359.UTC O/T-Track+ 2.85

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/66
#NodeStampedElapsedSoftware
1 2:341/66 2026-10-04 13:22 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:341/66 @20261004.132217.UTC hpt/lnx 1.9 2024-03-02

Routed ping · 2026-09-20 12:35 UTC

Answered in 45m

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

Answered
MSGID
2:5001/100@fidonet 6aafd329
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-20 12:35 UTC
Answered
2026-09-20 13:21 UTC by RnTrack Pong, 2:341/66

Outbound path

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

2:5001/100→2:5020/715→2:292/854→+1h 3m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-20 12:35 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-20 12:35 UTC – RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-20 14:36 local – D'Bridge 4
4 2:292/854 2026-09-20 13:39 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20260920.123553.UTC FidoMail 97f43bf5
2:5020/715 @20260920.123553.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260920.143606 D'Bridge 4
2:292/854@Ward_Dossche @20260920.133901.UTC O/T-Track+ 2.85

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/66
#NodeStampedElapsedSoftware
1 2:341/66 2026-09-20 13:20 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:341/66 @20260920.132002.UTC hpt/lnx 1.9 2024-03-02

Routed ping · 2026-09-06 12:28 UTC

Answered in 1h 0m

The robot at 2:341/66 bounced it back 1h 0m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9d5c74
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-06 12:38 UTC
Answered
2026-09-06 13:29 UTC by RnTrack Pong, 2:341/66

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 5m2:292/854
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-06 12:28 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-06 14:31 local – D'Bridge 4
3 2:292/854 2026-09-06 13:33 UTC +1h 5m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260906.122837.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260906.143102 D'Bridge 4
2:292/854@Ward_Dossche @20260906.133359.UTC O/T-Track+ 2.85

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/66→2:292/854→+1h 8m2:292/854
#NodeStampedElapsedSoftware
1 2:341/66 2026-09-06 13:20 UTC – hpt/lnx 1.9 2024-03-02
2 2:292/854 2026-09-06 15:26 local – D'Bridge 4
3 2:292/854 2026-09-06 14:28 UTC +1h 8m O/T-Track+ 2.85
Raw Via lines 
2:341/66 @20260906.132002.UTC hpt/lnx 1.9 2024-03-02
2:292/854 @20260906.152607 D'Bridge 4
2:292/854@Ward_Dossche @20260906.142859.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-18 13:21 UTC

pong unsecure Pong

From RnTrack Pong, 2:341/66 · answers 2:5001/100@fidonet 6ad4be0e

Path quoted in this reply

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

This reply's own Via lines

  • 2:341/66 @20261018.132007.UTC hpt/lnx 1.9 2024-03-02

2026-10-04 13:23 UTC

pong unsecure Pong

From RnTrack Pong, 2:341/66 · answers 2:5001/100@fidonet 6ac2490e

Path quoted in this reply

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

This reply's own Via lines

  • 2:341/66 @20261004.132217.UTC hpt/lnx 1.9 2024-03-02

2026-09-20 13:21 UTC

pong unsecure Pong

From RnTrack Pong, 2:341/66 · answers 2:5001/100@fidonet 6aafd329

Path quoted in this reply

2:5001/100→2:5020/715→2:292/854→+1h 3m2:292/854

This reply's own Via lines

  • 2:341/66 @20260920.132002.UTC hpt/lnx 1.9 2024-03-02

2026-09-06 13:29 UTC

pong Pong

From RnTrack Pong, 2:341/66 · answers 2:5001/100@fidonet 6a9d5c74

Path quoted in this reply

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

This reply's own Via lines

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