NodelistDB

Netmail PING — 2:221/0

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

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

Routed ping · 2026-09-06 23:49 UTC

Answered in 5m

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

Answered
MSGID
2:5001/100@fidonet 6a9dfc1d
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-06 23:55 UTC by Postmaster, 2:221/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-06 23:49 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 01:51 local – D'Bridge 4
3 2:292/854 2026-09-07 00:53 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260906.234949.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.015114 D'Bridge 4
2:292/854@Ward_Dossche @20260907.005359.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→2:221/1
#NodeStampedElapsedSoftware
1 2:221/1 2026-09-06 23:54 UTC – RNtrack 2.3.1/Lnx/Perl
2 2:221/1 2026-09-06 23:54 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines 
2:221/1 @20260906.235456.UTC RNtrack 2.3.1/Lnx/Perl
2:221/1 @20260906.235456.UTC hpt/lnx 1.9 2024-03-02

Evidence

Replies

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

2026-09-06 23:55 UTC

pong unsecure Pong receipt

From Postmaster, 2:221/0 · answers 2:5001/100@fidonet 6a9dfc1d

Path quoted in this reply

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

This reply's own Via lines

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