NodelistDB

Netmail PING — 2:463/0

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

← All PING/TRACE nodes Node history for 2:463/0

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

Answered in 26m

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

Answered
MSGID
2:5001/100@fidonet 6ad56b81
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:07 UTC
Answered
2026-10-19 01:25 UTC by Ping Robot, 2:463/0

Outbound path

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

?→2:5001/100→+7m2:5020/715→+7m2:463/68
#NodeStampedElapsedSoftware
1 ? – – lines:
2 2:5001/100 2026-10-19 00:59 UTC – FidoMail v0.1.5
3 2:5020/715 2026-10-19 01:07 UTC +7m RNtrack 2.3.0/Lnx/Perl
4 2:463/68 2026-10-19 01:15 UTC +7m hpt 1.3.0/lnx 17-09-02
Raw Via lines 
lines:
2:5001/100@fidonet @20261019.005942.UTC FidoMail v0.1.5
2:5020/715 @20261019.010728.UTC RNtrack 2.3.0/Lnx/Perl
2:463/68 @20261019.011504.UTC hpt 1.3.0/lnx 17-09-02

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:463/0→2:463/1331→2:463/68
#NodeStampedElapsedSoftware
1 2:463/0 2026-10-19 01:15 local – .0000 FIDOGATE/ftntoss
2 2:463/1331 2026-10-19 01:20 local – .0000 FIDOGATE/ftntoss
3 2:463/68 2026-10-19 01:25 UTC – hpt 1.3.0/lnx 17-09-02
Raw Via lines 
2:463/0 @20261019.011554.0000 FIDOGATE/ftntoss
2:463/1331 @20261019.012000.0000 FIDOGATE/ftntoss
2:463/68 @20261019.012503.UTC hpt 1.3.0/lnx 17-09-02

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

Answered in 20m

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

Answered
MSGID
2:5001/100@fidonet 6ac2f681
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:04 UTC
Answered
2026-10-05 01:20 UTC by Ping Robot, 2:463/0

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→+5m2:463/68
#NodeStampedElapsedSoftware
1 ? – – lines:
2 2:5001/100 2026-10-05 00:59 UTC – FidoMail d6aaa2b3
3 2:5020/715 2026-10-05 01:04 UTC +4m RNtrack 2.3.0/Lnx/Perl
4 2:463/68 2026-10-05 01:10 UTC +5m hpt 1.3.0/lnx 17-09-02
Raw Via lines 
lines:
2:5001/100@fidonet @20261005.005942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.010425.UTC RNtrack 2.3.0/Lnx/Perl
2:463/68 @20261005.011007.UTC hpt 1.3.0/lnx 17-09-02

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:463/0→2:463/1331→2:463/68
#NodeStampedElapsedSoftware
1 2:463/0 2026-10-05 01:10 local – .0000 FIDOGATE/ftntoss
2 2:463/1331 2026-10-05 01:15 local – .0000 FIDOGATE/ftntoss
3 2:463/68 2026-10-05 01:20 UTC – hpt 1.3.0/lnx 17-09-02
Raw Via lines 
2:463/0 @20261005.011044.0000 FIDOGATE/ftntoss
2:463/1331 @20261005.011500.0000 FIDOGATE/ftntoss
2:463/68 @20261005.012006.UTC hpt 1.3.0/lnx 17-09-02

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

Answered in 34m

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

Answered
MSGID
2:5001/100@fidonet 6ab0809c
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:05 UTC
Answered
2026-09-21 01:30 UTC by Ping Robot, 2:463/0

Outbound path

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

?→2:5001/100→+9m2:5020/715→+14m2:463/68
#NodeStampedElapsedSoftware
1 ? – – lines:
2 2:5001/100 2026-09-21 00:55 UTC – FidoMail 97f43bf5
3 2:5020/715 2026-09-21 01:05 UTC +9m RNtrack 2.3.0/Lnx/Perl
4 2:463/68 2026-09-21 01:20 UTC +14m hpt 1.3.0/lnx 17-09-02
Raw Via lines 
lines:
2:5001/100@fidonet @20260921.005553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.010522.UTC RNtrack 2.3.0/Lnx/Perl
2:463/68 @20260921.012005.UTC hpt 1.3.0/lnx 17-09-02

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:463/0→2:463/1331→2:463/68
#NodeStampedElapsedSoftware
1 2:463/0 2026-09-21 01:20 local – .0000 FIDOGATE/ftntoss
2 2:463/1331 2026-09-21 01:25 local – .0000 FIDOGATE/ftntoss
3 2:463/68 2026-09-21 01:30 UTC – hpt 1.3.0/lnx 17-09-02
Raw Via lines 
2:463/0 @20260921.012007.0000 FIDOGATE/ftntoss
2:463/1331 @20260921.012500.0000 FIDOGATE/ftntoss
2:463/68 @20260921.013005.UTC hpt 1.3.0/lnx 17-09-02

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

Answered in 11m

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

Answered
MSGID
2:5001/100@fidonet 6a9e0a2f
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 00:49 UTC
Answered
2026-09-07 01:00 UTC by Ping Robot, 2:463/0

Outbound path

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

?→2:5020/715→+16s2:463/68
#NodeStampedElapsedSoftware
1 ? – – lines:
2 2:5020/715 2026-09-07 00:49 UTC – RNtrack 2.3.0/Lnx/Perl
3 2:463/68 2026-09-07 00:50 UTC +16s hpt 1.3.0/lnx 17-09-02
Raw Via lines 
lines:
2:5020/715 @20260907.004949.UTC RNtrack 2.3.0/Lnx/Perl
2:463/68 @20260907.005005.UTC hpt 1.3.0/lnx 17-09-02

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:463/0→2:463/1331→2:463/68
#NodeStampedElapsedSoftware
1 2:463/0 2026-09-07 00:50 local – .0000 FIDOGATE/ftntoss
2 2:463/1331 2026-09-07 00:55 local – .0000 FIDOGATE/ftntoss
3 2:463/68 2026-09-07 01:00 UTC – hpt 1.3.0/lnx 17-09-02
Raw Via lines 
2:463/0 @20260907.005052.0000 FIDOGATE/ftntoss
2:463/1331 @20260907.005500.0000 FIDOGATE/ftntoss
2:463/68 @20260907.010005.UTC hpt 1.3.0/lnx 17-09-02

Evidence

Replies

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

2026-10-19 01:25 UTC

pong Pong

From Ping Robot, 2:463/0 · answers 2:5001/100@fidonet 6ad56b81

Path quoted in this reply

?→2:5001/100→+7m2:5020/715→+7m2:463/68

This reply's own Via lines

  • 2:463/0 @20261019.011554.0000 FIDOGATE/ftntoss
  • 2:463/1331 @20261019.012000.0000 FIDOGATE/ftntoss
  • 2:463/68 @20261019.012503.UTC hpt 1.3.0/lnx 17-09-02

2026-10-05 01:20 UTC

pong Pong

From Ping Robot, 2:463/0 · answers 2:5001/100@fidonet 6ac2f681

Path quoted in this reply

?→2:5001/100→+4m2:5020/715→+5m2:463/68

This reply's own Via lines

  • 2:463/0 @20261005.011044.0000 FIDOGATE/ftntoss
  • 2:463/1331 @20261005.011500.0000 FIDOGATE/ftntoss
  • 2:463/68 @20261005.012006.UTC hpt 1.3.0/lnx 17-09-02

2026-09-21 01:30 UTC

pong Pong

From Ping Robot, 2:463/0 · answers 2:5001/100@fidonet 6ab0809c

Path quoted in this reply

?→2:5001/100→+9m2:5020/715→+14m2:463/68

This reply's own Via lines

  • 2:463/0 @20260921.012007.0000 FIDOGATE/ftntoss
  • 2:463/1331 @20260921.012500.0000 FIDOGATE/ftntoss
  • 2:463/68 @20260921.013005.UTC hpt 1.3.0/lnx 17-09-02

2026-09-07 01:00 UTC

pong Pong

From Ping Robot, 2:463/0 · answers 2:5001/100@fidonet 6a9e0a2f

Path quoted in this reply

?→2:5020/715→+16s2:463/68

This reply's own Via lines

  • 2:463/0 @20260907.005052.0000 FIDOGATE/ftntoss
  • 2:463/1331 @20260907.005500.0000 FIDOGATE/ftntoss
  • 2:463/68 @20260907.010005.UTC hpt 1.3.0/lnx 17-09-02