Answered in 9m

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

Answered
MSGID
2:5001/100@fidonet 6ad57bea
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-19 02:19 UTC by SBBSecho, 4:4/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-19 02:09 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 02:09 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 04:11 local – D'Bridge 4
4 2:292/854 2026-10-19 03:13 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines
2:5001/100@fidonet @20261019.020943.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.020944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.041114 D'Bridge 4
2:292/854@Ward_Dossche @20261019.031359.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:14 UTC – SBBSecho 3.38-Linux master/22cbda6be5
2 2:292/854 2026-10-19 04:16 local – D'Bridge 4
3 2:292/854 2026-10-19 03:19 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines
4:902/26 @20261019.021455.UTC SBBSecho 3.38-Linux master/22cbda6be5
2:292/854 @20261019.041617 D'Bridge 4
2:292/854@Ward_Dossche @20261019.031900.UTC O/T-Track+ 2.85

Answered in 15m

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

Answered
MSGID
2:5001/100@fidonet 6ac30492
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:59 UTC
Answered
2026-10-05 02:15 UTC by SBBSecho, 4:4/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 01:59 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:59 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 04:01 local – D'Bridge 4
4 2:292/854 2026-10-05 03:04 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines
2:5001/100@fidonet @20261005.015943.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.015944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.040103 D'Bridge 4
2:292/854@Ward_Dossche @20261005.030400.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:07 UTC – SBBSecho 3.38-Linux master/22cbda6be5
2 2:292/854 2026-10-05 04:14 local – D'Bridge 4
Raw Via lines
4:902/26 @20261005.020708.UTC SBBSecho 3.38-Linux master/22cbda6be5
2:292/854 @20261005.041401 D'Bridge 4

Answered in 8m

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

Answered
MSGID
2:5001/100@fidonet 6ab08eac
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 02:04 UTC by SBBSecho, 4:4/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 01:55 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:55 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 03:56 local – D'Bridge 4
4 2:292/854 2026-09-21 02:58 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines
2:5001/100@fidonet @20260921.015554.UTC FidoMail 97f43bf5
2:5020/715 @20260921.015555.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.035617 D'Bridge 4
2:292/854@Ward_Dossche @20260921.025859.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 01:59 UTC – SBBSecho 3.37-Linux master/~3dc56fb6b5
2 2:292/854 2026-09-21 04:01 local – D'Bridge 4
3 2:292/854 2026-09-21 03:04 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines
4:902/26 @20260921.015954.UTC SBBSecho 3.37-Linux master/~3dc56fb6b5
2:292/854 @20260921.040113 D'Bridge 4
2:292/854@Ward_Dossche @20260921.030400.UTC O/T-Track+ 2.85

Answered in 7m

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

Answered
MSGID
2:5001/100@fidonet 6a9e1566
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 01:44 UTC by SBBSecho, 4:4/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:37 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 03:39 local – D'Bridge 4
Raw Via lines
2:5020/715 @20260907.013741.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.033910 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 01:40 UTC – SBBSecho 3.37-Linux master/6556a01a9
2 2:292/854 2026-09-07 03:41 local – D'Bridge 4
3 2:292/854 2026-09-07 02:43 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines
4:902/26 @20260907.014029.UTC SBBSecho 3.37-Linux master/6556a01a9
2:292/854 @20260907.034113 D'Bridge 4
2:292/854@Ward_Dossche @20260907.024359.UTC O/T-Track+ 2.85

Replies

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

pong Pong: PING

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

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.021455.UTC SBBSecho 3.38-Linux master/22cbda6be5
  • 2:292/854 @20261019.041617 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.031900.UTC O/T-Track+ 2.85

Software

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

pong Pong: PING

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

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

Software

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

pong Pong: PING

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

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.015954.UTC SBBSecho 3.37-Linux master/~3dc56fb6b5
  • 2:292/854 @20260921.040113 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.030400.UTC O/T-Track+ 2.85

Software

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

pong Pong: PING

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

Path quoted in this reply

2:5020/715→2:292/854

This reply's own Via lines

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

Software

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