NodelistDB

Netmail PING — 2:6035/3

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

← All PING/TRACE nodes Node history for 2:6035/3

Routed ping · 2026-09-07 01:17 UTC

Answered in 32m

The robot at 2:6035/3 bounced it back 32m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e10b4
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:17 UTC
Answered
2026-09-07 01:50 UTC by Ping Robot, 2:6035/3

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:17 UTC – RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5020/715 @20260907.011740.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:6035/3→+30m2:5020/715
#NodeStampedElapsedSoftware
1 2:6035/3 2026-09-07 01:20 UTC – hpt/w64-mvcdll 1.9 2024-02-05
2 2:5020/715 2026-09-07 01:50 UTC +30m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:6035/3 @20260907.012004.UTC hpt/w64-mvcdll 1.9 2024-02-05
2:5020/715 @20260907.015006.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-09-07 01:50 UTC

pong Pong

From Ping Robot, 2:6035/3 · answers 2:5001/100@fidonet 6a9e10b4

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:6035/3 @20260907.012004.UTC hpt/w64-mvcdll 1.9 2024-02-05
  • 2:5020/715 @20260907.015006.UTC RNtrack 2.3.0/Lnx/Perl