NodelistDB

Netmail PING — 2:240/5824

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

← All PING/TRACE nodes Node history for 2:240/5824

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

Answered in 9m

The robot at 2:240/5824 bounced it back 9m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad55fc6
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-19 00:19 UTC by SBBSecho, 2:240/5824
Robot
SBBSecho 3.14-Linux master/635c258d2 Jan 14 2022 GCC 8.3.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 4m2:292/854→2:240/5832
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 00:09 UTC – FidoMail v0.1.5
2 2:5020/715 2026-10-19 00:09 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 02:11 local – D'Bridge 4
4 2:292/854 2026-10-19 01:14 UTC +1h 4m O/T-Track+ 2.85
5 2:240/5832 2026-10-19 02:15 local – Itrack- 2.0
Raw Via lines 
2:5001/100@fidonet @20261019.000942.UTC FidoMail v0.1.5
2:5020/715 @20261019.000943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.021112 D'Bridge 4
2:292/854@Ward_Dossche @20261019.011400.UTC O/T-Track+ 2.85
2:240/5832@fidonet.org @20261019.021506.70 Itrack- 2.0

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:240/5824→2:240/5832→2:292/854→+1h 3m2:292/854
#NodeStampedElapsedSoftware
1 2:240/5824 2026-10-19 00:15 UTC – SBBSecho 3.14-Linux master/635c258d2
2 2:240/5832 2026-10-19 02:15 local – Itrack- 2.0
3 2:292/854 2026-10-19 02:16 local – D'Bridge 4
4 2:292/854 2026-10-19 01:18 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
2:240/5824 @20261019.001524.UTC SBBSecho 3.14-Linux master/635c258d2
2:240/5832@fidonet.org @20261019.021539.47 Itrack- 2.0
2:292/854 @20261019.021616 D'Bridge 4
2:292/854@Ward_Dossche @20261019.011859.UTC O/T-Track+ 2.85

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

Answered in 54m

The robot at 2:240/5824 bounced it back 54m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2eac6
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 00:09 UTC
Answered
2026-10-05 01:04 UTC by SBBSecho, 2:240/5824
Robot
SBBSecho 3.14-Linux master/635c258d2 Jan 14 2022 GCC 8.3.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 4m2:292/854→2:240/5832
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 00:09 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 00:09 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 02:11 local – D'Bridge 4
4 2:292/854 2026-10-05 01:13 UTC +1h 4m O/T-Track+ 2.85
5 2:240/5832 2026-10-05 02:15 local – Itrack- 2.0
Raw Via lines 
2:5001/100@fidonet @20261005.000942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.000943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.021107 D'Bridge 4
2:292/854@Ward_Dossche @20261005.011359.UTC O/T-Track+ 2.85
2:240/5832@fidonet.org @20261005.021512.56 Itrack- 2.0

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:240/5824→2:240/5832→2:292/854
#NodeStampedElapsedSoftware
1 2:240/5824 2026-10-05 01:00 UTC – SBBSecho 3.14-Linux master/635c258d2
2 2:240/5832 2026-10-05 03:02 local – Itrack- 2.0
3 2:292/854 2026-10-05 03:04 local – D'Bridge 4
Raw Via lines 
2:240/5824 @20261005.010012.UTC SBBSecho 3.14-Linux master/635c258d2
2:240/5832@fidonet.org @20261005.030220.30 Itrack- 2.0
2:292/854 @20261005.030402 D'Bridge 4

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

Answered in 8m

The robot at 2:240/5824 bounced it back 8m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab074e1
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 00:14 UTC by SBBSecho, 2:240/5824
Robot
SBBSecho 3.14-Linux master/635c258d2 Jan 14 2022 GCC 8.3.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→2:240/5832
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 00:05 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 00:05 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 02:06 local – D'Bridge 4
4 2:292/854 2026-09-21 01:08 UTC +1h 3m O/T-Track+ 2.85
5 2:240/5832 2026-09-21 02:09 local – Itrack- 2.0
Raw Via lines 
2:5001/100@fidonet @20260921.000553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.000554.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.020615 D'Bridge 4
2:292/854@Ward_Dossche @20260921.010859.UTC O/T-Track+ 2.85
2:240/5832@fidonet.org @20260921.020927.96 Itrack- 2.0

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:240/5824→2:240/5832→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:240/5824 2026-09-21 00:09 UTC – SBBSecho 3.14-Linux master/635c258d2
2 2:240/5832 2026-09-21 02:10 local – Itrack- 2.0
3 2:292/854 2026-09-21 02:11 local – D'Bridge 4
4 2:292/854 2026-09-21 01:13 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:240/5824 @20260921.000951.UTC SBBSecho 3.14-Linux master/635c258d2
2:240/5832@fidonet.org @20260921.021004.11 Itrack- 2.0
2:292/854 @20260921.021111 D'Bridge 4
2:292/854@Ward_Dossche @20260921.011359.UTC O/T-Track+ 2.85

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

Answered in 10m

The robot at 2:240/5824 bounced it back 10m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9dfe74
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-06 23:59 UTC
Answered
2026-09-07 00:09 UTC by SBBSecho, 2:240/5824
Robot
SBBSecho 3.14-Linux master/635c258d2 Jan 14 2022 GCC 8.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→2:240/5832
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-06 23:59 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 02:01 local – D'Bridge 4
3 2:292/854 2026-09-07 01:03 UTC +1h 4m O/T-Track+ 2.85
4 2:240/5832 2026-09-07 02:04 local – Itrack- 2.0
Raw Via lines 
2:5020/715 @20260906.235949.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.020111 D'Bridge 4
2:292/854@Ward_Dossche @20260907.010359.UTC O/T-Track+ 2.85
2:240/5832@fidonet.org @20260907.020459.64 Itrack- 2.0

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:240/5824→2:240/5832→2:292/854
#NodeStampedElapsedSoftware
1 2:240/5824 2026-09-07 00:06 UTC – SBBSecho 3.14-Linux master/635c258d2
2 2:240/5832 2026-09-07 02:06 local – Itrack- 2.0
3 2:292/854 2026-09-07 02:09 local – D'Bridge 4
Raw Via lines 
2:240/5824 @20260907.000616.UTC SBBSecho 3.14-Linux master/635c258d2
2:240/5832@fidonet.org @20260907.020625.30 Itrack- 2.0
2:292/854 @20260907.020908 D'Bridge 4

Evidence

Replies

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

2026-10-19 00:19 UTC

pong Pong: PING

From SBBSecho, 2:240/5824 · answers 2:5001/100@fidonet 6ad55fc6

Path quoted in this reply

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

This reply's own Via lines

  • 2:240/5824 @20261019.001524.UTC SBBSecho 3.14-Linux master/635c258d2
  • 2:240/5832@fidonet.org @20261019.021539.47 Itrack- 2.0
  • 2:292/854 @20261019.021616 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.011859.UTC O/T-Track+ 2.85

Software

SBBSecho 3.14-Linux master/635c258d2 Jan 14 2022 GCC 8.3.0   --- SBBSecho 3.14-Linux

2026-10-05 01:04 UTC

pong Pong: PING

From SBBSecho, 2:240/5824 · answers 2:5001/100@fidonet 6ac2eac6

Path quoted in this reply

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

This reply's own Via lines

  • 2:240/5824 @20261005.010012.UTC SBBSecho 3.14-Linux master/635c258d2
  • 2:240/5832@fidonet.org @20261005.030220.30 Itrack- 2.0
  • 2:292/854 @20261005.030402 D'Bridge 4

Software

SBBSecho 3.14-Linux master/635c258d2 Jan 14 2022 GCC 8.3.0   --- SBBSecho 3.14-Linux

2026-09-21 00:14 UTC

pong Pong: PING

From SBBSecho, 2:240/5824 · answers 2:5001/100@fidonet 6ab074e1

Path quoted in this reply

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

This reply's own Via lines

  • 2:240/5824 @20260921.000951.UTC SBBSecho 3.14-Linux master/635c258d2
  • 2:240/5832@fidonet.org @20260921.021004.11 Itrack- 2.0
  • 2:292/854 @20260921.021111 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.011359.UTC O/T-Track+ 2.85

Software

SBBSecho 3.14-Linux master/635c258d2 Jan 14 2022 GCC 8.3.0   --- SBBSecho 3.14-Linux

2026-09-07 00:09 UTC

pong Pong: PING

From SBBSecho, 2:240/5824 · answers 2:5001/100@fidonet 6a9dfe74

Path quoted in this reply

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

This reply's own Via lines

  • 2:240/5824 @20260907.000616.UTC SBBSecho 3.14-Linux master/635c258d2
  • 2:240/5832@fidonet.org @20260907.020625.30 Itrack- 2.0
  • 2:292/854 @20260907.020908 D'Bridge 4

Software

SBBSecho 3.14-Linux master/635c258d2 Jan 14 2022 GCC 8.3.0   --- SBBSecho 3.14-Linux