NodelistDB

Netmail PING — 3:772/1

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

← All PING/TRACE nodes Node history for 3:772/1

Routed ping · 2026-10-19 02:09 UTC

Answered in 9m

The robot at 3:772/1 bounced it back 9m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad57be9
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-19 02:19 UTC by Ping Robot, 3:772/1
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→+7m3:712/848→3:712/848
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 02:09 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 02:09 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-10-19 02:09 UTC +5s hpt/lnx 1.4.0-sta 27-11-08
4 3:712/848 2026-10-19 02:17 UTC +7m RNtrack 1.21/W32
5 3:712/848 2026-10-19 02:17 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
Raw Via lines 
2:5001/100@fidonet @20261019.020943.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.020944.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20261019.020949.UTC hpt/lnx 1.4.0-sta 27-11-08
3:712/848 @20261019.021701.UTC RNtrack 1.21/W32
3:712/848 @20261019.021701.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
#NodeStampedElapsedSoftware
1 3:770/1 2026-10-19 02:17 UTC – hpt/lnx 1.9 2024-02-05
2 2:292/854 2026-10-19 04:19 local – D'Bridge 4
Raw Via lines 
3:770/1 @20261019.021717.UTC hpt/lnx 1.9 2024-02-05
2:292/854 @20261019.041911 D'Bridge 4

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

Answered in 15m

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

Answered
MSGID
2:5001/100@fidonet 6ac30491
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:59 UTC
Answered
2026-10-05 02:15 UTC by Ping Robot, 3:772/1
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→+4m2:5020/715→+2s2:5080/102→+3m3:712/848→3:712/848
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:59 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 02:04 UTC +4m RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-10-05 02:04 UTC +2s hpt/lnx 1.4.0-sta 27-11-08
4 3:712/848 2026-10-05 02:08 UTC +3m RNtrack 1.21/W32
5 3:712/848 2026-10-05 02:08 UTC – hpt/w32-mvcdll 1.9.0-cur 04-11-15
Raw Via lines 
2:5001/100@fidonet @20261005.015943.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.020430.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20261005.020432.UTC hpt/lnx 1.4.0-sta 27-11-08
3:712/848 @20261005.020801.UTC RNtrack 1.21/W32
3:712/848 @20261005.020801.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 02:10 UTC – hpt/lnx 1.9 2024-02-05
2 2:292/854 2026-10-05 04:11 local – D'Bridge 4
3 2:292/854 2026-10-05 03:14 UTC +1h 3m O/T-Track+ 2.85
Raw Via lines 
3:770/1 @20261005.021003.UTC hpt/lnx 1.9 2024-02-05
2:292/854 @20261005.041107 D'Bridge 4
2:292/854@Ward_Dossche @20261005.031400.UTC O/T-Track+ 2.85

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

Answered in 8m

The robot at 3:772/1 bounced it back 8m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab08eab
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 02:04 UTC by Ping Robot, 3:772/1
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→+3m3:712/848→+1s3:712/848
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:55 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:55 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:5080/102 2026-09-21 01:56 UTC +5s hpt/lnx 1.4.0-sta 27-11-08
4 3:712/848 2026-09-21 01:59 UTC +3m RNtrack 1.21/W32
5 3:712/848 2026-09-21 01:59 UTC +1s hpt/w32-mvcdll 1.9.0-cur 04-11-15
Raw Via lines 
2:5001/100@fidonet @20260921.015554.UTC FidoMail 97f43bf5
2:5020/715 @20260921.015555.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20260921.015600.UTC hpt/lnx 1.4.0-sta 27-11-08
3:712/848 @20260921.015901.UTC RNtrack 1.21/W32
3:712/848 @20260921.015902.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-21 01:59 UTC – hpt/lnx 1.9 2024-02-05
2 2:292/854 2026-09-21 04:01 local – D'Bridge 4
3 2:292/854 2026-09-21 03:04 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
3:770/1 @20260921.015932.UTC hpt/lnx 1.9 2024-02-05
2:292/854 @20260921.040113 D'Bridge 4
2:292/854@Ward_Dossche @20260921.030400.UTC O/T-Track+ 2.85

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

Answered in 17m

The robot at 3:772/1 bounced it back 17m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e1565
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:37 UTC
Answered
2026-09-07 01:54 UTC by Ping Robot, 3:772/1
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→+8m3:712/848→+1s3:712/848
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:44 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5080/102 2026-09-07 01:44 UTC +2s hpt/lnx 1.4.0-sta 27-11-08
3 3:712/848 2026-09-07 01:53 UTC +8m RNtrack 1.21/W32
4 3:712/848 2026-09-07 01:53 UTC +1s hpt/w32-mvcdll 1.9.0-cur 04-11-15
Raw Via lines 
2:5020/715 @20260907.014422.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20260907.014424.UTC hpt/lnx 1.4.0-sta 27-11-08
3:712/848 @20260907.015300.UTC RNtrack 1.21/W32
3:712/848 @20260907.015301.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
#NodeStampedElapsedSoftware
1 3:770/1 2026-09-07 01:53 UTC – hpt/lnx 1.9 2024-02-05
2 2:292/854 2026-09-07 03:54 local – D'Bridge 4
Raw Via lines 
3:770/1 @20260907.015313.UTC hpt/lnx 1.9 2024-02-05
2:292/854 @20260907.035410 D'Bridge 4

Evidence

Replies

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

2026-10-19 02:25 UTC

trace ping/traceroute report

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

Path quoted in this reply

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

This reply's own Via lines

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

2026-10-19 02:19 UTC

pong Pong

From Ping Robot, 3:772/1 · answers 2:5001/100@fidonet 6ad57be9

Path quoted in this reply

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

This reply's own Via lines

  • 3:770/1 @20261019.021717.UTC hpt/lnx 1.9 2024-02-05
  • 2:292/854 @20261019.041911 D'Bridge 4

2026-10-19 02:10 UTC

trace PONG: PING

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

Path quoted in this reply

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

This reply's own Via lines

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

trace ping/traceroute report

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

Path quoted in this reply

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

This reply's own Via lines

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

2026-10-05 02:15 UTC

pong Pong

From Ping Robot, 3:772/1 · answers 2:5001/100@fidonet 6ac30491

Path quoted in this reply

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

This reply's own Via lines

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

2026-10-05 02:06 UTC

trace PONG: PING

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

Path quoted in this reply

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

This reply's own Via lines

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

Path quoted in this reply

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

This reply's own Via lines

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

2026-09-21 02:04 UTC

pong Pong

From Ping Robot, 3:772/1 · answers 2:5001/100@fidonet 6ab08eab

Path quoted in this reply

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

This reply's own Via lines

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

2026-09-21 01:57 UTC

trace PONG: PING

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

Path quoted in this reply

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

This reply's own Via lines

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

pong Pong

From Ping Robot, 3:772/1 · answers 2:5001/100@fidonet 6a9e1565

Path quoted in this reply

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

This reply's own Via lines

  • 3:770/1 @20260907.015313.UTC hpt/lnx 1.9 2024-02-05
  • 2:292/854 @20260907.035410 D'Bridge 4

2026-09-07 01:54 UTC

trace ping/traceroute report

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

Path quoted in this reply

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

This reply's own Via lines

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

2026-09-07 01:45 UTC

trace PONG: PING

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

Path quoted in this reply

2:5020/715

This reply's own Via lines

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