NodelistDB

Netmail PING — 2:5058/0

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

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

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

Answered in 15s

The robot at 2:5058/0 bounced it back 15s after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad5728a
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-19 01:29 UTC by Ping Robot, 2:5058/0

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
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:29 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:29 UTC +1s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5001/100@fidonet @20261019.012943.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.012944.UTC RNtrack 2.3.0/Lnx/Perl

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:5058/104→+3s2:5020/715
#NodeStampedElapsedSoftware
1 2:5058/104 2026-10-19 01:29 UTC – hpt/lnx 1.9 2023-02-18
2 2:5020/715 2026-10-19 01:29 UTC +3s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5058/104 @20261019.012949.UTC hpt/lnx 1.9 2023-02-18
2:5020/715 @20261019.012952.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 13s

The robot at 2:5058/0 bounced it back 13s after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2fd88
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-05 01:29 UTC by Ping Robot, 2:5058/0

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
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:29 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:29 UTC +3s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5001/100@fidonet @20261005.012942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.012945.UTC RNtrack 2.3.0/Lnx/Perl

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:5058/104→+2s2:5020/715
#NodeStampedElapsedSoftware
1 2:5058/104 2026-10-05 01:29 UTC – hpt/lnx 1.9 2023-02-18
2 2:5020/715 2026-10-05 01:29 UTC +2s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5058/104 @20261005.012952.UTC hpt/lnx 1.9 2023-02-18
2:5020/715 @20261005.012954.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 30s

The robot at 2:5058/0 bounced it back 30s after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab087a3
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 01:26 UTC by Ping Robot, 2:5058/0

Outbound path

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

2:5001/100→+5s2:5020/715
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:25 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:25 UTC +5s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5001/100@fidonet @20260921.012553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.012558.UTC RNtrack 2.3.0/Lnx/Perl

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:5058/104→+2s2:5020/715
#NodeStampedElapsedSoftware
1 2:5058/104 2026-09-21 01:26 UTC – hpt/lnx 1.9 2023-02-18
2 2:5020/715 2026-09-21 01:26 UTC +2s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5058/104 @20260921.012619.UTC hpt/lnx 1.9 2023-02-18
2:5020/715 @20260921.012621.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 30s

The robot at 2:5058/0 bounced it back 30s after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0ff2
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 01:14 UTC by Ping Robot, 2:5058/0

Outbound path

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

2:5020/715
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:14 UTC – RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5020/715 @20260907.011426.UTC RNtrack 2.3.0/Lnx/Perl

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:5058/104→+10s2:5020/715
#NodeStampedElapsedSoftware
1 2:5058/104 2026-09-07 01:14 UTC – hpt/lnx 1.9 2023-02-18
2 2:5020/715 2026-09-07 01:14 UTC +10s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5058/104 @20260907.011443.UTC hpt/lnx 1.9 2023-02-18
2:5020/715 @20260907.011453.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-10-19 01:29 UTC

pong Pong

From Ping Robot, 2:5058/0 · answers 2:5001/100@fidonet 6ad5728a

Path quoted in this reply

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

This reply's own Via lines

  • 2:5058/104 @20261019.012949.UTC hpt/lnx 1.9 2023-02-18
  • 2:5020/715 @20261019.012952.UTC RNtrack 2.3.0/Lnx/Perl

2026-10-05 01:29 UTC

pong Pong

From Ping Robot, 2:5058/0 · answers 2:5001/100@fidonet 6ac2fd88

Path quoted in this reply

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

This reply's own Via lines

  • 2:5058/104 @20261005.012952.UTC hpt/lnx 1.9 2023-02-18
  • 2:5020/715 @20261005.012954.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-21 01:26 UTC

pong Pong

From Ping Robot, 2:5058/0 · answers 2:5001/100@fidonet 6ab087a3

Path quoted in this reply

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

This reply's own Via lines

  • 2:5058/104 @20260921.012619.UTC hpt/lnx 1.9 2023-02-18
  • 2:5020/715 @20260921.012621.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-07 01:14 UTC

pong Pong

From Ping Robot, 2:5058/0 · answers 2:5001/100@fidonet 6a9e0ff2

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:5058/104 @20260907.011443.UTC hpt/lnx 1.9 2023-02-18
  • 2:5020/715 @20260907.011453.UTC RNtrack 2.3.0/Lnx/Perl