Answered in 15m

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

Answered
MSGID
2:5001/100@fidonet 6ad57736
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:49 UTC
Answered
2026-10-19 02:05 UTC by mailer-daemon, 3:3/0
Transit notices
1

Outbound path

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

2:5001/100→+1s2:5020/715→+6s2:5080/102
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:49 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:49 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-10-19 01:49 UTC +6s hpt/lnx 1.4.0-sta 27-11-08
Raw Via lines
2:5001/100@fidonet @20261019.014942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.014943.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20261019.014949.UTC hpt/lnx 1.4.0-sta 27-11-08

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.

3:712/848→+1s3:712/848→+8m2:280/5003.0→+58s2:5020/715
#NodeStampedElapsedSoftware
1 3:712/848 2026-10-19 01:56 UTC – RNtrack 1.21/W32
2 3:712/848 2026-10-19 01:56 UTC +1s hpt/w32-mvcdll 1.9.0-cur 04-11-15
3 2:280/5003.0 2026-10-19 02:04 UTC +8m FIDOGATE/ftntoss 4.4.14
4 2:5020/715 2026-10-19 02:05 UTC +58s RNtrack 2.3.0/Lnx/Perl
Raw Via lines
3:712/848 @20261019.015600.UTC RNtrack 1.21/W32
3:712/848 @20261019.015601.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
2:280/5003.0 @20261019.020402.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20261019.020500.UTC RNtrack 2.3.0/Lnx/Perl

Answered in 14m

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

Answered
MSGID
2:5001/100@fidonet 6ac2ffe1
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:39 UTC
Answered
2026-10-05 01:54 UTC by mailer-daemon, 3:3/0
Transit notices
1

Outbound path

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

2:5001/100→+2s2:5020/715→+2s2:5080/102
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:39 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:39 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-10-05 01:39 UTC +2s hpt/lnx 1.4.0-sta 27-11-08
Raw Via lines
2:5001/100@fidonet @20261005.013942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.013944.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20261005.013946.UTC hpt/lnx 1.4.0-sta 27-11-08

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.

3:712/848→3:712/848→+10m2:280/5003.0→+28s2:5020/715
#NodeStampedElapsedSoftware
1 3:712/848 2026-10-05 01:44 UTC – RNtrack 1.21/W32
2 3:712/848 2026-10-05 01:44 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
3 2:280/5003.0 2026-10-05 01:54 UTC +10m FIDOGATE/ftntoss 4.4.14
4 2:5020/715 2026-10-05 01:54 UTC +28s RNtrack 2.3.0/Lnx/Perl
Raw Via lines
3:712/848 @20261005.014401.UTC RNtrack 1.21/W32
3:712/848 @20261005.014401.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
2:280/5003.0 @20261005.015402.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20261005.015430.UTC RNtrack 2.3.0/Lnx/Perl

Answered in 46m

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

Answered
MSGID
2:5001/100@fidonet 6ab089fc
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:35 UTC
Answered
2026-09-21 02:22 UTC by mailer-daemon, 3:3/0
Transit notices
1

Outbound path

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

2:5001/100→+1s2:5020/715→+5s2:5080/102
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:35 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:35 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-09-21 01:35 UTC +5s hpt/lnx 1.4.0-sta 27-11-08
Raw Via lines
2:5001/100@fidonet @20260921.013553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.013554.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20260921.013559.UTC hpt/lnx 1.4.0-sta 27-11-08

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.

3:712/848→3:712/848→+3m2:280/5003.0→+38m2:5020/715
#NodeStampedElapsedSoftware
1 3:712/848 2026-09-21 01:41 UTC – RNtrack 1.21/W32
2 3:712/848 2026-09-21 01:41 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
3 2:280/5003.0 2026-09-21 01:44 UTC +3m FIDOGATE/ftntoss 4.4.14
4 2:5020/715 2026-09-21 02:22 UTC +38m RNtrack 2.3.0/Lnx/Perl
Raw Via lines
3:712/848 @20260921.014101.UTC RNtrack 1.21/W32
3:712/848 @20260921.014101.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
2:280/5003.0 @20260921.014402.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20260921.022208.UTC RNtrack 2.3.0/Lnx/Perl

Answered in 6m

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

Answered
MSGID
2:5001/100@fidonet 6a9e10b5
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 01:24 UTC by mailer-daemon, 3:3/0
Transit notices
1

Outbound path

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

2:5020/715→+2s2:5080/102
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:17 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5080/102 2026-09-07 01:17 UTC +2s hpt/lnx 1.4.0-sta 27-11-08
Raw Via lines
2:5020/715 @20260907.011740.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20260907.011742.UTC hpt/lnx 1.4.0-sta 27-11-08

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.

3:712/848→+1s3:712/848→+1m2:280/5003.0→+21s2:5020/715
#NodeStampedElapsedSoftware
1 3:712/848 2026-09-07 01:23 UTC – RNtrack 1.21/W32
2 3:712/848 2026-09-07 01:23 UTC +1s hpt/w32-mvcdll 1.9.0-cur 04-11-15
3 2:280/5003.0 2026-09-07 01:24 UTC +1m FIDOGATE/ftntoss 4.4.14
4 2:5020/715 2026-09-07 01:24 UTC +21s RNtrack 2.3.0/Lnx/Perl
Raw Via lines
3:712/848 @20260907.012300.UTC RNtrack 1.21/W32
3:712/848 @20260907.012301.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
2:280/5003.0 @20260907.012401.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20260907.012422.UTC RNtrack 2.3.0/Lnx/Perl

Replies

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

pong ping/traceroute report

From mailer-daemon, 3:3/0 · answers 2:5001/100@fidonet 6ad57736

Path quoted in this reply

2:5001/100→+1s2:5020/715→+6s2:5080/102

This reply's own Via lines

  • 3:712/848 @20261019.015600.UTC RNtrack 1.21/W32
  • 3:712/848 @20261019.015601.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
  • 2:280/5003.0 @20261019.020402.UTC FIDOGATE/ftntoss 4.4.14
  • 2:5020/715 @20261019.020500.UTC RNtrack 2.3.0/Lnx/Perl

trace PONG: PING

From Ping-Pong Robot, 2:5080/102 · answers 2:5001/100@fidonet 6ad57736

Path quoted in this reply

2:5001/100→+1s2:5020/715

This reply's own Via lines

  • 2:5080/102 @20261019.014949.UTC hpt/lnx 1.4.0-sta 27-11-08

Software

hpt/lnx 1.4.0-sta 27-11-08   --- pong.pl,v 1.6 2010/02/01 23:47:21

pong ping/traceroute report

From mailer-daemon, 3:3/0 · answers 2:5001/100@fidonet 6ac2ffe1

Path quoted in this reply

2:5001/100→+2s2:5020/715→+2s2:5080/102

This reply's own Via lines

  • 3:712/848 @20261005.014401.UTC RNtrack 1.21/W32
  • 3:712/848 @20261005.014401.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
  • 2:280/5003.0 @20261005.015402.UTC FIDOGATE/ftntoss 4.4.14
  • 2:5020/715 @20261005.015430.UTC RNtrack 2.3.0/Lnx/Perl

trace PONG: PING

From Ping-Pong Robot, 2:5080/102 · answers 2:5001/100@fidonet 6ac2ffe1

Path quoted in this reply

2:5001/100→+2s2:5020/715

This reply's own Via lines

  • 2:5080/102 @20261005.013946.UTC hpt/lnx 1.4.0-sta 27-11-08

Software

hpt/lnx 1.4.0-sta 27-11-08   --- pong.pl,v 1.6 2010/02/01 23:47:21

pong ping/traceroute report

From mailer-daemon, 3:3/0 · answers 2:5001/100@fidonet 6ab089fc

Path quoted in this reply

2:5001/100→+1s2:5020/715→+5s2:5080/102

This reply's own Via lines

  • 3:712/848 @20260921.014101.UTC RNtrack 1.21/W32
  • 3:712/848 @20260921.014101.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
  • 2:280/5003.0 @20260921.014402.UTC FIDOGATE/ftntoss 4.4.14
  • 2:5020/715 @20260921.022208.UTC RNtrack 2.3.0/Lnx/Perl

trace PONG: PING

From Ping-Pong Robot, 2:5080/102 · answers 2:5001/100@fidonet 6ab089fc

Path quoted in this reply

2:5001/100→+1s2:5020/715

This reply's own Via lines

  • 2:5080/102 @20260921.013559.UTC hpt/lnx 1.4.0-sta 27-11-08

Software

hpt/lnx 1.4.0-sta 27-11-08   --- pong.pl,v 1.6 2010/02/01 23:47:21

pong ping/traceroute report

From mailer-daemon, 3:3/0 · answers 2:5001/100@fidonet 6a9e10b5

Path quoted in this reply

2:5020/715→+2s2:5080/102

This reply's own Via lines

  • 3:712/848 @20260907.012300.UTC RNtrack 1.21/W32
  • 3:712/848 @20260907.012301.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
  • 2:280/5003.0 @20260907.012401.UTC FIDOGATE/ftntoss 4.4.14
  • 2:5020/715 @20260907.012422.UTC RNtrack 2.3.0/Lnx/Perl

trace PONG: PING

From Ping-Pong Robot, 2:5080/102 · answers 2:5001/100@fidonet 6a9e10b5

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:5080/102 @20260907.011742.UTC hpt/lnx 1.4.0-sta 27-11-08

Software

hpt/lnx 1.4.0-sta 27-11-08   --- pong.pl,v 1.6 2010/02/01 23:47:21