NodelistDB

Netmail PING — 1:320/0

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

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

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 6a9df76c
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.232949.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/0, newest first, as the sending node received it. Pongs and transit notices are matched to the ping they answer.

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 6a9df76c

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 6a9df76c

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)   ---