NodelistDB

Netmail PING — 2:5030/731

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

← All PING/TRACE nodes Node history for 2:5030/731

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

Answered in 2m

The robot at 2:5030/731 bounced it back 2m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad57288
First hop
2:5030/731@fidonet (rule)
Answered
2026-10-19 01:32 UTC by PING@s0t, 2:5030/731

Outbound path

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

2:5001/100
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:29 UTC – FidoMail 65fd0ae9
Raw Via lines 
2:5001/100@fidonet @20261019.012942.UTC FidoMail 65fd0ae9

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:5030/731
#NodeStampedElapsedSoftware
1 2:5030/731 2026-10-19 01:31 UTC – RNtrack 2.2.2/W64
Raw Via lines 
2:5030/731 @20261019.013122.UTC RNtrack 2.2.2/W64

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

Answered in 2m

The robot at 2:5030/731 bounced it back 2m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2fd86
First hop
2:5030/731@fidonet (rule)
Answered
2026-10-05 01:32 UTC by PING@s0t, 2:5030/731

Outbound path

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

2:5001/100
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:29 UTC – FidoMail d6aaa2b3
Raw Via lines 
2:5001/100@fidonet @20261005.012942.UTC FidoMail d6aaa2b3

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:5030/731
#NodeStampedElapsedSoftware
1 2:5030/731 2026-10-05 01:31 UTC – RNtrack 2.2.2/W64
Raw Via lines 
2:5030/731 @20261005.013124.UTC RNtrack 2.2.2/W64

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

Answered in 53s

The robot at 2:5030/731 bounced it back 53s after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab087a1
First hop
2:5030/731@fidonet (rule)
Answered
2026-09-21 01:26 UTC by PING@s0t, 2:5030/731

Outbound path

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

2:5001/100
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:25 UTC – FidoMail 97f43bf5
Raw Via lines 
2:5001/100@fidonet @20260921.012553.UTC FidoMail 97f43bf5

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:5030/731
#NodeStampedElapsedSoftware
1 2:5030/731 2026-09-21 01:25 UTC – RNtrack 2.2.2/W64
Raw Via lines 
2:5030/731 @20260921.012549.UTC RNtrack 2.2.2/W64

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

Answered in 3m

The robot at 2:5030/731 bounced it back 3m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0ff0
First hop
2:5030/731@fidonet (rule)
Handed over
2026-09-07 01:14 UTC
Answered
2026-09-07 01:17 UTC by PING@s0t, 2:5030/731

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:5030/731
#NodeStampedElapsedSoftware
1 2:5030/731 2026-09-07 01:16 UTC – RNtrack 2.2.2/W64
Raw Via lines 
2:5030/731 @20260907.011637.UTC RNtrack 2.2.2/W64

Evidence

Replies

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

2026-10-19 01:32 UTC

pong PONG

From PING@s0t, 2:5030/731 · answers 2:5001/100@fidonet 6ad57288

Path quoted in this reply

2:5001/100

This reply's own Via lines

  • 2:5030/731 @20261019.013122.UTC RNtrack 2.2.2/W64

2026-10-05 01:32 UTC

pong PONG

From PING@s0t, 2:5030/731 · answers 2:5001/100@fidonet 6ac2fd86

Path quoted in this reply

2:5001/100

This reply's own Via lines

  • 2:5030/731 @20261005.013124.UTC RNtrack 2.2.2/W64

2026-09-21 01:26 UTC

pong PONG

From PING@s0t, 2:5030/731 · answers 2:5001/100@fidonet 6ab087a1

Path quoted in this reply

2:5001/100

This reply's own Via lines

  • 2:5030/731 @20260921.012549.UTC RNtrack 2.2.2/W64