NodelistDB

Netmail PING — 4:902/26

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

← All PING/TRACE nodes Node history for 4:902/26

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

Answered in 9m

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

Answered
MSGID
2:5001/100@fidonet 6ad57e43
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 02:19 UTC
Answered
2026-10-19 02:29 UTC by SBBSecho, 4:902/26
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-19 02:19 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 02:19 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 04:21 local – D'Bridge 4
4 2:292/854 2026-10-19 03:23 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261019.021943.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.021944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.042109 D'Bridge 4
2:292/854@Ward_Dossche @20261019.032359.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:24 UTC – SBBSecho 3.38-Linux master/22cbda6be5
2 2:292/854 2026-10-19 04:26 local – D'Bridge 4
3 2:292/854 2026-10-19 03:28 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
4:902/26 @20261019.022453.UTC SBBSecho 3.38-Linux master/22cbda6be5
2:292/854 @20261019.042606 D'Bridge 4
2:292/854@Ward_Dossche @20261019.032859.UTC O/T-Track+ 2.85

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

Answered in 10m

The robot at 4:902/26 bounced it back 10m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac306eb
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 02:09 UTC
Answered
2026-10-05 02:20 UTC by SBBSecho, 4:902/26
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:09 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 02:09 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 04:11 local – D'Bridge 4
4 2:292/854 2026-10-05 03:14 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261005.020943.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.020944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.041107 D'Bridge 4
2:292/854@Ward_Dossche @20261005.031400.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
#NodeStampedElapsedSoftware
1 4:902/26 2026-10-05 02:15 UTC – SBBSecho 3.38-Linux master/22cbda6be5
2 2:292/854 2026-10-05 04:19 local – D'Bridge 4
Raw Via lines 
4:902/26 @20261005.021516.UTC SBBSecho 3.38-Linux master/22cbda6be5
2:292/854 @20261005.041903 D'Bridge 4

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

Answered in 8m

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

Answered
MSGID
2:5001/100@fidonet 6ab09105
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 02:14 UTC by SBBSecho, 4:902/26
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→+2s2:5020/715→2:292/854→+1h 3m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 02:05 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 02:05 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 04:06 local – D'Bridge 4
4 2:292/854 2026-09-21 03:09 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20260921.020553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.020555.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.040617 D'Bridge 4
2:292/854@Ward_Dossche @20260921.030900.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 3m2:292/854
#NodeStampedElapsedSoftware
1 4:902/26 2026-09-21 02:10 UTC – SBBSecho 3.37-Linux master/~3dc56fb6b5
2 2:292/854 2026-09-21 04:11 local – D'Bridge 4
3 2:292/854 2026-09-21 03:13 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
4:902/26 @20260921.021013.UTC SBBSecho 3.37-Linux master/~3dc56fb6b5
2:292/854 @20260921.041114 D'Bridge 4
2:292/854@Ward_Dossche @20260921.031359.UTC O/T-Track+ 2.85

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

Answered in 12m

The robot at 4:902/26 bounced it back 12m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e179f
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:47 UTC
Answered
2026-09-07 01:59 UTC by SBBSecho, 4:902/26
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→+1h 6m2:292/854
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:47 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 03:51 local – D'Bridge 4
3 2:292/854 2026-09-07 02:53 UTC +1h 6m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260907.014723.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.035113 D'Bridge 4
2:292/854@Ward_Dossche @20260907.025359.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 3m2:292/854
#NodeStampedElapsedSoftware
1 4:902/26 2026-09-07 01:55 UTC – SBBSecho 3.37-Linux master/6556a01a9
2 2:292/854 2026-09-07 03:56 local – D'Bridge 4
3 2:292/854 2026-09-07 02:58 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
4:902/26 @20260907.015528.UTC SBBSecho 3.37-Linux master/6556a01a9
2:292/854 @20260907.035613 D'Bridge 4
2:292/854@Ward_Dossche @20260907.025859.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-19 02:29 UTC

pong Pong: PING

From SBBSecho, 4:902/26 · answers 2:5001/100@fidonet 6ad57e43

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 @20261019.022453.UTC SBBSecho 3.38-Linux master/22cbda6be5
  • 2:292/854 @20261019.042606 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.032859.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:20 UTC

pong Pong: PING

From SBBSecho, 4:902/26 · answers 2:5001/100@fidonet 6ac306eb

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.021516.UTC SBBSecho 3.38-Linux master/22cbda6be5
  • 2:292/854 @20261005.041903 D'Bridge 4

Software

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

2026-09-21 02:14 UTC

pong Pong: PING

From SBBSecho, 4:902/26 · answers 2:5001/100@fidonet 6ab09105

Path quoted in this reply

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

This reply's own Via lines

  • 4:902/26 @20260921.021013.UTC SBBSecho 3.37-Linux master/~3dc56fb6b5
  • 2:292/854 @20260921.041114 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.031359.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 01:59 UTC

pong Pong: PING

From SBBSecho, 4:902/26 · answers 2:5001/100@fidonet 6a9e179f

Path quoted in this reply

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

This reply's own Via lines

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

Software

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