NodelistDB

Netmail PING — 1:1/19

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

← All PING/TRACE nodes Node history for 1:1/19

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

Answered in 20m

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

Answered
MSGID
2:5001/100@fidonet 6ad13306
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-15 20:09 UTC
Answered
2026-10-15 20:30 UTC by Ping service, 1:1/19
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→+1s2:5020/715→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-15 20:09 UTC – FidoMail e334310e
2 2:5020/715 2026-10-15 20:09 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-15 22:11 local – D'Bridge 4
4 2:292/854 2026-10-15 21:14 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261015.200942.UTC FidoMail e334310e
2:5020/715 @20261015.200943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261015.221109 D'Bridge 4
2:292/854@Ward_Dossche @20261015.211400.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→+16s1:229/426→2:292/854→+1h 13m2:292/854
#NodeStampedElapsedSoftware
1 1:320/219 2026-10-15 20:15 UTC – mbfido 1.1.7.2
2 1:229/426 2026-10-15 16:15 local – D'Bridge 4
3 1:229/426 2026-10-15 20:15 UTC +16s O/T-Track+ 2.85
4 2:292/854 2026-10-15 22:26 local – D'Bridge 4
5 2:292/854 2026-10-15 21:29 UTC +1h 13m O/T-Track+ 2.85
Raw Via lines 
1:320/219@fidonet @20261015.201508.UTC mbfido 1.1.7.2
1:229/426 @20261015.161524 D'Bridge 4
1:229/426@fidonet @20261015.201524.UTC O/T-Track+ 2.85
2:292/854 @20261015.222608 D'Bridge 4
2:292/854@Ward_Dossche @20261015.212900.UTC O/T-Track+ 2.85

Routed ping · 2026-10-01 20:09 UTC

Answered in 19m

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

Answered
MSGID
2:5001/100@fidonet 6abebe06
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-01 20:09 UTC
Answered
2026-10-01 20:29 UTC by Ping service, 1:1/19
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→2:5020/715→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-01 20:09 UTC – FidoMail a8bc7247
2 2:5020/715 2026-10-01 20:09 UTC – RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-01 22:11 local – D'Bridge 4
4 2:292/854 2026-10-01 21:14 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
2:5001/100@fidonet @20261001.200942.UTC FidoMail a8bc7247
2:5020/715 @20261001.200942.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261001.221112 D'Bridge 4
2:292/854@Ward_Dossche @20261001.211401.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-01 20:14 UTC – mbfido 1.1.7.2
2 1:229/426 2026-10-01 16:16 local – D'Bridge 4
3 1:229/426 2026-10-01 20:16 UTC +1m O/T-Track+ 2.85
4 2:292/854 2026-10-01 22:26 local – D'Bridge 4
5 2:292/854 2026-10-01 21:28 UTC +1h 12m O/T-Track+ 2.85
Raw Via lines 
1:320/219@fidonet @20261001.201440.UTC mbfido 1.1.7.2
1:229/426 @20261001.161603 D'Bridge 4
1:229/426@fidonet @20261001.201603.UTC O/T-Track+ 2.85
2:292/854 @20261001.222606 D'Bridge 4
2:292/854@Ward_Dossche @20261001.212859.UTC O/T-Track+ 2.85

Routed ping · 2026-09-17 20:05 UTC

Answered in 18m

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

Answered
MSGID
2:5001/100@fidonet 6aac4821
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-17 20:05 UTC
Answered
2026-09-17 20:24 UTC by Ping service, 1:1/19
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 3m2:292/854
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-17 20:05 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-17 22:06 local – D'Bridge 4
3 2:292/854 2026-09-17 21:09 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260917.200554.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260917.220608 D'Bridge 4
2:292/854@Ward_Dossche @20260917.210900.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→-45s1:229/426→2:292/854→+1h 14m2:292/854
#NodeStampedElapsedSoftware
1 1:320/219 2026-09-17 20:10 UTC – mbfido 1.1.7.2
2 1:229/426 2026-09-17 16:09 local – D'Bridge 4
3 1:229/426 2026-09-17 20:09 UTC -45s O/T-Track+ 2.85
4 2:292/854 2026-09-17 22:21 local – D'Bridge 4
5 2:292/854 2026-09-17 21:23 UTC +1h 14m O/T-Track+ 2.85
Raw Via lines 
1:320/219@fidonet @20260917.201000.UTC mbfido 1.1.7.2
1:229/426 @20260917.160915 D'Bridge 4
1:229/426@fidonet @20260917.200915.UTC O/T-Track+ 2.85
2:292/854 @20260917.222108 D'Bridge 4
2:292/854@Ward_Dossche @20260917.212359.UTC O/T-Track+ 2.85

Routed ping · 2026-09-03 20:00 UTC

Answered in 4h 9m

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

Answered
MSGID
2:5001/100@fidonet 6a99d1e1
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-03 20:10 UTC
Answered
2026-09-04 00:09 UTC by Ping service, 1:1/19
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 7m2:292/854
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-03 23:41 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-04 01:46 local – D'Bridge 4
3 2:292/854 2026-09-04 00:49 UTC +1h 7m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260903.234155.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260904.014604 D'Bridge 4
2:292/854@Ward_Dossche @20260904.004900.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→-39s1:229/426→2:292/854→+1h 19m2:292/854
#NodeStampedElapsedSoftware
1 1:320/219 2026-09-03 23:49 UTC – mbfido 1.1.7.2
2 1:229/426 2026-09-03 19:49 local – D'Bridge 4
3 1:229/426 2026-09-03 23:49 UTC -39s O/T-Track+ 2.85
4 2:292/854 2026-09-04 02:04 local – D'Bridge 4
5 2:292/854 2026-09-04 01:08 UTC +1h 19m O/T-Track+ 2.85
Raw Via lines 
1:320/219@fidonet @20260903.234954.UTC mbfido 1.1.7.2
1:229/426 @20260903.194915 D'Bridge 4
1:229/426@fidonet @20260903.234915.UTC O/T-Track+ 2.85
2:292/854 @20260904.020405 D'Bridge 4
2:292/854@Ward_Dossche @20260904.010859.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-15 20:30 UTC

pong Re: Your PING Request

From Ping service, 1:1/19 · answers 2:5001/100@fidonet 6ad13306

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20261015.201508.UTC mbfido 1.1.7.2
  • 1:229/426 @20261015.161524 D'Bridge 4
  • 1:229/426@fidonet @20261015.201524.UTC O/T-Track+ 2.85
  • 2:292/854 @20261015.222608 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261015.212900.UTC O/T-Track+ 2.85

Software

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

2026-10-01 20:29 UTC

pong Re: Your PING Request

From Ping service, 1:1/19 · answers 2:5001/100@fidonet 6abebe06

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20261001.201440.UTC mbfido 1.1.7.2
  • 1:229/426 @20261001.161603 D'Bridge 4
  • 1:229/426@fidonet @20261001.201603.UTC O/T-Track+ 2.85
  • 2:292/854 @20261001.222606 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261001.212859.UTC O/T-Track+ 2.85

Software

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

2026-09-17 20:24 UTC

pong Re: Your PING Request

From Ping service, 1:1/19 · answers 2:5001/100@fidonet 6aac4821

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20260917.201000.UTC mbfido 1.1.7.2
  • 1:229/426 @20260917.160915 D'Bridge 4
  • 1:229/426@fidonet @20260917.200915.UTC O/T-Track+ 2.85
  • 2:292/854 @20260917.222108 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260917.212359.UTC O/T-Track+ 2.85

Software

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

2026-09-04 00:09 UTC

pong Re: Your PING Request

From Ping service, 1:1/19 · answers 2:5001/100@fidonet 6a99d1e1

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20260903.234954.UTC mbfido 1.1.7.2
  • 1:229/426 @20260903.194915 D'Bridge 4
  • 1:229/426@fidonet @20260903.234915.UTC O/T-Track+ 2.85
  • 2:292/854 @20260904.020405 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260904.010859.UTC O/T-Track+ 2.85

Software

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