NodelistDB

Netmail PING — 2:5030/553

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

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

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

Answered in 13h 46m

The robot at 2:5030/553 bounced it back 13h 46m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad57287
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:29 UTC
Answered
2026-10-19 15:15 UTC by Ping Robot, 2:5030/553

Outbound path

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

2:5001/100→+2s2:5020/715→+1m2:5030/731→2:5030/1957
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:29 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:29 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5030/731 2026-10-19 01:31 UTC +1m RNtrack 2.2.2/W64
4 2:5030/1957 – – RNtrack 2.1.10/FBSD 19 Oct 2026 04:36:00 UTC+0300
Raw Via lines 
2:5001/100@fidonet @20261019.012942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.012944.UTC RNtrack 2.3.0/Lnx/Perl
2:5030/731 @20261019.013119.UTC RNtrack 2.2.2/W64
2:5030/1957 RNtrack 2.1.10/FBSD 19 Oct 2026 04:36:00 UTC+0300

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/553→2:5030/1957→+14m2:5030/1115→+38s2:5020/715
#NodeStampedElapsedSoftware
1 2:5030/553 2026-10-19 15:00 UTC – hpt/w32-mvcdll 1.9.0-cur 06-03-10
2 2:5030/1957 – – RNtrack 2.1.10/FBSD 19 Oct 2026 18:12:00 UTC+0300
3 2:5030/1115 2026-10-19 15:15 UTC +14m FTrack 3.02/FBSD
4 2:5020/715 2026-10-19 15:15 UTC +38s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5030/553 @20261019.150006.UTC hpt/w32-mvcdll 1.9.0-cur 06-03-10
2:5030/1957 RNtrack 2.1.10/FBSD 19 Oct 2026 18:12:00 UTC+0300
2:5030/1115 @20261019.151502.UTC FTrack 3.02/FBSD
2:5020/715 @20261019.151540.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 13h 56m

The robot at 2:5030/553 bounced it back 13h 56m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2fb32
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:19 UTC
Answered
2026-10-05 15:15 UTC by Ping Robot, 2:5030/553

Outbound path

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

2:5001/100→+2s2:5020/715→-13s2:5030/731→2:5030/1957
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:19 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:19 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5030/731 2026-10-05 01:19 UTC -13s RNtrack 2.2.2/W64
4 2:5030/1957 – – RNtrack 2.1.10/FBSD 05 Oct 2026 04:24:00 UTC+0300
Raw Via lines 
2:5001/100@fidonet @20261005.011942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.011944.UTC RNtrack 2.3.0/Lnx/Perl
2:5030/731 @20261005.011931.UTC RNtrack 2.2.2/W64
2:5030/1957 RNtrack 2.1.10/FBSD 05 Oct 2026 04:24:00 UTC+0300

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/553→2:5030/1957→+14m2:5030/1115→+46s2:5020/715
#NodeStampedElapsedSoftware
1 2:5030/553 2026-10-05 15:00 UTC – hpt/w32-mvcdll 1.9.0-cur 06-03-10
2 2:5030/1957 – – RNtrack 2.1.10/FBSD 05 Oct 2026 18:12:00 UTC+0300
3 2:5030/1115 2026-10-05 15:15 UTC +14m FTrack 3.02/FBSD
4 2:5020/715 2026-10-05 15:15 UTC +46s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5030/553 @20261005.150019.UTC hpt/w32-mvcdll 1.9.0-cur 06-03-10
2:5030/1957 RNtrack 2.1.10/FBSD 05 Oct 2026 18:12:00 UTC+0300
2:5030/1115 @20261005.151502.UTC FTrack 3.02/FBSD
2:5020/715 @20261005.151548.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 13h 59m

The robot at 2:5030/553 bounced it back 13h 59m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab0854d
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:15 UTC
Answered
2026-09-21 15:15 UTC by Ping Robot, 2:5030/553

Outbound path

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

2:5001/100→+2s2:5020/715→+6m2:5030/731→2:5030/1957
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:15 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:15 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5030/731 2026-09-21 01:22 UTC +6m RNtrack 2.2.2/W64
4 2:5030/1957 – – RNtrack 2.1.10/FBSD 21 Sep 2026 04:24:00 UTC+0300
Raw Via lines 
2:5001/100@fidonet @20260921.011553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.011555.UTC RNtrack 2.3.0/Lnx/Perl
2:5030/731 @20260921.012216.UTC RNtrack 2.2.2/W64
2:5030/1957 RNtrack 2.1.10/FBSD 21 Sep 2026 04:24:00 UTC+0300

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/553→2:5030/1957→+14m2:5030/1115→+7s2:5020/715
#NodeStampedElapsedSoftware
1 2:5030/553 2026-09-21 15:00 UTC – hpt/w32-mvcdll 1.9.0-cur 06-03-10
2 2:5030/1957 – – RNtrack 2.1.10/FBSD 21 Sep 2026 18:12:00 UTC+0300
3 2:5030/1115 2026-09-21 15:15 UTC +14m FTrack 3.02/FBSD
4 2:5020/715 2026-09-21 15:15 UTC +7s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5030/553 @20260921.150016.UTC hpt/w32-mvcdll 1.9.0-cur 06-03-10
2:5030/1957 RNtrack 2.1.10/FBSD 21 Sep 2026 18:12:00 UTC+0300
2:5030/1115 @20260921.151502.UTC FTrack 3.02/FBSD
2:5020/715 @20260921.151509.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 14h 11m

The robot at 2:5030/553 bounced it back 14h 11m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0d9b
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:11 UTC
Answered
2026-09-07 15:15 UTC by Ping Robot, 2:5030/553

Outbound path

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

2:5020/715→+6s2:5030/731→2:5030/1957
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:11 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5030/731 2026-09-07 01:12 UTC +6s RNtrack 2.2.2/W64
3 2:5030/1957 – – RNtrack 2.1.10/FBSD 07 Sep 2026 04:24:00 UTC+0300
Raw Via lines 
2:5020/715 @20260907.011159.UTC RNtrack 2.3.0/Lnx/Perl
2:5030/731 @20260907.011205.UTC RNtrack 2.2.2/W64
2:5030/1957 RNtrack 2.1.10/FBSD 07 Sep 2026 04:24:00 UTC+0300

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/553→2:5030/1957→+14m2:5030/1115→+53s2:5020/715
#NodeStampedElapsedSoftware
1 2:5030/553 2026-09-07 15:00 UTC – hpt/w32-mvcdll 1.9.0-cur 06-03-10
2 2:5030/1957 – – RNtrack 2.1.10/FBSD 07 Sep 2026 18:12:00 UTC+0300
3 2:5030/1115 2026-09-07 15:15 UTC +14m FTrack 3.02/FBSD
4 2:5020/715 2026-09-07 15:15 UTC +53s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5030/553 @20260907.150019.UTC hpt/w32-mvcdll 1.9.0-cur 06-03-10
2:5030/1957 RNtrack 2.1.10/FBSD 07 Sep 2026 18:12:00 UTC+0300
2:5030/1115 @20260907.151501.UTC FTrack 3.02/FBSD
2:5020/715 @20260907.151554.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-10-19 15:15 UTC

pong Pong

From Ping Robot, 2:5030/553 · answers 2:5001/100@fidonet 6ad57287

Path quoted in this reply

2:5001/100→+2s2:5020/715→+1m2:5030/731→2:5030/1957

This reply's own Via lines

  • 2:5030/553 @20261019.150006.UTC hpt/w32-mvcdll 1.9.0-cur 06-03-10
  • 2:5030/1957 RNtrack 2.1.10/FBSD 19 Oct 2026 18:12:00 UTC+0300
  • 2:5030/1115 @20261019.151502.UTC FTrack 3.02/FBSD
  • 2:5020/715 @20261019.151540.UTC RNtrack 2.3.0/Lnx/Perl

2026-10-05 15:15 UTC

pong Pong

From Ping Robot, 2:5030/553 · answers 2:5001/100@fidonet 6ac2fb32

Path quoted in this reply

2:5001/100→+2s2:5020/715→-13s2:5030/731→2:5030/1957

This reply's own Via lines

  • 2:5030/553 @20261005.150019.UTC hpt/w32-mvcdll 1.9.0-cur 06-03-10
  • 2:5030/1957 RNtrack 2.1.10/FBSD 05 Oct 2026 18:12:00 UTC+0300
  • 2:5030/1115 @20261005.151502.UTC FTrack 3.02/FBSD
  • 2:5020/715 @20261005.151548.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-21 15:15 UTC

pong Pong

From Ping Robot, 2:5030/553 · answers 2:5001/100@fidonet 6ab0854d

Path quoted in this reply

2:5001/100→+2s2:5020/715→+6m2:5030/731→2:5030/1957

This reply's own Via lines

  • 2:5030/553 @20260921.150016.UTC hpt/w32-mvcdll 1.9.0-cur 06-03-10
  • 2:5030/1957 RNtrack 2.1.10/FBSD 21 Sep 2026 18:12:00 UTC+0300
  • 2:5030/1115 @20260921.151502.UTC FTrack 3.02/FBSD
  • 2:5020/715 @20260921.151509.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-07 15:15 UTC

pong Pong

From Ping Robot, 2:5030/553 · answers 2:5001/100@fidonet 6a9e0d9b

Path quoted in this reply

2:5020/715→+6s2:5030/731→2:5030/1957

This reply's own Via lines

  • 2:5030/553 @20260907.150019.UTC hpt/w32-mvcdll 1.9.0-cur 06-03-10
  • 2:5030/1957 RNtrack 2.1.10/FBSD 07 Sep 2026 18:12:00 UTC+0300
  • 2:5030/1115 @20260907.151501.UTC FTrack 3.02/FBSD
  • 2:5020/715 @20260907.151554.UTC RNtrack 2.3.0/Lnx/Perl