Answered in 8m

The robot at 2:460/58 bounced it back 8m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad56b80
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-19 01:07 UTC by Ping Robot, 2:460/58

Outbound path

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

2:5001/100→+7m2:5020/715→+5s2:5020/1042
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 00:59 UTC – FidoMail v0.1.5
2 2:5020/715 2026-10-19 01:07 UTC +7m RNtrack 2.3.0/Lnx/Perl
3 2:5020/1042 2026-10-19 01:07 UTC +5s RNtrack 2.3.0/Lnx/Perl
Raw Via lines
2:5001/100@fidonet @20261019.005942.UTC FidoMail v0.1.5
2:5020/715 @20261019.010728.UTC RNtrack 2.3.0/Lnx/Perl
2:5020/1042 @20261019.010733.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:460/58
#NodeStampedElapsedSoftware
1 2:460/58 2026-10-19 01:07 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines
2:460/58 @20261019.010746.UTC hpt/lnx 1.9 2024-03-02

Answered in 5m

The robot at 2:460/58 bounced it back 5m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2f680
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-05 01:04 UTC by Ping Robot, 2:460/58

Outbound path

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

2:5001/100→+4m2:5020/715→+4s2:5020/1042
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 00:59 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:04 UTC +4m RNtrack 2.3.0/Lnx/Perl
3 2:5020/1042 2026-10-05 01:04 UTC +4s RNtrack 2.3.0/Lnx/Perl
Raw Via lines
2:5001/100@fidonet @20261005.005942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.010425.UTC RNtrack 2.3.0/Lnx/Perl
2:5020/1042 @20261005.010429.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:460/58
#NodeStampedElapsedSoftware
1 2:460/58 2026-10-05 01:04 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines
2:460/58 @20261005.010434.UTC hpt/lnx 1.9 2024-03-02

Answered in 9m

The robot at 2:460/58 bounced it back 9m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab0809b
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 01:05 UTC by Ping Robot, 2:460/58

Outbound path

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

2:5001/100→+9m2:5020/715→+5s2:5020/1042
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 00:55 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:05 UTC +9m RNtrack 2.3.0/Lnx/Perl
3 2:5020/1042 2026-09-21 01:05 UTC +5s RNtrack 2.3.0/Lnx/Perl
Raw Via lines
2:5001/100@fidonet @20260921.005553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.010522.UTC RNtrack 2.3.0/Lnx/Perl
2:5020/1042 @20260921.010527.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:460/58
#NodeStampedElapsedSoftware
1 2:460/58 2026-09-21 01:05 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines
2:460/58 @20260921.010531.UTC hpt/lnx 1.9 2024-03-02

Answered in 27s

The robot at 2:460/58 bounced it back 27s after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0a2e
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 00:50 UTC by Ping Robot, 2:460/58

Outbound path

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

2:5020/715→+1s2:5020/1042
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 00:49 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5020/1042 2026-09-07 00:49 UTC +1s RNtrack 2.3.0/Lnx/Perl
Raw Via lines
2:5020/715 @20260907.004949.UTC RNtrack 2.3.0/Lnx/Perl
2:5020/1042 @20260907.004950.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:460/58
#NodeStampedElapsedSoftware
1 2:460/58 2026-09-07 00:50 UTC – hpt/lnx 1.9 2024-03-02
Raw Via lines
2:460/58 @20260907.005011.UTC hpt/lnx 1.9 2024-03-02

Replies

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

pong unsecure Pong

From Ping Robot, 2:460/58 · answers 2:5001/100@fidonet 6ad56b80

Path quoted in this reply

2:5001/100→+7m2:5020/715→+5s2:5020/1042

This reply's own Via lines

  • 2:460/58 @20261019.010746.UTC hpt/lnx 1.9 2024-03-02

pong unsecure Pong

From Ping Robot, 2:460/58 · answers 2:5001/100@fidonet 6ac2f680

Path quoted in this reply

2:5001/100→+4m2:5020/715→+4s2:5020/1042

This reply's own Via lines

  • 2:460/58 @20261005.010434.UTC hpt/lnx 1.9 2024-03-02

pong unsecure Pong

From Ping Robot, 2:460/58 · answers 2:5001/100@fidonet 6ab0809b

Path quoted in this reply

2:5001/100→+9m2:5020/715→+5s2:5020/1042

This reply's own Via lines

  • 2:460/58 @20260921.010531.UTC hpt/lnx 1.9 2024-03-02

pong unsecure Pong

From Ping Robot, 2:460/58 · answers 2:5001/100@fidonet 6a9e0a2e

Path quoted in this reply

2:5020/715→+1s2:5020/1042

This reply's own Via lines

  • 2:460/58 @20260907.005011.UTC hpt/lnx 1.9 2024-03-02