NodelistDB

Netmail PING — 1:16/0

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

← All PING/TRACE nodes Node history for 1:16/0

Routed ping · 2026-10-18 23:19 UTC

Answered in 14m

The robot at 1:16/0 bounced it back 14m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad55411
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-18 23:19 UTC
Answered
2026-10-18 23:34 UTC by Ping service, 1:16/0
Robot
MBSE-FIDO 1.1.7.2 (Linux-x86_64)

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 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-18 23:19 UTC – FidoMail v0.1.5
2 2:5020/715 2026-10-18 23:19 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 01:21 local – D'Bridge 4
4 2:292/854 2026-10-19 00:24 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261018.231942.UTC FidoMail v0.1.5
2:5020/715 @20261018.231944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.012112 D'Bridge 4
2:292/854@Ward_Dossche @20261019.002400.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.

1:320/219→1:229/426→+57s1:229/426→2:292/854→+1h 8m2:292/854
#NodeStampedElapsedSoftware
1 1:320/219 2026-10-18 23:24 UTC – mbfido 1.1.7.2
2 1:229/426 2026-10-18 19:25 local – D'Bridge 4
3 1:229/426 2026-10-18 23:25 UTC +57s O/T-Track+ 2.85
4 2:292/854 2026-10-19 01:31 local – D'Bridge 4
5 2:292/854 2026-10-19 00:34 UTC +1h 8m O/T-Track+ 2.85
Raw Via lines 
1:320/219@fidonet @20261018.232447.UTC mbfido 1.1.7.2
1:229/426 @20261018.192544 D'Bridge 4
1:229/426@fidonet @20261018.232544.UTC O/T-Track+ 2.85
2:292/854 @20261019.013112 D'Bridge 4
2:292/854@Ward_Dossche @20261019.003402.UTC O/T-Track+ 2.85

Routed ping · 2026-10-04 23:19 UTC

Answered in 20m

The robot at 1:16/0 bounced it back 20m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2df11
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-04 23:19 UTC
Answered
2026-10-04 23:40 UTC by Ping service, 1:16/0
Robot
MBSE-FIDO 1.1.7.2 (Linux-x86_64)

Outbound path

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

2:5001/100→+3s2:5020/715→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-04 23:19 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-04 23:19 UTC +3s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 01:21 local – D'Bridge 4
4 2:292/854 2026-10-05 00:23 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261004.231942.UTC FidoMail d6aaa2b3
2:5020/715 @20261004.231945.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.012107 D'Bridge 4
2:292/854@Ward_Dossche @20261005.002359.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.

1:320/219→1:229/426→+1m1:229/426→2:292/854→+1h 12m2:292/854
#NodeStampedElapsedSoftware
1 1:320/219 2026-10-04 23:25 UTC – mbfido 1.1.7.2
2 1:229/426 2026-10-04 19:26 local – D'Bridge 4
3 1:229/426 2026-10-04 23:26 UTC +1m O/T-Track+ 2.85
4 2:292/854 2026-10-05 01:36 local – D'Bridge 4
5 2:292/854 2026-10-05 00:39 UTC +1h 12m O/T-Track+ 2.85
Raw Via lines 
1:320/219@fidonet @20261004.232513.UTC mbfido 1.1.7.2
1:229/426 @20261004.192623 D'Bridge 4
1:229/426@fidonet @20261004.232623.UTC O/T-Track+ 2.85
2:292/854 @20261005.013604 D'Bridge 4
2:292/854@Ward_Dossche @20261005.003900.UTC O/T-Track+ 2.85

Routed ping · 2026-09-20 23:15 UTC

Answered in 18m

The robot at 1:16/0 bounced it back 18m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab0692c
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-20 23:15 UTC
Answered
2026-09-20 23:34 UTC by Ping service, 1:16/0
Robot
MBSE-FIDO 1.1.7.2 (Linux-x86_64)

Outbound path

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

2:5001/100→+5s2:5020/715→2:292/854→+1h 2m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-20 23:15 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-20 23:15 UTC +5s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 01:16 local – D'Bridge 4
4 2:292/854 2026-09-21 00:18 UTC +1h 2m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20260920.231553.UTC FidoMail 97f43bf5
2:5020/715 @20260920.231558.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.011654 D'Bridge 4
2:292/854@Ward_Dossche @20260921.001834.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.

1:320/219→1:229/426→-38s1:229/426→2:292/854→+1h 15m2:292/854
#NodeStampedElapsedSoftware
1 1:320/219 2026-09-20 23:19 UTC – mbfido 1.1.7.2
2 1:229/426 2026-09-20 19:18 local – D'Bridge 4
3 1:229/426 2026-09-20 23:18 UTC -38s O/T-Track+ 2.85
4 2:292/854 2026-09-21 01:31 local – D'Bridge 4
5 2:292/854 2026-09-21 00:33 UTC +1h 15m O/T-Track+ 2.85
Raw Via lines 
1:320/219@fidonet @20260920.231932.UTC mbfido 1.1.7.2
1:229/426 @20260920.191854 D'Bridge 4
1:229/426@fidonet @20260920.231854.UTC O/T-Track+ 2.85
2:292/854 @20260921.013115 D'Bridge 4
2:292/854@Ward_Dossche @20260921.003359.UTC O/T-Track+ 2.85

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

Answered in 20m

The robot at 1:16/0 bounced it back 20m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9df2bf
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-06 23:09 UTC
Answered
2026-09-06 23:29 UTC by Ping service, 1:16/0
Robot
MBSE-FIDO 1.1.7.2 (Linux-x86_64)

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
#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
Raw Via lines 
2:5020/715 @20260906.230955.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

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:320/219→1:229/426→-46s1:229/426→2:292/854→+1h 14m2:292/854
#NodeStampedElapsedSoftware
1 1:320/219 2026-09-06 23:15 UTC – mbfido 1.1.7.2
2 1:229/426 2026-09-06 19:14 local – D'Bridge 4
3 1:229/426 2026-09-06 23:14 UTC -46s O/T-Track+ 2.85
4 2:292/854 2026-09-07 01:26 local – D'Bridge 4
5 2:292/854 2026-09-07 00:28 UTC +1h 14m O/T-Track+ 2.85
Raw Via lines 
1:320/219@fidonet @20260906.231501.UTC mbfido 1.1.7.2
1:229/426 @20260906.191415 D'Bridge 4
1:229/426@fidonet @20260906.231415.UTC O/T-Track+ 2.85
2:292/854 @20260907.012613 D'Bridge 4
2:292/854@Ward_Dossche @20260907.002859.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-18 23:34 UTC

pong Re: Your PING Request

From Ping service, 1:16/0 · answers 2:5001/100@fidonet 6ad55411

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20261018.232447.UTC mbfido 1.1.7.2
  • 1:229/426 @20261018.192544 D'Bridge 4
  • 1:229/426@fidonet @20261018.232544.UTC O/T-Track+ 2.85
  • 2:292/854 @20261019.013112 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.003402.UTC O/T-Track+ 2.85

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64)   ---

2026-10-04 23:40 UTC

pong Re: Your PING Request

From Ping service, 1:16/0 · answers 2:5001/100@fidonet 6ac2df11

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20261004.232513.UTC mbfido 1.1.7.2
  • 1:229/426 @20261004.192623 D'Bridge 4
  • 1:229/426@fidonet @20261004.232623.UTC O/T-Track+ 2.85
  • 2:292/854 @20261005.013604 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.003900.UTC O/T-Track+ 2.85

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64)   ---

2026-09-20 23:34 UTC

pong Re: Your PING Request

From Ping service, 1:16/0 · answers 2:5001/100@fidonet 6ab0692c

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20260920.231932.UTC mbfido 1.1.7.2
  • 1:229/426 @20260920.191854 D'Bridge 4
  • 1:229/426@fidonet @20260920.231854.UTC O/T-Track+ 2.85
  • 2:292/854 @20260921.013115 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.003359.UTC O/T-Track+ 2.85

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64)   ---

2026-09-06 23:29 UTC

pong Re: Your PING Request

From Ping service, 1:16/0 · answers 2:5001/100@fidonet 6a9df2bf

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20260906.231501.UTC mbfido 1.1.7.2
  • 1:229/426 @20260906.191415 D'Bridge 4
  • 1:229/426@fidonet @20260906.231415.UTC O/T-Track+ 2.85
  • 2:292/854 @20260907.012613 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.002859.UTC O/T-Track+ 2.85

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64)   ---