NodelistDB

Netmail PING — 2:5020/2065

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

← All PING/TRACE nodes Node history for 2:5020/2065

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

Answered in 44m

The robot at 2:5020/2065 bounced it back 44m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad57031
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:19 UTC
Answered
2026-10-19 02:04 UTC by FTrack, 2:5020/2065

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→2:5020/12000→+40m2:5020/2065→-40m2:5001/100→+2s2:5020/715→2:5020/12000→+40m2:5020/2065
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:19 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:19 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5020/12000 – – PyFTN Mon Oct 19 05:00:01 2026
4 2:5020/2065 2026-10-19 02:00 UTC +40m FTrack 3.1/W32
5 2:5001/100 2026-10-19 01:19 UTC -40m FidoMail 65fd0ae9
6 2:5020/715 2026-10-19 01:19 UTC +2s RNtrack 2.3.0/Lnx/Perl
7 2:5020/12000 – – PyFTN Mon Oct 19 05:00:01 2026
8 2:5020/2065 2026-10-19 02:00 UTC +40m FTrack 3.1/W32
Raw Via lines 
2:5001/100@fidonet @20261019.011942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.011944.UTC RNtrack 2.3.0/Lnx/Perl
PyFTN 2:5020/12000 Mon Oct 19 05:00:01 2026
2:5020/2065 @20261019.020005.UTC FTrack 3.1/W32
2:5001/100@fidonet @20261019.011942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.011944.UTC RNtrack 2.3.0/Lnx/Perl
PyFTN 2:5020/12000 Mon Oct 19 05:00:01 2026
2:5020/2065 @20261019.020005.UTC FTrack 3.1/W32

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:5020/2065→2:5020/12000→+3m2:5020/715
#NodeStampedElapsedSoftware
1 2:5020/2065 2026-10-19 02:00 UTC – FTrack 3.1/W32
2 2:5020/12000 – – PyFTN Mon Oct 19 05:03:55 2026
3 2:5020/715 2026-10-19 02:03 UTC +3m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5020/2065 @20261019.020005.UTC FTrack 3.1/W32
PyFTN 2:5020/12000 Mon Oct 19 05:03:55 2026
2:5020/715 @20261019.020359.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 52m

The robot at 2:5020/2065 bounced it back 52m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2fb2f
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:19 UTC
Answered
2026-10-05 02:12 UTC by FTrack, 2:5020/2065

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→2:5020/12000→+40m2:5020/2065→-40m2:5001/100→+2s2:5020/715→2:5020/12000→+40m2:5020/2065
#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:5020/12000 – – PyFTN Mon Oct 5 05:00:03 2026
4 2:5020/2065 2026-10-05 02:00 UTC +40m FTrack 3.1/W32
5 2:5001/100 2026-10-05 01:19 UTC -40m FidoMail d6aaa2b3
6 2:5020/715 2026-10-05 01:19 UTC +2s RNtrack 2.3.0/Lnx/Perl
7 2:5020/12000 – – PyFTN Mon Oct 5 05:00:03 2026
8 2:5020/2065 2026-10-05 02:00 UTC +40m FTrack 3.1/W32
Raw Via lines 
2:5001/100@fidonet @20261005.011942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.011944.UTC RNtrack 2.3.0/Lnx/Perl
PyFTN 2:5020/12000 Mon Oct  5 05:00:03 2026
2:5020/2065 @20261005.020007.UTC FTrack 3.1/W32
2:5001/100@fidonet @20261005.011942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.011944.UTC RNtrack 2.3.0/Lnx/Perl
PyFTN 2:5020/12000 Mon Oct  5 05:00:03 2026
2:5020/2065 @20261005.020007.UTC FTrack 3.1/W32

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:5020/2065→2:5020/12000→+12m2:5020/715
#NodeStampedElapsedSoftware
1 2:5020/2065 2026-10-05 02:00 UTC – FTrack 3.1/W32
2 2:5020/12000 – – PyFTN Mon Oct 5 05:12:08 2026
3 2:5020/715 2026-10-05 02:12 UTC +12m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5020/2065 @20261005.020007.UTC FTrack 3.1/W32
PyFTN 2:5020/12000 Mon Oct  5 05:12:08 2026
2:5020/715 @20261005.021213.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 51m

The robot at 2:5020/2065 bounced it back 51m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab0854a
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:15 UTC
Answered
2026-09-21 02:07 UTC by FTrack, 2:5020/2065

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→2:5020/12000→+44m2:5020/2065→-44m2:5001/100→+2s2:5020/715→2:5020/12000→+44m2:5020/2065
#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:5020/12000 – – PyFTN Mon Sep 21 05:00:03 2026
4 2:5020/2065 2026-09-21 02:00 UTC +44m FTrack 3.1/W32
5 2:5001/100 2026-09-21 01:15 UTC -44m FidoMail 97f43bf5
6 2:5020/715 2026-09-21 01:15 UTC +2s RNtrack 2.3.0/Lnx/Perl
7 2:5020/12000 – – PyFTN Mon Sep 21 05:00:03 2026
8 2:5020/2065 2026-09-21 02:00 UTC +44m FTrack 3.1/W32
Raw Via lines 
2:5001/100@fidonet @20260921.011553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.011555.UTC RNtrack 2.3.0/Lnx/Perl
PyFTN 2:5020/12000 Mon Sep 21 05:00:03 2026
2:5020/2065 @20260921.020004.UTC FTrack 3.1/W32
2:5001/100@fidonet @20260921.011553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.011555.UTC RNtrack 2.3.0/Lnx/Perl
PyFTN 2:5020/12000 Mon Sep 21 05:00:03 2026
2:5020/2065 @20260921.020004.UTC FTrack 3.1/W32

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:5020/2065→2:5020/12000→+7m2:5020/715
#NodeStampedElapsedSoftware
1 2:5020/2065 2026-09-21 02:00 UTC – FTrack 3.1/W32
2 2:5020/12000 – – PyFTN Mon Sep 21 05:07:22 2026
3 2:5020/715 2026-09-21 02:07 UTC +7m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5020/2065 @20260921.020004.UTC FTrack 3.1/W32
PyFTN 2:5020/12000 Mon Sep 21 05:07:22 2026
2:5020/715 @20260921.020727.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 1h 8m

The robot at 2:5020/2065 bounced it back 1h 8m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e0d98
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:11 UTC
Answered
2026-09-07 02:12 UTC by FTrack, 2:5020/2065

Outbound path

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

2:5020/715→2:5020/12000→+47m2:5020/2065→-47m2:5020/715→2:5020/12000→+47m2:5020/2065
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:12 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5020/12000 – – PyFTN Mon Sep 7 05:00:01 2026
3 2:5020/2065 2026-09-07 02:00 UTC +47m FTrack 3.1/W32
4 2:5020/715 2026-09-07 01:12 UTC -47m RNtrack 2.3.0/Lnx/Perl
5 2:5020/12000 – – PyFTN Mon Sep 7 05:00:01 2026
6 2:5020/2065 2026-09-07 02:00 UTC +47m FTrack 3.1/W32
Raw Via lines 
2:5020/715 @20260907.011228.UTC RNtrack 2.3.0/Lnx/Perl
PyFTN 2:5020/12000 Mon Sep  7 05:00:01 2026
2:5020/2065 @20260907.020003.UTC FTrack 3.1/W32
2:5020/715 @20260907.011228.UTC RNtrack 2.3.0/Lnx/Perl
PyFTN 2:5020/12000 Mon Sep  7 05:00:01 2026
2:5020/2065 @20260907.020003.UTC FTrack 3.1/W32

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:5020/2065→2:5020/12000→+12m2:5020/715
#NodeStampedElapsedSoftware
1 2:5020/2065 2026-09-07 02:00 UTC – FTrack 3.1/W32
2 2:5020/12000 – – PyFTN Mon Sep 7 05:12:43 2026
3 2:5020/715 2026-09-07 02:12 UTC +12m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5020/2065 @20260907.020003.UTC FTrack 3.1/W32
PyFTN 2:5020/12000 Mon Sep  7 05:12:43 2026
2:5020/715 @20260907.021248.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-10-19 02:04 UTC

pong PONG

From FTrack, 2:5020/2065 · answers 2:5001/100@fidonet 6ad57031

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:5020/12000→+40m2:5020/2065→-40m2:5001/100→+2s2:5020/715→2:5020/12000→+40m2:5020/2065

This reply's own Via lines

  • 2:5020/2065 @20261019.020005.UTC FTrack 3.1/W32
  • PyFTN 2:5020/12000 Mon Oct 19 05:03:55 2026
  • 2:5020/715 @20261019.020359.UTC RNtrack 2.3.0/Lnx/Perl

2026-10-05 02:12 UTC

pong PONG

From FTrack, 2:5020/2065 · answers 2:5001/100@fidonet 6ac2fb2f

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:5020/12000→+40m2:5020/2065→-40m2:5001/100→+2s2:5020/715→2:5020/12000→+40m2:5020/2065

This reply's own Via lines

  • 2:5020/2065 @20261005.020007.UTC FTrack 3.1/W32
  • PyFTN 2:5020/12000 Mon Oct 5 05:12:08 2026
  • 2:5020/715 @20261005.021213.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-21 02:07 UTC

pong PONG

From FTrack, 2:5020/2065 · answers 2:5001/100@fidonet 6ab0854a

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:5020/12000→+44m2:5020/2065→-44m2:5001/100→+2s2:5020/715→2:5020/12000→+44m2:5020/2065

This reply's own Via lines

  • 2:5020/2065 @20260921.020004.UTC FTrack 3.1/W32
  • PyFTN 2:5020/12000 Mon Sep 21 05:07:22 2026
  • 2:5020/715 @20260921.020727.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-07 02:12 UTC

pong PONG

From FTrack, 2:5020/2065 · answers 2:5001/100@fidonet 6a9e0d98

Path quoted in this reply

2:5020/715→2:5020/12000→+47m2:5020/2065→-47m2:5020/715→2:5020/12000→+47m2:5020/2065

This reply's own Via lines

  • 2:5020/2065 @20260907.020003.UTC FTrack 3.1/W32
  • PyFTN 2:5020/12000 Mon Sep 7 05:12:43 2026
  • 2:5020/715 @20260907.021248.UTC RNtrack 2.3.0/Lnx/Perl