NodelistDB

Netmail PING — 2:5019/40

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

← All PING/TRACE nodes Node history for 2:5019/40

Routed ping · 2026-09-07 00:59 UTC

Answered in 12m

The robot at 2:5019/40 bounced it back 12m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0c87
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 01:12 UTC by Netmail Daemon, 2:5019/40

Outbound path

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

2:5020/715
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:11 UTC – RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5020/715 @20260907.011159.UTC RNtrack 2.3.0/Lnx/Perl

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.

2:5019/40→+28s2:5020/715
#NodeStampedElapsedSoftware
1 2:5019/40 2026-09-07 01:12 UTC – hpt-nsf/linux 5d92f5b96d 2025-08-31
2 2:5020/715 2026-09-07 01:12 UTC +28s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5019/40 @20260907.011200.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
2:5020/715 @20260907.011228.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-09-07 01:12 UTC

pong PONG: PING

From Netmail Daemon, 2:5019/40 · answers 2:5001/100@fidonet 6a9e0c87

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:5019/40 @20260907.011200.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20260907.011228.UTC RNtrack 2.3.0/Lnx/Perl