NodelistDB

Netmail PING — 2:550/278

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

← All PING/TRACE nodes Node history for 2:550/278

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

Answered in 3m

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

Answered
MSGID
2:5001/100@fidonet 6a9e10b3
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 01:20 UTC by PING Robot, 2:550/278

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:550/278→+3m2:5020/715
#NodeStampedElapsedSoftware
1 2:550/278 2026-09-07 01:17 UTC – hpt/lnx 1.9 2023-02-24
2 2:5020/715 2026-09-07 01:20 UTC +3m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:550/278 @20260907.011741.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20260907.012046.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-09-07 01:20 UTC

pong PING reply: PING

From PING Robot, 2:550/278 · answers 2:5001/100@fidonet 6a9e10b3

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:550/278 @20260907.011741.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20260907.012046.UTC RNtrack 2.3.0/Lnx/Perl