NodelistDB

Netmail PING — 4:904/0

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

← All PING/TRACE nodes Node history for 4:904/0

Routed ping · 2026-10-19 02:29 UTC

Answered in 9m

The robot at 4:904/0 bounced it back 9m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad58097
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 02:29 UTC
Answered
2026-10-19 02:39 UTC by SBBSecho, 4:904/0
Robot
SBBSecho 3.38-Linux master/22cbda6be5 sep 30 2026 GCC 12.2.0

Outbound path

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

2:5001/100→2:5020/715→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 02:29 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 02:29 UTC – RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 04:31 local – D'Bridge 4
4 2:292/854 2026-10-19 03:33 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261019.022943.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.022943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.043103 D'Bridge 4
2:292/854@Ward_Dossche @20261019.033359.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.

4:902/26→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 4:902/26 2026-10-19 02:34 UTC – SBBSecho 3.38-Linux master/22cbda6be5
2 2:292/854 2026-10-19 04:36 local – D'Bridge 4
3 2:292/854 2026-10-19 03:38 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
4:902/26 @20261019.023456.UTC SBBSecho 3.38-Linux master/22cbda6be5
2:292/854 @20261019.043606 D'Bridge 4
2:292/854@Ward_Dossche @20261019.033859.UTC O/T-Track+ 2.85

Routed ping · 2026-10-05 02:19 UTC

Answered in 15m

The robot at 4:904/0 bounced it back 15m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac3093e
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 02:19 UTC
Answered
2026-10-05 02:35 UTC by SBBSecho, 4:904/0
Robot
SBBSecho 3.38-Linux master/22cbda6be5 sep 30 2026 GCC 12.2.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
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 02:19 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 02:19 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 04:21 local – D'Bridge 4
4 2:292/854 2026-10-05 03:24 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261005.021942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.021943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.042103 D'Bridge 4
2:292/854@Ward_Dossche @20261005.032400.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.

4:902/26→2:292/854→+1h 5m2:292/854
#NodeStampedElapsedSoftware
1 4:902/26 2026-10-05 02:28 UTC – SBBSecho 3.38-Linux master/22cbda6be5
2 2:292/854 2026-10-05 04:31 local – D'Bridge 4
3 2:292/854 2026-10-05 03:34 UTC +1h 5m O/T-Track+ 2.85
Raw Via lines 
4:902/26 @20261005.022808.UTC SBBSecho 3.38-Linux master/22cbda6be5
2:292/854 @20261005.043107 D'Bridge 4
2:292/854@Ward_Dossche @20261005.033400.UTC O/T-Track+ 2.85

Routed ping · 2026-09-21 02:15 UTC

Answered in 8m

The robot at 4:904/0 bounced it back 8m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab09359
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 02:24 UTC by SBBSecho, 4:904/0
Robot
SBBSecho 3.37-Linux master/~3dc56fb6b5 sep 16 2026 GCC 12.2.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 02:15 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 02:15 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 04:16 local – D'Bridge 4
4 2:292/854 2026-09-21 03:18 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20260921.021553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.021554.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.041617 D'Bridge 4
2:292/854@Ward_Dossche @20260921.031859.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.

4:902/26→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 4:902/26 2026-09-21 02:19 UTC – SBBSecho 3.37-Linux master/~3dc56fb6b5
2 2:292/854 2026-09-21 04:21 local – D'Bridge 4
3 2:292/854 2026-09-21 03:23 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
4:902/26 @20260921.021957.UTC SBBSecho 3.37-Linux master/~3dc56fb6b5
2:292/854 @20260921.042102 D'Bridge 4
2:292/854@Ward_Dossche @20260921.032359.UTC O/T-Track+ 2.85

Routed ping · 2026-09-07 01:57 UTC

Answered in 7m

The robot at 4:904/0 bounced it back 7m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e19f4
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 02:04 UTC by SBBSecho, 4:904/0
Robot
SBBSecho 3.37-Linux master/6556a01a9 jul 10 2026 GCC 12.2.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
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:57 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 03:59 local – D'Bridge 4
Raw Via lines 
2:5020/715 @20260907.015708.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.035909 D'Bridge 4

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.

4:902/26→2:292/854→+1h 3m2:292/854
#NodeStampedElapsedSoftware
1 4:902/26 2026-09-07 02:00 UTC – SBBSecho 3.37-Linux master/6556a01a9
2 2:292/854 2026-09-07 04:01 local – D'Bridge 4
3 2:292/854 2026-09-07 03:03 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
4:902/26 @20260907.020027.UTC SBBSecho 3.37-Linux master/6556a01a9
2:292/854 @20260907.040112 D'Bridge 4
2:292/854@Ward_Dossche @20260907.030359.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-19 02:39 UTC

pong Pong: PING

From SBBSecho, 4:904/0 · answers 2:5001/100@fidonet 6ad58097

Path quoted in this reply

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

This reply's own Via lines

  • 4:902/26 @20261019.023456.UTC SBBSecho 3.38-Linux master/22cbda6be5
  • 2:292/854 @20261019.043606 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.033859.UTC O/T-Track+ 2.85

Software

SBBSecho 3.38-Linux master/22cbda6be5 sep 30 2026 GCC 12.2.0   --- SBBSecho 3.38-Linux

2026-10-05 02:35 UTC

pong Pong: PING

From SBBSecho, 4:904/0 · answers 2:5001/100@fidonet 6ac3093e

Path quoted in this reply

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

This reply's own Via lines

  • 4:902/26 @20261005.022808.UTC SBBSecho 3.38-Linux master/22cbda6be5
  • 2:292/854 @20261005.043107 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.033400.UTC O/T-Track+ 2.85

Software

SBBSecho 3.38-Linux master/22cbda6be5 sep 30 2026 GCC 12.2.0   --- SBBSecho 3.38-Linux

2026-09-21 02:24 UTC

pong Pong: PING

From SBBSecho, 4:904/0 · answers 2:5001/100@fidonet 6ab09359

Path quoted in this reply

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

This reply's own Via lines

  • 4:902/26 @20260921.021957.UTC SBBSecho 3.37-Linux master/~3dc56fb6b5
  • 2:292/854 @20260921.042102 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.032359.UTC O/T-Track+ 2.85

Software

SBBSecho 3.37-Linux master/~3dc56fb6b5 sep 16 2026 GCC 12.2.0   --- SBBSecho 3.37-Linux

2026-09-07 02:04 UTC

pong Pong: PING

From SBBSecho, 4:904/0 · answers 2:5001/100@fidonet 6a9e19f4

Path quoted in this reply

2:5020/715→2:292/854

This reply's own Via lines

  • 4:902/26 @20260907.020027.UTC SBBSecho 3.37-Linux master/6556a01a9
  • 2:292/854 @20260907.040112 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.030359.UTC O/T-Track+ 2.85

Software

SBBSecho 3.37-Linux master/6556a01a9 jul 10 2026 GCC 12.2.0   --- SBBSecho 3.37-Linux