NodelistDB

Netmail PING — 2:5019/400

Every FTS-4010 PING sent to 2:5019/400 (fidonet), with the path each one walked.

← All PING/TRACE nodes Node history for 2:5019/400

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

Answered in 1m

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

Answered
MSGID
2:5001/100@fidonet 6ad5702f
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-19 01:20 UTC by GaNJaNET Robot, 2:5019/400

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→+4s2:5019/40
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:19 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:19 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5019/40 2026-10-19 01:19 UTC +4s hpt-nsf/linux 5d92f5b96d 2025-08-31
Raw Via lines 
2:5001/100@fidonet @20261019.011942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.011944.UTC RNtrack 2.3.0/Lnx/Perl
2:5019/40 @20261019.011948.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31

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:5019/400→2:5019/40→+48s2:5020/715
#NodeStampedElapsedSoftware
1 2:5019/400 2026-10-19 04:19 local – Phfito/1.3.6/cvs
2 2:5019/40 2026-10-19 01:20 UTC – hpt-nsf/linux 5d92f5b96d 2025-08-31
3 2:5020/715 2026-10-19 01:20 UTC +48s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5019/400 @20261019.041950 Phfito/1.3.6/cvs
2:5019/40 @20261019.012003.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
2:5020/715 @20261019.012051.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 1m

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

Answered
MSGID
2:5001/100@fidonet 6ac2f8da
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-05 01:11 UTC by GaNJaNET Robot, 2:5019/400

Outbound path

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

2:5001/100→+3s2:5020/715→+3s2:5019/40
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:09 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:09 UTC +3s RNtrack 2.3.0/Lnx/Perl
3 2:5019/40 2026-10-05 01:09 UTC +3s hpt-nsf/linux 5d92f5b96d 2025-08-31
Raw Via lines 
2:5001/100@fidonet @20261005.010943.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.010946.UTC RNtrack 2.3.0/Lnx/Perl
2:5019/40 @20261005.010949.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31

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:5019/400→2:5019/40→+55s2:5020/715
#NodeStampedElapsedSoftware
1 2:5019/400 2026-10-05 04:10 local – Phfito/1.3.6/cvs
2 2:5019/40 2026-10-05 01:10 UTC – hpt-nsf/linux 5d92f5b96d 2025-08-31
3 2:5020/715 2026-10-05 01:11 UTC +55s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5019/400 @20261005.041017 Phfito/1.3.6/cvs
2:5019/40 @20261005.011021.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
2:5020/715 @20261005.011116.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 1m

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

Answered
MSGID
2:5001/100@fidonet 6ab082f5
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 01:07 UTC by GaNJaNET Robot, 2:5019/400

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:5019/40
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:05 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:05 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5019/40 2026-09-21 01:05 UTC +2s hpt-nsf/linux 5d92f5b96d 2025-08-31
Raw Via lines 
2:5001/100@fidonet @20260921.010553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.010555.UTC RNtrack 2.3.0/Lnx/Perl
2:5019/40 @20260921.010557.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31

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:5019/400→2:5019/40→+46s2:5020/715
#NodeStampedElapsedSoftware
1 2:5019/400 2026-09-21 04:06 local – Phfito/1.3.6/cvs
2 2:5019/40 2026-09-21 01:06 UTC – hpt-nsf/linux 5d92f5b96d 2025-08-31
3 2:5020/715 2026-09-21 01:07 UTC +46s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5019/400 @20260921.040621 Phfito/1.3.6/cvs
2:5019/40 @20260921.010636.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
2:5020/715 @20260921.010722.UTC RNtrack 2.3.0/Lnx/Perl

Routed ping · 2026-09-07 00:59 UTC

Answered in 13m

The robot at 2:5019/400 bounced it back 13m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0c88
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 01:13 UTC by GaNJaNET Robot, 2:5019/400

Outbound path

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

2:5020/715→+1s2:5019/40
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:11 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5019/40 2026-09-07 01:12 UTC +1s hpt-nsf/linux 5d92f5b96d 2025-08-31
Raw Via lines 
2:5020/715 @20260907.011159.UTC RNtrack 2.3.0/Lnx/Perl
2:5019/40 @20260907.011200.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31

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:5019/400→2:5019/40→+56s2:5020/715
#NodeStampedElapsedSoftware
1 2:5019/400 2026-09-07 04:12 local – Phfito/1.3.6/cvs
2 2:5019/40 2026-09-07 01:12 UTC – hpt-nsf/linux 5d92f5b96d 2025-08-31
3 2:5020/715 2026-09-07 01:13 UTC +56s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5019/400 @20260907.041228 Phfito/1.3.6/cvs
2:5019/40 @20260907.011232.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
2:5020/715 @20260907.011328.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-10-19 01:20 UTC

pong Answer to your PING

From GaNJaNET Robot, 2:5019/400 · answers 2:5001/100@fidonet 6ad5702f

Path quoted in this reply

2:5001/100→+2s2:5020/715→+4s2:5019/40

This reply's own Via lines

  • 2:5019/400 @20261019.041950 Phfito/1.3.6/cvs
  • 2:5019/40 @20261019.012003.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20261019.012051.UTC RNtrack 2.3.0/Lnx/Perl

2026-10-19 01:19 UTC

pong PONG: PING

From Netmail Daemon, 2:5019/40 · answers 2:5001/100@fidonet 6ad5702f

Path quoted in this reply

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

This reply's own Via lines

  • 2:5019/40 @20261019.011948.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20261019.011950.UTC RNtrack 2.3.0/Lnx/Perl

2026-10-05 01:11 UTC

pong Answer to your PING

From GaNJaNET Robot, 2:5019/400 · answers 2:5001/100@fidonet 6ac2f8da

Path quoted in this reply

2:5001/100→+3s2:5020/715→+3s2:5019/40

This reply's own Via lines

  • 2:5019/400 @20261005.041017 Phfito/1.3.6/cvs
  • 2:5019/40 @20261005.011021.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20261005.011116.UTC RNtrack 2.3.0/Lnx/Perl

2026-10-05 01:10 UTC

pong PONG: PING

From Netmail Daemon, 2:5019/40 · answers 2:5001/100@fidonet 6ac2f8da

Path quoted in this reply

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

This reply's own Via lines

  • 2:5019/40 @20261005.010949.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20261005.011017.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-21 01:07 UTC

pong Answer to your PING

From GaNJaNET Robot, 2:5019/400 · answers 2:5001/100@fidonet 6ab082f5

Path quoted in this reply

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

This reply's own Via lines

  • 2:5019/400 @20260921.040621 Phfito/1.3.6/cvs
  • 2:5019/40 @20260921.010636.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20260921.010722.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-21 01:06 UTC

pong PONG: PING

From Netmail Daemon, 2:5019/40 · answers 2:5001/100@fidonet 6ab082f5

Path quoted in this reply

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

This reply's own Via lines

  • 2:5019/40 @20260921.010557.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20260921.010621.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-07 01:13 UTC

pong Answer to your PING

From GaNJaNET Robot, 2:5019/400 · answers 2:5001/100@fidonet 6a9e0c88

Path quoted in this reply

2:5020/715→+1s2:5019/40

This reply's own Via lines

  • 2:5019/400 @20260907.041228 Phfito/1.3.6/cvs
  • 2:5019/40 @20260907.011232.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20260907.011328.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-07 01:12 UTC

pong PONG: PING

From Netmail Daemon, 2:5019/40 · answers 2:5001/100@fidonet 6a9e0c88

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:5019/40 @20260907.011200.UTC hpt-nsf/linux 5d92f5b96d 2025-08-31
  • 2:5020/715 @20260907.011228.UTC RNtrack 2.3.0/Lnx/Perl