NodelistDB

Netmail PING — 2:34/0

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

← All PING/TRACE nodes Node history for 2:34/0

Routed ping · 2026-10-19 00:39 UTC

Answered in 41m

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

Answered
MSGID
2:5001/100@fidonet 6ad566d1
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 00:39 UTC
Answered
2026-10-19 01:20 UTC by RnTrack Pong, 2:34/0

Outbound path

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

2:5001/100→+3s2:5020/715→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 00:39 UTC – FidoMail v0.1.5
2 2:5020/715 2026-10-19 00:39 UTC +3s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 02:41 local – D'Bridge 4
4 2:292/854 2026-10-19 01:44 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261019.003942.UTC FidoMail v0.1.5
2:5020/715 @20261019.003945.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.024112 D'Bridge 4
2:292/854@Ward_Dossche @20261019.014400.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-19 01:20 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:341/66 @20261019.012007.UTC hpt/lnx 1.9 2024-03-02

Routed ping · 2026-10-05 00:39 UTC

Answered in 43m

The robot at 2:34/0 bounced it back 43m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2f1d1
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 00:39 UTC
Answered
2026-10-05 01:22 UTC by RnTrack Pong, 2:34/0

Outbound path

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

2:5001/100→+2s2:5020/715→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 00:39 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 00:39 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 02:41 local – D'Bridge 4
4 2:292/854 2026-10-05 01:44 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261005.003942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.003944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.024106 D'Bridge 4
2:292/854@Ward_Dossche @20261005.014400.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-05 01:20 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:341/66 @20261005.012002.UTC hpt/lnx 1.9 2024-03-02

Routed ping · 2026-09-21 00:35 UTC

Answered in 45m

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

Answered
MSGID
2:5001/100@fidonet 6ab07bec
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 00:35 UTC
Answered
2026-09-21 01:21 UTC by RnTrack Pong, 2:34/0

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 3m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 00:35 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 00:35 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 02:36 local – D'Bridge 4
4 2:292/854 2026-09-21 01:38 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20260921.003553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.003554.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.023613 D'Bridge 4
2:292/854@Ward_Dossche @20260921.013859.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-21 01:20 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:341/66 @20260921.012002.UTC hpt/lnx 1.9 2024-03-02

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

Answered in 55m

The robot at 2:34/0 bounced it back 55m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e057f
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 00:29 UTC
Answered
2026-09-07 01:24 UTC by RnTrack Pong, 2:34/0

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
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 00:29 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 02:31 local – D'Bridge 4
3 2:292/854 2026-09-07 01:33 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260907.002950.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.023115 D'Bridge 4
2:292/854@Ward_Dossche @20260907.013359.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 3m2:292/854
#NodeStampedElapsedSoftware
1 2:341/66 2026-09-07 01:20 UTC – hpt/lnx 1.9 2024-03-02
2 2:292/854 2026-09-07 03:21 local – D'Bridge 4
3 2:292/854 2026-09-07 02:23 UTC +1h 3m O/T-Track+ 2.85
Raw 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

Evidence

Replies

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

2026-10-19 01:20 UTC

pong unsecure Pong

From RnTrack Pong, 2:34/0 · answers 2:5001/100@fidonet 6ad566d1

Path quoted in this reply

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

This reply's own Via lines

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

2026-10-05 01:22 UTC

pong unsecure Pong

From RnTrack Pong, 2:34/0 · answers 2:5001/100@fidonet 6ac2f1d1

Path quoted in this reply

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

This reply's own Via lines

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

2026-09-21 01:21 UTC

pong unsecure Pong

From RnTrack Pong, 2:34/0 · answers 2:5001/100@fidonet 6ab07bec

Path quoted in this reply

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

This reply's own Via lines

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

2026-09-07 01:24 UTC

pong Pong

From RnTrack Pong, 2:34/0 · answers 2:5001/100@fidonet 6a9e057f

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