Answered in 11m

The robot at 2:463/68 bounced it back 11m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad56b7e
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:07 UTC
Answered
2026-10-19 01:10 UTC by Crazy Mail Robot, 2:463/68

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
#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
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

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:463/68
#NodeStampedElapsedSoftware
1 2:463/68 2026-10-19 01:10 UTC – hpt 1.3.0/lnx 17-09-02
Raw Via lines
2:463/68 @20261019.011007.UTC hpt 1.3.0/lnx 17-09-02

Answered in 6m

The robot at 2:463/68 bounced it back 6m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2f67e
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-05 01:05 UTC by Crazy Mail Robot, 2:463/68

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
#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
Raw Via lines
2:5001/100@fidonet @20261005.005942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.010425.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:463/68
#NodeStampedElapsedSoftware
1 2:463/68 2026-10-05 01:05 UTC – hpt 1.3.0/lnx 17-09-02
Raw Via lines
2:463/68 @20261005.010508.UTC hpt 1.3.0/lnx 17-09-02

Answered in 24m

The robot at 2:463/68 bounced it back 24m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab08099
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:05 UTC
Answered
2026-09-21 01:20 UTC by Crazy Mail Robot, 2:463/68

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
#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
Raw Via lines
2:5001/100@fidonet @20260921.005553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.010522.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:463/68
#NodeStampedElapsedSoftware
1 2:463/68 2026-09-21 01:20 UTC – hpt 1.3.0/lnx 17-09-02
Raw Via lines
2:463/68 @20260921.012005.UTC hpt 1.3.0/lnx 17-09-02

Answered in 1m

The robot at 2:463/68 bounced it back 1m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0a2c
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 00:50 UTC by Crazy Mail Robot, 2:463/68

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 00:49 UTC – RNtrack 2.3.0/Lnx/Perl
Raw Via lines
2:5020/715 @20260907.004948.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:463/68
#NodeStampedElapsedSoftware
1 2:463/68 2026-09-07 00:50 UTC – hpt 1.3.0/lnx 17-09-02
Raw Via lines
2:463/68 @20260907.005005.UTC hpt 1.3.0/lnx 17-09-02

Replies

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

pong Ping Receipt Response (Pong)

From Crazy Mail Robot, 2:463/68 · answers 2:5001/100@fidonet 6ad56b7e

Path quoted in this reply

2:5001/100→+7m2:5020/715

This reply's own Via lines

  • 2:463/68 @20261019.011007.UTC hpt 1.3.0/lnx 17-09-02

pong Ping Receipt Response (Pong)

From Crazy Mail Robot, 2:463/68 · answers 2:5001/100@fidonet 6ac2f67e

Path quoted in this reply

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

This reply's own Via lines

  • 2:463/68 @20261005.010508.UTC hpt 1.3.0/lnx 17-09-02

pong Ping Receipt Response (Pong)

From Crazy Mail Robot, 2:463/68 · answers 2:5001/100@fidonet 6ab08099

Path quoted in this reply

2:5001/100→+9m2:5020/715

This reply's own Via lines

  • 2:463/68 @20260921.012005.UTC hpt 1.3.0/lnx 17-09-02

pong Ping Receipt Response (Pong)

From Crazy Mail Robot, 2:463/68 · answers 2:5001/100@fidonet 6a9e0a2c

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:463/68 @20260907.005005.UTC hpt 1.3.0/lnx 17-09-02