NodelistDB

Netmail PING — 3:712/848

Every FTS-4010 PING sent to 3:712/848 (fidonet), with the path each one walked.

← All PING/TRACE nodes Node history for 3:712/848

Routed ping · 2026-10-19 01:59 UTC

Answered in 16m

The robot at 3:712/848 bounced it back 16m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad57992
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:59 UTC
Answered
2026-10-19 02:16 UTC by mailer-daemon, 3:712/848
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→+5s2:5080/102
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:59 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:59 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-10-19 01:59 UTC +5s hpt/lnx 1.4.0-sta 27-11-08
Raw Via lines 
2:5001/100@fidonet @20261019.015942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.015944.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20261019.015949.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→+57s2:5020/715
#NodeStampedElapsedSoftware
1 3:712/848 2026-10-19 02:05 UTC – RNtrack 1.21/W32
2 3:712/848 2026-10-19 02:05 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
3 2:280/5003.0 2026-10-19 02:15 UTC +10m FIDOGATE/ftntoss 4.4.14
4 2:5020/715 2026-10-19 02:15 UTC +57s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
3:712/848 @20261019.020501.UTC RNtrack 1.21/W32
3:712/848 @20261019.020501.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
2:280/5003.0 @20261019.021502.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20261019.021559.UTC RNtrack 2.3.0/Lnx/Perl

Routed ping · 2026-10-05 01:49 UTC

Answered in 14m

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

Answered
MSGID
2:5001/100@fidonet 6ac3023b
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:49 UTC
Answered
2026-10-05 02:04 UTC by mailer-daemon, 3:712/848
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→+2s2:5080/102
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:49 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:49 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-10-05 01:49 UTC +2s hpt/lnx 1.4.0-sta 27-11-08
Raw Via lines 
2:5001/100@fidonet @20261005.014943.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.014944.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20261005.014946.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→+8m2:280/5003.0→+29s2:5020/715
#NodeStampedElapsedSoftware
1 3:712/848 2026-10-05 01:56 UTC – RNtrack 1.21/W32
2 3:712/848 2026-10-05 01:56 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
3 2:280/5003.0 2026-10-05 02:04 UTC +8m FIDOGATE/ftntoss 4.4.14
4 2:5020/715 2026-10-05 02:04 UTC +29s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
3:712/848 @20261005.015601.UTC RNtrack 1.21/W32
3:712/848 @20261005.015601.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
2:280/5003.0 @20261005.020401.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20261005.020430.UTC RNtrack 2.3.0/Lnx/Perl

Routed ping · 2026-09-21 01:45 UTC

Answered in 36m

The robot at 3:712/848 bounced it back 36m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab08c55
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:45 UTC
Answered
2026-09-21 02:22 UTC by mailer-daemon, 3:712/848
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→+5s2:5080/102
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:45 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:45 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-09-21 01:46 UTC +5s hpt/lnx 1.4.0-sta 27-11-08
Raw Via lines 
2:5001/100@fidonet @20260921.014553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.014555.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20260921.014600.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→+1m2:280/5003.0→+28m2:5020/715
#NodeStampedElapsedSoftware
1 3:712/848 2026-09-21 01:53 UTC – RNtrack 1.21/W32
2 3:712/848 2026-09-21 01:53 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
3 2:280/5003.0 2026-09-21 01:54 UTC +1m FIDOGATE/ftntoss 4.4.14
4 2:5020/715 2026-09-21 02:22 UTC +28m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
3:712/848 @20260921.015301.UTC RNtrack 1.21/W32
3:712/848 @20260921.015301.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
2:280/5003.0 @20260921.015402.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20260921.022208.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 6m

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

Answered
MSGID
2:5001/100@fidonet 6a9e130f
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 01:34 UTC by mailer-daemon, 3:712/848
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→+1s2:5080/102
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:27 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5080/102 2026-09-07 01:27 UTC +1s hpt/lnx 1.4.0-sta 27-11-08
Raw Via lines 
2:5020/715 @20260907.012741.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20260907.012742.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→+2m2:280/5003.0→+23s2:5020/715
#NodeStampedElapsedSoftware
1 3:712/848 2026-09-07 01:32 UTC – RNtrack 1.21/W32
2 3:712/848 2026-09-07 01:32 UTC +1s hpt/w32-mvcdll 1.9.0-cur 04-11-15
3 2:280/5003.0 2026-09-07 01:34 UTC +2m FIDOGATE/ftntoss 4.4.14
4 2:5020/715 2026-09-07 01:34 UTC +23s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
3:712/848 @20260907.013200.UTC RNtrack 1.21/W32
3:712/848 @20260907.013201.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
2:280/5003.0 @20260907.013401.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20260907.013424.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-10-19 02:16 UTC

pong ping/traceroute report

From mailer-daemon, 3:712/848 · answers 2:5001/100@fidonet 6ad57992

Path quoted in this reply

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

This reply's own Via lines

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

2026-10-19 02:00 UTC

trace PONG: PING

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

Path quoted in this reply

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

This reply's own Via lines

  • 2:5080/102 @20261019.015949.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

2026-10-05 02:04 UTC

pong ping/traceroute report

From mailer-daemon, 3:712/848 · answers 2:5001/100@fidonet 6ac3023b

Path quoted in this reply

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

This reply's own Via lines

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

2026-10-05 01:50 UTC

trace PONG: PING

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

Path quoted in this reply

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

This reply's own Via lines

  • 2:5080/102 @20261005.014946.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

2026-09-21 02:22 UTC

pong ping/traceroute report

From mailer-daemon, 3:712/848 · answers 2:5001/100@fidonet 6ab08c55

Path quoted in this reply

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

This reply's own Via lines

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

2026-09-21 01:46 UTC

trace PONG: PING

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

Path quoted in this reply

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

This reply's own Via lines

  • 2:5080/102 @20260921.014600.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

2026-09-07 01:34 UTC

trace PONG: PING

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

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:5080/102 @20260907.012742.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

2026-09-07 01:34 UTC

pong ping/traceroute report

From mailer-daemon, 3:712/848 · answers 2:5001/100@fidonet 6a9e130f

Path quoted in this reply

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

This reply's own Via lines

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