NodelistDB

Netmail PING — 3:57/0

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

← All PING/TRACE nodes Node history for 3:57/0

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

Answered in 25m

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

Answered
MSGID
2:5001/100@fidonet 6ad57737
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:49 UTC
Answered
2026-10-19 02:14 UTC by Ping Robot, 3:57/0
Transit notices
2

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→+6m3:712/848→+1s3:712/848
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:49 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:49 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-10-19 01:49 UTC +5s hpt/lnx 1.4.0-sta 27-11-08
4 3:712/848 2026-10-19 01:56 UTC +6m RNtrack 1.21/W32
5 3:712/848 2026-10-19 01:56 UTC +1s hpt/w32-mvcdll 1.9.0-cur 04-11-15
Raw Via lines 
2:5001/100@fidonet @20261019.014942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.014944.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20261019.014949.UTC hpt/lnx 1.4.0-sta 27-11-08
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

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:770/1→2:292/854→+1h 3m2:292/854
#NodeStampedElapsedSoftware
1 3:770/1 2026-10-19 02:10 UTC – hpt/lnx 1.9 2024-02-05
2 2:292/854 2026-10-19 04:11 local – D'Bridge 4
3 2:292/854 2026-10-19 03:13 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
3:770/1 @20261019.021049.UTC hpt/lnx 1.9 2024-02-05
2:292/854 @20261019.041114 D'Bridge 4
2:292/854@Ward_Dossche @20261019.031359.UTC O/T-Track+ 2.85

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

Answered in 10m

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

Answered
MSGID
2:5001/100@fidonet 6ac2ffe2
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:39 UTC
Answered
2026-10-05 01:50 UTC by Ping Robot, 3:57/0
Transit notices
2

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→+4m3:712/848→3:712/848
#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
4 3:712/848 2026-10-05 01:44 UTC +4m RNtrack 1.21/W32
5 3:712/848 2026-10-05 01:44 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
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
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

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:770/1→2:292/854→+1h 3m2:292/854
#NodeStampedElapsedSoftware
1 3:770/1 2026-10-05 01:45 UTC – hpt/lnx 1.9 2024-02-05
2 2:292/854 2026-10-05 03:46 local – D'Bridge 4
3 2:292/854 2026-10-05 02:49 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
3:770/1 @20261005.014517.UTC hpt/lnx 1.9 2024-02-05
2:292/854 @20261005.034603 D'Bridge 4
2:292/854@Ward_Dossche @20261005.024900.UTC O/T-Track+ 2.85

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

Answered in 13m

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

Answered
MSGID
2:5001/100@fidonet 6ab089fd
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:35 UTC
Answered
2026-09-21 01:49 UTC by Ping Robot, 3:57/0
Transit notices
2

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→+5m3:712/848→3:712/848
#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
4 3:712/848 2026-09-21 01:41 UTC +5m RNtrack 1.21/W32
5 3:712/848 2026-09-21 01:41 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
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
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

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:770/1→2:292/854→+1h 5m2:292/854
#NodeStampedElapsedSoftware
1 3:770/1 2026-09-21 01:43 UTC – hpt/lnx 1.9 2024-02-05
2 2:292/854 2026-09-21 03:46 local – D'Bridge 4
3 2:292/854 2026-09-21 02:49 UTC +1h 5m O/T-Track+ 2.85
Raw Via lines 
3:770/1 @20260921.014340.UTC hpt/lnx 1.9 2024-02-05
2:292/854 @20260921.034612 D'Bridge 4
2:292/854@Ward_Dossche @20260921.024900.UTC O/T-Track+ 2.85

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

Answered in 12m

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

Answered
MSGID
2:5001/100@fidonet 6a9e10b6
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:17 UTC
Answered
2026-09-07 01:29 UTC by Ping Robot, 3:57/0
Transit notices
2

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→+5m3:712/848→+1s3:712/848
#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
3 3:712/848 2026-09-07 01:23 UTC +5m RNtrack 1.21/W32
4 3:712/848 2026-09-07 01:23 UTC +1s hpt/w32-mvcdll 1.9.0-cur 04-11-15
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
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

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:770/1→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 3:770/1 2026-09-07 01:24 UTC – hpt/lnx 1.9 2024-02-05
2 2:292/854 2026-09-07 03:26 local – D'Bridge 4
3 2:292/854 2026-09-07 02:28 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
3:770/1 @20260907.012409.UTC hpt/lnx 1.9 2024-02-05
2:292/854 @20260907.032613 D'Bridge 4
2:292/854@Ward_Dossche @20260907.022859.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-19 02:14 UTC

pong Pong

From Ping Robot, 3:57/0 · answers 2:5001/100@fidonet 6ad57737

Path quoted in this reply

2:5001/100→+2s2:5020/715→+5s2:5080/102→+6m3:712/848→+1s3:712/848

This reply's own Via lines

  • 3:770/1 @20261019.021049.UTC hpt/lnx 1.9 2024-02-05
  • 2:292/854 @20261019.041114 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.031359.UTC O/T-Track+ 2.85

2026-10-19 02:05 UTC

trace ping/traceroute report

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

Path quoted in this reply

2:5001/100→+2s2:5020/715→+5s2: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

2026-10-19 01:50 UTC

trace PONG: PING

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

Path quoted in this reply

2:5001/100→+2s2: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

2026-10-05 01:54 UTC

trace ping/traceroute report

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

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

2026-10-05 01:50 UTC

pong Pong

From Ping Robot, 3:57/0 · answers 2:5001/100@fidonet 6ac2ffe2

Path quoted in this reply

2:5001/100→+2s2:5020/715→+2s2:5080/102→+4m3:712/848→3:712/848

This reply's own Via lines

  • 3:770/1 @20261005.014517.UTC hpt/lnx 1.9 2024-02-05
  • 2:292/854 @20261005.034603 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.024900.UTC O/T-Track+ 2.85

2026-10-05 01:40 UTC

trace PONG: PING

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

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

2026-09-21 02:22 UTC

trace ping/traceroute report

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

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

2026-09-21 01:49 UTC

pong Pong

From Ping Robot, 3:57/0 · answers 2:5001/100@fidonet 6ab089fd

Path quoted in this reply

2:5001/100→+1s2:5020/715→+5s2:5080/102→+5m3:712/848→3:712/848

This reply's own Via lines

  • 3:770/1 @20260921.014340.UTC hpt/lnx 1.9 2024-02-05
  • 2:292/854 @20260921.034612 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.024900.UTC O/T-Track+ 2.85

2026-09-21 01:36 UTC

trace PONG: PING

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

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

2026-09-07 01:29 UTC

pong Pong

From Ping Robot, 3:57/0 · answers 2:5001/100@fidonet 6a9e10b6

Path quoted in this reply

2:5020/715→+2s2:5080/102→+5m3:712/848→+1s3:712/848

This reply's own Via lines

  • 3:770/1 @20260907.012409.UTC hpt/lnx 1.9 2024-02-05
  • 2:292/854 @20260907.032613 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.022859.UTC O/T-Track+ 2.85

2026-09-07 01:24 UTC

trace ping/traceroute report

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

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

2026-09-07 01:18 UTC

trace PONG: PING

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

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