Answered in 30s

The robot at 2:5058/0 bounced it back 30s after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0ff2
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 01:14 UTC by Ping Robot, 2:5058/0

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:14 UTC RNtrack 2.3.0/Lnx/Perl
Raw Via lines
2:5020/715 @20260907.011426.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:5058/104+10s2:5020/715
#NodeStampedElapsedSoftware
1 2:5058/104 2026-09-07 01:14 UTC hpt/lnx 1.9 2023-02-18
2 2:5020/715 2026-09-07 01:14 UTC +10s RNtrack 2.3.0/Lnx/Perl
Raw Via lines
2:5058/104 @20260907.011443.UTC hpt/lnx 1.9 2023-02-18
2:5020/715 @20260907.011453.UTC RNtrack 2.3.0/Lnx/Perl

Replies

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

pong Pong

From Ping Robot, 2:5058/0 · answers 2:5001/100@fidonet 6a9e0ff2

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:5058/104 @20260907.011443.UTC hpt/lnx 1.9 2023-02-18
  • 2:5020/715 @20260907.011453.UTC RNtrack 2.3.0/Lnx/Perl