NodelistDB

Netmail PING — 1:124/5016

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

← All PING/TRACE nodes Node history for 1:124/5016

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

Answered in 16h 5m

The robot at 1:124/5016 bounced it back 16h 5m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9df2bc
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-06 23:09 UTC
Answered
2026-09-07 15:15 UTC by SBBSecho, 1:124/5016
Robot
SBBSecho 3.37-Linux master/4de4ef90db Sep 04 2026 GCC 13.3.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→1:229/426→-1h 0m1:229/426→1:396/45
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-06 23:09 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 01:11 local – D'Bridge 4
3 2:292/854 2026-09-07 00:13 UTC +1h 4m O/T-Track+ 2.85
4 1:229/426 2026-09-06 19:13 local – D'Bridge 4
5 1:229/426 2026-09-06 23:13 UTC -1h 0m O/T-Track+ 2.85
6 1:396/45 – – Squish/386 1.11 Mon Sep 07 2026 at 16:08 UTC
Raw Via lines 
2:5020/715 @20260906.230949.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.011110 D'Bridge 4
2:292/854@Ward_Dossche @20260907.001359.UTC O/T-Track+ 2.85
1:229/426 @20260906.191347 D'Bridge 4
1:229/426@fidonet @20260906.231347.UTC O/T-Track+ 2.85
Squish/386 1.11 1:396/45, Mon Sep 07 2026 at 16:08 UTC

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.

1:124/5016→+1m2:280/464→2:280/464→+1m2:280/5003.0→+26s2:5020/715
#NodeStampedElapsedSoftware
1 1:124/5016 2026-09-07 15:12 UTC – SBBSecho 3.37-Linux master/4de4ef90db
2 2:280/464 2026-09-07 15:14 UTC +1m FMail-lnx64(Toss) 2.3.4.1-B20260520
3 2:280/464 2026-09-07 15:14 UTC – FMail-lnx64(Pack) 2.3.4.1-B20260520
4 2:280/5003.0 2026-09-07 15:15 UTC +1m FIDOGATE/ftntoss 4.4.14
5 2:5020/715 2026-09-07 15:15 UTC +26s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
1:124/5016 @20260907.151257.UTC SBBSecho 3.37-Linux master/4de4ef90db
2:280/464 @20260907.151400.283.UTC FMail-lnx64(Toss) 2.3.4.1-B20260520
2:280/464 @20260907.151400.292.UTC FMail-lnx64(Pack) 2.3.4.1-B20260520
2:280/5003.0 @20260907.151501.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20260907.151527.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-09-07 15:15 UTC

pong Pong: PING

From SBBSecho, 1:124/5016 · answers 2:5001/100@fidonet 6a9df2bc

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854→1:229/426→-1h 0m1:229/426→1:396/45

This reply's own Via lines

  • 1:124/5016 @20260907.151257.UTC SBBSecho 3.37-Linux master/4de4ef90db
  • 2:280/464 @20260907.151400.283.UTC FMail-lnx64(Toss) 2.3.4.1-B20260520
  • 2:280/464 @20260907.151400.292.UTC FMail-lnx64(Pack) 2.3.4.1-B20260520
  • 2:280/5003.0 @20260907.151501.UTC FIDOGATE/ftntoss 4.4.14
  • 2:5020/715 @20260907.151527.UTC RNtrack 2.3.0/Lnx/Perl

Software

SBBSecho 3.37-Linux master/4de4ef90db Sep 04 2026 GCC 13.3.0   --- SBBSecho 3.37-Linux