NodelistDB

Netmail PING — 3:633/280

Every FTS-4010 PING sent to 3:633/280 (fidonet), with the path each one walked.

← All PING/TRACE nodes Node history for 3:633/280

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

Answered in 36m

The robot at 3:633/280 bounced it back 36m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e130c
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:27 UTC
Answered
2026-09-07 02:04 UTC by Ping Robot, 3:633/280
Transit notices
2

Outbound path

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

2:5020/715→+1s2:5080/102→+4m3:712/848→+1s3:712/848
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:27 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5080/102 2026-09-07 01:27 UTC +1s hpt/lnx 1.4.0-sta 27-11-08
3 3:712/848 2026-09-07 01:32 UTC +4m RNtrack 1.21/W32
4 3:712/848 2026-09-07 01:32 UTC +1s hpt/w32-mvcdll 1.9.0-cur 04-11-15
Raw Via lines 
2:5020/715 @20260907.012741.UTC RNtrack 2.3.0/Lnx/Perl
2:5080/102 @20260907.012742.UTC hpt/lnx 1.4.0-sta 27-11-08
3:712/848 @20260907.013200.UTC RNtrack 1.21/W32
3:712/848 @20260907.013201.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15

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.

3:633/280→+5m2:280/464→2:280/464→+9m2:280/5003.0→+20s2:5020/715
#NodeStampedElapsedSoftware
1 3:633/280 2026-09-07 01:48 UTC – hpt/lnx 1.9 2024-03-02
2 2:280/464 2026-09-07 01:54 UTC +5m FMail-lnx64(Toss) 2.3.4.1-B20260520
3 2:280/464 2026-09-07 01:54 UTC – FMail-lnx64(Pack) 2.3.4.1-B20260520
4 2:280/5003.0 2026-09-07 02:04 UTC +9m FIDOGATE/ftntoss 4.4.14
5 2:5020/715 2026-09-07 02:04 UTC +20s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
3:633/280 @20260907.014814.UTC hpt/lnx 1.9 2024-03-02
2:280/464 @20260907.015403.282.UTC FMail-lnx64(Toss) 2.3.4.1-B20260520
2:280/464 @20260907.015403.291.UTC FMail-lnx64(Pack) 2.3.4.1-B20260520
2:280/5003.0 @20260907.020402.UTC FIDOGATE/ftntoss 4.4.14
2:5020/715 @20260907.020422.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-09-07 02:04 UTC

pong PONG: PING

From Ping Robot, 3:633/280 · answers 2:5001/100@fidonet 6a9e130c

Path quoted in this reply

2:5020/715→+1s2:5080/102→+4m3:712/848→+1s3:712/848

This reply's own Via lines

  • 3:633/280 @20260907.014814.UTC hpt/lnx 1.9 2024-03-02
  • 2:280/464 @20260907.015403.282.UTC FMail-lnx64(Toss) 2.3.4.1-B20260520
  • 2:280/464 @20260907.015403.291.UTC FMail-lnx64(Pack) 2.3.4.1-B20260520
  • 2:280/5003.0 @20260907.020402.UTC FIDOGATE/ftntoss 4.4.14
  • 2:5020/715 @20260907.020422.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-07 01:34 UTC

trace PONG: PING

From Ping-Pong Robot, 2:5080/102 · answers 2:5001/100@fidonet 6a9e130c

Path quoted in this reply

2:5020/715

This reply's own Via lines

  • 2:5080/102 @20260907.012742.UTC hpt/lnx 1.4.0-sta 27-11-08

Software

hpt/lnx 1.4.0-sta 27-11-08   --- pong.pl,v 1.6 2010/02/01 23:47:21

2026-09-07 01:34 UTC

trace ping/traceroute report

From mailer-daemon, 3:712/848 · answers 2:5001/100@fidonet 6a9e130c

Path quoted in this reply

2:5020/715→+1s2:5080/102

This reply's own Via lines

  • 3:712/848 @20260907.013200.UTC RNtrack 1.21/W32
  • 3:712/848 @20260907.013201.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
  • 2:280/5003.0 @20260907.013401.UTC FIDOGATE/ftntoss 4.4.14
  • 2:5020/715 @20260907.013424.UTC RNtrack 2.3.0/Lnx/Perl