NodelistDB

Netmail PING — 2:423/39

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

← All PING/TRACE nodes Node history for 2:423/39

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

Answered in 23m

The robot at 2:423/39 bounced it back 23m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2f429
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:04 UTC
Answered
2026-10-05 01:12 UTC by Robot, 2:423/39

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:423/39→2:423/81
#NodeStampedElapsedSoftware
1 2:423/39 2026-10-05 03:11 local – CrashMail II/Linux 1.5.1
2 2:423/81 2026-10-05 01:12 UTC – T-Mail 2608.OS2 0428
Raw Via lines 
2:423/39 @20261005.031101 CrashMail II/Linux 1.5.1
2:423/81@fidonet.org @20261005.031221.UTC+2 T-Mail 2608.OS2 0428

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

Answered in 5m

The robot at 2:423/39 bounced it back 5m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab07e44
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-21 00:51 UTC by Robot, 2:423/39

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:423/39→2:423/81
#NodeStampedElapsedSoftware
1 2:423/39 2026-09-21 02:50 local – CrashMail II/Linux 1.5.1
2 2:423/81 2026-09-21 00:51 UTC – T-Mail 2608.OS2 0428
Raw Via lines 
2:423/39 @20260921.025001 CrashMail II/Linux 1.5.1
2:423/81@fidonet.org @20260921.025139.UTC+2 T-Mail 2608.OS2 0428

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

Answered in 7m

The robot at 2:423/39 bounced it back 7m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e07d8
First hop
2:5020/715@fidonet (rule)
Answered
2026-09-07 00:46 UTC by Robot, 2:423/39

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:423/39→2:423/81
#NodeStampedElapsedSoftware
1 2:423/39 2026-09-07 02:45 local – CrashMail II/Linux 1.5.1
2 2:423/81 2026-09-07 00:46 UTC – T-Mail 2608.OS2 0428
Raw Via lines 
2:423/39 @20260907.024501 CrashMail II/Linux 1.5.1
2:423/81@fidonet.org @20260907.024632.UTC+2 T-Mail 2608.OS2 0428

Evidence

Replies

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

2026-10-05 01:12 UTC

pong unsecure Pong

From Robot, 2:423/39 · answers 2:5001/100@fidonet 6ac2f429

This reply's own Via lines

  • 2:423/39 @20261005.031101 CrashMail II/Linux 1.5.1
  • 2:423/81@fidonet.org @20261005.031221.UTC+2 T-Mail 2608.OS2 0428

2026-09-21 00:51 UTC

pong unsecure Pong

From Robot, 2:423/39 · answers 2:5001/100@fidonet 6ab07e44

This reply's own Via lines

  • 2:423/39 @20260921.025001 CrashMail II/Linux 1.5.1
  • 2:423/81@fidonet.org @20260921.025139.UTC+2 T-Mail 2608.OS2 0428

2026-09-07 00:46 UTC

pong unsecure Pong

From Robot, 2:423/39 · answers 2:5001/100@fidonet 6a9e07d8

This reply's own Via lines

  • 2:423/39 @20260907.024501 CrashMail II/Linux 1.5.1
  • 2:423/81@fidonet.org @20260907.024632.UTC+2 T-Mail 2608.OS2 0428