NodelistDB

Netmail PING — 1:104/117

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

← All PING/TRACE nodes Node history for 1:104/117

Routed ping · 2026-10-18 22:59 UTC

No answer

Nothing came back within seven days of sending.

No answer
MSGID
2:5001/100@fidonet 6ad54f62
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-18 22:59 UTC
Note
no answer within 168h0m0s

Routed ping · 2026-10-04 22:59 UTC

No answer

Nothing came back within seven days of sending.

No answer
MSGID
2:5001/100@fidonet 6ac2da62
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-04 22:59 UTC
Note
no answer within 168h0m0s

Routed ping · 2026-09-20 22:55 UTC

No answer

Nothing came back within seven days of sending.

No answer
MSGID
2:5001/100@fidonet 6ab0647d
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-20 22:55 UTC
Note
no answer within 168h0m0s

Routed ping · 2026-09-06 22:49 UTC

Answered in 15m

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

Answered
MSGID
2:5001/100@fidonet 6a9dee0f
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-06 22:49 UTC
Answered
2026-09-06 23:04 UTC by Ping Robot, 1:104/117

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→1:229/426→-1h 0m1:229/426
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-06 22:49 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 00:51 local – D'Bridge 4
3 2:292/854 2026-09-06 23:53 UTC +1h 4m O/T-Track+ 2.85
4 1:229/426 2026-09-06 18:53 local – D'Bridge 4
5 1:229/426 2026-09-06 22:53 UTC -1h 0m O/T-Track+ 2.85
Raw Via lines 
2:5020/715 @20260906.224948.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.005107 D'Bridge 4
2:292/854@Ward_Dossche @20260906.235359.UTC O/T-Track+ 2.85
1:229/426 @20260906.185340 D'Bridge 4
1:229/426@fidonet @20260906.225340.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:104/117→+5s2:5020/1042→+4s2:5020/715
#NodeStampedElapsedSoftware
1 1:104/117 2026-09-06 23:04 UTC – hpt/lnx 1.9 2024-03-02
2 2:5020/1042 2026-09-06 23:04 UTC +5s RNtrack 2.3.0/Lnx/Perl
3 2:5020/715 2026-09-06 23:04 UTC +4s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
1:104/117 @20260906.230438.UTC hpt/lnx 1.9 2024-03-02
2:5020/1042 @20260906.230443.UTC RNtrack 2.3.0/Lnx/Perl
2:5020/715 @20260906.230447.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-09-06 23:04 UTC

pong Pong

From Ping Robot, 1:104/117 · answers 2:5001/100@fidonet 6a9dee0f

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854→1:229/426→-1h 0m1:229/426

This reply's own Via lines

  • 1:104/117 @20260906.230438.UTC hpt/lnx 1.9 2024-03-02
  • 2:5020/1042 @20260906.230443.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:5020/715 @20260906.230447.UTC RNtrack 2.3.0/Lnx/Perl