NodelistDB

Netmail PING — 1:320/119

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

← All PING/TRACE nodes Node history for 1:320/119

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

Answered in 19m

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

Answered
MSGID
2:5001/100@fidonet 6ad558bf
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-18 23:39 UTC
Answered
2026-10-18 23:59 UTC by O/T-Track+ 2.85, 1:320/119
Robot
O/T+ 2.85 CS59356
Transit notices
1

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→-59m1:320/219
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-18 23:39 UTC – FidoMail v0.1.5
2 2:5020/715 2026-10-18 23:39 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 01:41 local – D'Bridge 4
4 2:292/854 2026-10-19 00:44 UTC +1h 4m O/T-Track+ 2.85
5 1:320/219 2026-10-18 23:44 UTC -59m mbfido 1.1.7.2
Raw Via lines 
2:5001/100@fidonet @20261018.233942.UTC FidoMail v0.1.5
2:5020/715 @20261018.233944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.014114 D'Bridge 4
2:292/854@Ward_Dossche @20261019.004400.UTC O/T-Track+ 2.85
1:320/219@fidonet @20261018.234447.UTC mbfido 1.1.7.2

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/119→1:320/119→+1m1:320/219→1:229/426→+12s1:229/426→2:292/854→+1h 6m2:292/854
#NodeStampedElapsedSoftware
1 1:320/119 2026-10-18 23:50 UTC – O/T-Track+ 2.85
2 1:320/119 2026-10-18 23:50 UTC – FastEcho 1.46.1 10045
3 1:320/219 2026-10-18 23:52 UTC +1m mbfido 1.1.7.2
4 1:229/426 2026-10-18 19:52 local – D'Bridge 4
5 1:229/426 2026-10-18 23:52 UTC +12s O/T-Track+ 2.85
6 2:292/854 2026-10-19 01:56 local – D'Bridge 4
7 2:292/854 2026-10-19 00:58 UTC +1h 6m O/T-Track+ 2.85
Raw Via lines 
1:320/119@fidonet @20261018.235050.UTC O/T-Track+ 2.85
1:320/119@fidonet @20261018.235050.UTC FastEcho 1.46.1 10045
1:320/219@fidonet @20261018.235247.UTC mbfido 1.1.7.2
1:229/426 @20261018.195259 D'Bridge 4
1:229/426@fidonet @20261018.235259.UTC O/T-Track+ 2.85
2:292/854 @20261019.015616 D'Bridge 4
2:292/854@Ward_Dossche @20261019.005859.UTC O/T-Track+ 2.85

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

Answered in 45m

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

Answered
MSGID
2:5001/100@fidonet 6ac2e3bf
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-04 23:39 UTC
Answered
2026-10-05 00:25 UTC by O/T-Track+ 2.85, 1:320/119
Robot
O/T+ 2.85 CS59356
Transit notices
1

Outbound path

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

2:5001/100→+10m2:5020/715→2:292/854→+1h 4m2:292/854→-58m1:320/219
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-04 23:39 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-04 23:49 UTC +10m RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 01:51 local – D'Bridge 4
4 2:292/854 2026-10-05 00:54 UTC +1h 4m O/T-Track+ 2.85
5 1:320/219 2026-10-04 23:55 UTC -58m mbfido 1.1.7.2
Raw Via lines 
2:5001/100@fidonet @20261004.233942.UTC FidoMail d6aaa2b3
2:5020/715 @20261004.234943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.015108 D'Bridge 4
2:292/854@Ward_Dossche @20261005.005400.UTC O/T-Track+ 2.85
1:320/219@fidonet @20261004.235513.UTC mbfido 1.1.7.2

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/119→1:320/119→+3m1:320/219→1:229/426→+5m1:229/426→2:292/854
#NodeStampedElapsedSoftware
1 1:320/119 2026-10-04 23:58 UTC – O/T-Track+ 2.85
2 1:320/119 2026-10-04 23:58 UTC – FastEcho 1.46.1 10045
3 1:320/219 2026-10-05 00:01 UTC +3m mbfido 1.1.7.2
4 1:229/426 2026-10-04 20:06 local – D'Bridge 4
5 1:229/426 2026-10-05 00:06 UTC +5m O/T-Track+ 2.85
6 2:292/854 2026-10-05 02:24 local – D'Bridge 4
Raw Via lines 
1:320/119@fidonet @20261004.235808.UTC O/T-Track+ 2.85
1:320/119@fidonet @20261004.235808.UTC FastEcho 1.46.1 10045
1:320/219@fidonet @20261005.000108.UTC mbfido 1.1.7.2
1:229/426 @20261004.200610 D'Bridge 4
1:229/426@fidonet @20261005.000640.UTC O/T-Track+ 2.85
2:292/854 @20261005.022405 D'Bridge 4

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

Answered in 13m

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

Answered
MSGID
2:5001/100@fidonet 6ab06dda
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-20 23:35 UTC
Answered
2026-09-20 23:49 UTC by O/T-Track+ 2.85, 1:320/119
Robot
O/T+ 2.85 CS59356
Transit notices
1

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 3m2:292/854→-59m1:320/219
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-20 23:35 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-20 23:35 UTC +3s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 01:36 local – D'Bridge 4
4 2:292/854 2026-09-21 00:39 UTC +1h 3m O/T-Track+ 2.85
5 1:320/219 2026-09-20 23:39 UTC -59m mbfido 1.1.7.2
Raw Via lines 
2:5001/100@fidonet @20260920.233553.UTC FidoMail 97f43bf5
2:5020/715 @20260920.233556.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.013621 D'Bridge 4
2:292/854@Ward_Dossche @20260921.003900.UTC O/T-Track+ 2.85
1:320/219@fidonet @20260920.233932.UTC mbfido 1.1.7.2

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/119→1:320/119→+27s1:320/219→1:229/426→+8s1:229/426→2:292/854
#NodeStampedElapsedSoftware
1 1:320/119 2026-09-20 23:41 UTC – O/T-Track+ 2.85
2 1:320/119 2026-09-20 23:41 UTC – FastEcho 1.46.1 10045
3 1:320/219 2026-09-20 23:42 UTC +27s mbfido 1.1.7.2
4 1:229/426 2026-09-20 19:42 local – D'Bridge 4
5 1:229/426 2026-09-20 23:42 UTC +8s O/T-Track+ 2.85
6 2:292/854 2026-09-21 01:49 local – D'Bridge 4
Raw Via lines 
1:320/119@fidonet @20260920.234140.UTC O/T-Track+ 2.85
1:320/119@fidonet @20260920.234140.UTC FastEcho 1.46.1 10045
1:320/219@fidonet @20260920.234207.UTC mbfido 1.1.7.2
1:229/426 @20260920.194215 D'Bridge 4
1:229/426@fidonet @20260920.234215.UTC O/T-Track+ 2.85
2:292/854 @20260921.014915 D'Bridge 4

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

Answered in 40m

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

Answered
MSGID
2:5001/100@fidonet 6a9df76d
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-06 23:29 UTC
Answered
2026-09-07 00:09 UTC by O/T-Track+ 2.85, 1:320/119
Robot
O/T+ 2.85 CS59356
Transit notices
1

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→-59m1:320/219
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-06 23:29 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 01:31 local – D'Bridge 4
3 2:292/854 2026-09-07 00:33 UTC +1h 4m O/T-Track+ 2.85
4 1:320/219 2026-09-06 23:34 UTC -59m mbfido 1.1.7.2
Raw Via lines 
2:5020/715 @20260906.232955.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.013114 D'Bridge 4
2:292/854@Ward_Dossche @20260907.003359.UTC O/T-Track+ 2.85
1:320/219@fidonet @20260906.233458.UTC mbfido 1.1.7.2

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/119→1:320/119→+8m1:320/219→1:229/426→-37s1:229/426→2:292/854→+1h 24m2:292/854
#NodeStampedElapsedSoftware
1 1:320/119 2026-09-06 23:37 UTC – O/T-Track+ 2.85
2 1:320/119 2026-09-06 23:37 UTC – FastEcho 1.46.1 10045
3 1:320/219 2026-09-06 23:45 UTC +8m mbfido 1.1.7.2
4 1:229/426 2026-09-06 19:44 local – D'Bridge 4
5 1:229/426 2026-09-06 23:44 UTC -37s O/T-Track+ 2.85
6 2:292/854 2026-09-07 02:06 local – D'Bridge 4
7 2:292/854 2026-09-07 01:08 UTC +1h 24m O/T-Track+ 2.85
Raw Via lines 
1:320/119@fidonet @20260906.233724.UTC O/T-Track+ 2.85
1:320/119@fidonet @20260906.233724.UTC FastEcho 1.46.1 10045
1:320/219@fidonet @20260906.234528.UTC mbfido 1.1.7.2
1:229/426 @20260906.194451 D'Bridge 4
1:229/426@fidonet @20260906.234451.UTC O/T-Track+ 2.85
2:292/854 @20260907.020613 D'Bridge 4
2:292/854@Ward_Dossche @20260907.010859.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-18 23:59 UTC

trace Re: Your PING Request

From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6ad558bf

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.234447.UTC mbfido 1.1.7.2
  • 1:229/426 @20261018.194459 D'Bridge 4
  • 1:229/426@fidonet @20261018.234459.UTC O/T-Track+ 2.85
  • 2:292/854 @20261019.015616 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.005859.UTC O/T-Track+ 2.85

Software

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

2026-10-18 23:59 UTC

pong "Ping"-response processing at destination

From O/T-Track+ 2.85, 1:320/119 · answers 2:5001/100@fidonet 6ad558bf

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:292/854→+1h 4m2:292/854→-59m1:320/219

This reply's own Via lines

  • 1:320/119@fidonet @20261018.235050.UTC O/T-Track+ 2.85
  • 1:320/119@fidonet @20261018.235050.UTC FastEcho 1.46.1 10045
  • 1:320/219@fidonet @20261018.235247.UTC mbfido 1.1.7.2
  • 1:229/426 @20261018.195259 D'Bridge 4
  • 1:229/426@fidonet @20261018.235259.UTC O/T-Track+ 2.85
  • 2:292/854 @20261019.015616 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.005859.UTC O/T-Track+ 2.85

Software

O/T+ 2.85 CS59356   --- FidoMail v0.1.5

2026-10-05 00:25 UTC

pong "Ping"-response processing at destination

From O/T-Track+ 2.85, 1:320/119 · answers 2:5001/100@fidonet 6ac2e3bf

Path quoted in this reply

2:5001/100→+10m2:5020/715→2:292/854→+1h 4m2:292/854→-58m1:320/219

This reply's own Via lines

  • 1:320/119@fidonet @20261004.235808.UTC O/T-Track+ 2.85
  • 1:320/119@fidonet @20261004.235808.UTC FastEcho 1.46.1 10045
  • 1:320/219@fidonet @20261005.000108.UTC mbfido 1.1.7.2
  • 1:229/426 @20261004.200610 D'Bridge 4
  • 1:229/426@fidonet @20261005.000640.UTC O/T-Track+ 2.85
  • 2:292/854 @20261005.022405 D'Bridge 4

Software

O/T+ 2.85 CS59356   --- FidoMail v0.1.4-211-gd6aaa2b3

2026-10-05 00:05 UTC

trace Re: Your PING Request

From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6ac2e3bf

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20261004.235513.UTC mbfido 1.1.7.2
  • 1:229/426 @20261004.195542 D'Bridge 4
  • 1:229/426@fidonet @20261004.235542.UTC O/T-Track+ 2.85
  • 2:292/854 @20261005.020104 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.010400.UTC O/T-Track+ 2.85

Software

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

2026-09-20 23:49 UTC

trace Re: Your PING Request

From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6ab06dda

Path quoted in this reply

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

This reply's own Via lines

  • 1:320/219@fidonet @20260920.233932.UTC mbfido 1.1.7.2
  • 1:229/426 @20260920.193912 D'Bridge 4
  • 1:229/426@fidonet @20260920.233912.UTC O/T-Track+ 2.85
  • 2:292/854 @20260921.014915 D'Bridge 4

Software

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

2026-09-20 23:49 UTC

pong "Ping"-response processing at destination

From O/T-Track+ 2.85, 1:320/119 · answers 2:5001/100@fidonet 6ab06dda

Path quoted in this reply

2:5001/100→+3s2:5020/715→2:292/854→+1h 3m2:292/854→-59m1:320/219

This reply's own Via lines

  • 1:320/119@fidonet @20260920.234140.UTC O/T-Track+ 2.85
  • 1:320/119@fidonet @20260920.234140.UTC FastEcho 1.46.1 10045
  • 1:320/219@fidonet @20260920.234207.UTC mbfido 1.1.7.2
  • 1:229/426 @20260920.194215 D'Bridge 4
  • 1:229/426@fidonet @20260920.234215.UTC O/T-Track+ 2.85
  • 2:292/854 @20260921.014915 D'Bridge 4

Software

O/T+ 2.85 CS59356   --- FidoMail v0.1.4-122-g97f43bf5

2026-09-07 00:09 UTC

pong "Ping"-response processing at destination

From O/T-Track+ 2.85, 1:320/119 · answers 2:5001/100@fidonet 6a9df76d

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854→-59m1:320/219

This reply's own Via lines

  • 1:320/119@fidonet @20260906.233724.UTC O/T-Track+ 2.85
  • 1:320/119@fidonet @20260906.233724.UTC FastEcho 1.46.1 10045
  • 1:320/219@fidonet @20260906.234528.UTC mbfido 1.1.7.2
  • 1:229/426 @20260906.194451 D'Bridge 4
  • 1:229/426@fidonet @20260906.234451.UTC O/T-Track+ 2.85
  • 2:292/854 @20260907.020613 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.010859.UTC O/T-Track+ 2.85

Software

O/T+ 2.85 CS59356   --- FidoMail v0.1.4-20-g980f7aa

2026-09-06 23:39 UTC

trace Re: Your PING Request

From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6a9df76d

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.233458.UTC mbfido 1.1.7.2
  • 1:229/426 @20260906.193417 D'Bridge 4
  • 1:229/426@fidonet @20260906.233417.UTC O/T-Track+ 2.85
  • 2:292/854 @20260907.013910 D'Bridge 4

Software

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