NodelistDB

Netmail PING — 2:221/1

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

← All PING/TRACE nodes Node history for 2:221/1

Routed ping · 2026-10-15 20:09 UTC

Answered in 5m

The robot at 2:221/1 bounced it back 5m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad13307
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-15 20:15 UTC by RNtrack Pongmaster, 2:221/1
Robot
ThePong/lnx 20260923

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-15 20:09 UTC – FidoMail e334310e
2 2:5020/715 2026-10-15 20:09 UTC +3s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-15 22:11 local – D'Bridge 4
4 2:292/854 2026-10-15 21:14 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261015.200942.UTC FidoMail e334310e
2:5020/715 @20261015.200945.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261015.221109 D'Bridge 4
2:292/854@Ward_Dossche @20261015.211400.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:221/1
#NodeStampedElapsedSoftware
1 2:221/1 2026-10-15 20:15 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:221/1 @20261015.201502.UTC hpt/lnx 1.9 2024-03-02

Routed ping · 2026-10-01 20:09 UTC

Answered in 4m

The robot at 2:221/1 bounced it back 4m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6abebe07
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-01 20:14 UTC by RNtrack Pongmaster, 2:221/1
Robot
ThePong/lnx 20260923

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-01 20:09 UTC – FidoMail a8bc7247
2 2:5020/715 2026-10-01 20:09 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-01 22:11 local – D'Bridge 4
4 2:292/854 2026-10-01 21:14 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261001.200942.UTC FidoMail a8bc7247
2:5020/715 @20261001.200944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261001.221112 D'Bridge 4
2:292/854@Ward_Dossche @20261001.211401.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:221/1
#NodeStampedElapsedSoftware
1 2:221/1 2026-10-01 20:14 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:221/1 @20261001.201429.UTC hpt/lnx 1.9 2024-03-02

Routed ping · 2026-09-17 20:05 UTC

Answered in 4m

The robot at 2:221/1 bounced it back 4m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6aac4822
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-17 20:10 UTC by RNtrack Pongmaster, 2:221/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 3m2:292/854
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-17 20:05 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-17 22:06 local – D'Bridge 4
3 2:292/854 2026-09-17 21:09 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260917.200555.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260917.220608 D'Bridge 4
2:292/854@Ward_Dossche @20260917.210900.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:221/1→+1s2:221/1
#NodeStampedElapsedSoftware
1 2:221/1 2026-09-17 20:09 UTC – RNtrack 2.3.1/Lnx
2 2:221/1 2026-09-17 20:09 UTC +1s hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:221/1 @20260917.200953.UTC RNtrack 2.3.1/Lnx
2:221/1 @20260917.200954.UTC hpt/lnx 1.9 2024-03-02

Routed ping · 2026-09-03 20:00 UTC

Answered in 13h 19m

The robot at 2:221/1 bounced it back 13h 19m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a99d1e2
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-03 20:10 UTC
Answered
2026-09-04 09:20 UTC by Postmaster, 2:221/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 7m2:292/854
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-03 23:41 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-04 01:46 local – D'Bridge 4
3 2:292/854 2026-09-04 00:49 UTC +1h 7m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260903.234155.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260904.014604 D'Bridge 4
2:292/854@Ward_Dossche @20260904.004900.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:221/1
#NodeStampedElapsedSoftware
1 2:221/1 2026-09-04 09:20 UTC – RNtrack 2.3.1/Lnx/Perl
Raw Via lines 
2:221/1 @20260904.092026.UTC RNtrack 2.3.1/Lnx/Perl

Evidence

Replies

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

2026-10-15 20:15 UTC

pong unsecure Pong receipt

From RNtrack Pongmaster, 2:221/1 · answers 2:5001/100@fidonet 6ad13307

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:221/1 @20261015.201502.UTC hpt/lnx 1.9 2024-03-02

Software

ThePong/lnx 20260923   --- RNtrack 2.3.1/Lnx/Perl

2026-10-01 20:14 UTC

pong unsecure Pong receipt

From RNtrack Pongmaster, 2:221/1 · answers 2:5001/100@fidonet 6abebe07

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:221/1 @20261001.201429.UTC hpt/lnx 1.9 2024-03-02

Software

ThePong/lnx 20260923   --- RNtrack 2.3.1/Lnx/Perl

2026-09-17 20:10 UTC

pong unsecure Pong receipt

From RNtrack Pongmaster, 2:221/1 · answers 2:5001/100@fidonet 6aac4822

Path quoted in this reply

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

This reply's own Via lines

  • 2:221/1 @20260917.200953.UTC RNtrack 2.3.1/Lnx
  • 2:221/1 @20260917.200954.UTC hpt/lnx 1.9 2024-03-02

2026-09-04 09:20 UTC

pong unsecure Pong receipt

From Postmaster, 2:221/1 · answers 2:5001/100@fidonet 6a99d1e2

Path quoted in this reply

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

This reply's own Via lines

  • 2:221/1 @20260904.092026.UTC RNtrack 2.3.1/Lnx/Perl