NodelistDB

Netmail PING — 2:280/2060

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

← All PING/TRACE nodes Node history for 2:280/2060

Routed ping · 2026-10-19 00:09 UTC

Answered in 7m

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

Answered
MSGID
2:5001/100@fidonet 6ad55fc8
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-19 00:17 UTC by AroundMyRooms Ping Robot, 2:280/2060

Outbound path

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

2:5001/100→+1s2:5020/715→2:292/854→+1h 4m2:292/854→-58m2:280/5003.0
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 00:09 UTC – FidoMail v0.1.5
2 2:5020/715 2026-10-19 00:09 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 02:11 local – D'Bridge 4
4 2:292/854 2026-10-19 01:14 UTC +1h 4m O/T-Track+ 2.85
5 2:280/5003.0 2026-10-19 00:15 UTC -58m FIDOGATE/ftntoss 4.4.14
Raw Via lines 
2:5001/100@fidonet @20261019.000942.UTC FidoMail v0.1.5
2:5020/715 @20261019.000943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.021112 D'Bridge 4
2:292/854@Ward_Dossche @20261019.011400.UTC O/T-Track+ 2.85
2:280/5003.0 @20261019.001502.UTC FIDOGATE/ftntoss 4.4.14

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:280/2060
#NodeStampedElapsedSoftware
1 2:280/2060 2026-10-19 00:17 UTC – hpt/lnx 1.9.0-cur 2020-04-15
Raw Via lines 
2:280/2060 @20261019.001701.UTC hpt/lnx 1.9.0-cur 2020-04-15

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

Answered in 16m

The robot at 2:280/2060 bounced it back 16m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2eac8
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 00:09 UTC
Answered
2026-10-05 00:26 UTC by AroundMyRooms Ping Robot, 2:280/2060

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:292/854→+1h 4m2:292/854→-49m2:280/5003.0
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 00:09 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 00:09 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 02:11 local – D'Bridge 4
4 2:292/854 2026-10-05 01:13 UTC +1h 4m O/T-Track+ 2.85
5 2:280/5003.0 2026-10-05 00:24 UTC -49m FIDOGATE/ftntoss 4.4.14
Raw Via lines 
2:5001/100@fidonet @20261005.000942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.000944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.021107 D'Bridge 4
2:292/854@Ward_Dossche @20261005.011359.UTC O/T-Track+ 2.85
2:280/5003.0 @20261005.002402.UTC FIDOGATE/ftntoss 4.4.14

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:280/2060
#NodeStampedElapsedSoftware
1 2:280/2060 2026-10-05 00:26 UTC – hpt/lnx 1.9.0-cur 2020-04-15
Raw Via lines 
2:280/2060 @20261005.002601.UTC hpt/lnx 1.9.0-cur 2020-04-15

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

Answered in 11m

The robot at 2:280/2060 bounced it back 11m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab074e3
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 00:05 UTC
Answered
2026-09-21 00:17 UTC by AroundMyRooms Ping Robot, 2:280/2060

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:292/854→+1h 3m2:292/854→-53m2:280/5003.0
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 00:05 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 00:05 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 02:06 local – D'Bridge 4
4 2:292/854 2026-09-21 01:08 UTC +1h 3m O/T-Track+ 2.85
5 2:280/5003.0 2026-09-21 00:15 UTC -53m FIDOGATE/ftntoss 4.4.14
Raw Via lines 
2:5001/100@fidonet @20260921.000553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.000555.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.020615 D'Bridge 4
2:292/854@Ward_Dossche @20260921.010859.UTC O/T-Track+ 2.85
2:280/5003.0 @20260921.001501.UTC FIDOGATE/ftntoss 4.4.14

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:280/2060
#NodeStampedElapsedSoftware
1 2:280/2060 2026-09-21 00:17 UTC – hpt/lnx 1.9.0-cur 2020-04-15
Raw Via lines 
2:280/2060 @20260921.001701.UTC hpt/lnx 1.9.0-cur 2020-04-15

Routed ping · 2026-09-06 23:59 UTC

Answered in 17m

The robot at 2:280/2060 bounced it back 17m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9dfe76
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-06 23:59 UTC
Answered
2026-09-07 00:17 UTC by AroundMyRooms Ping Robot, 2:280/2060

Outbound path

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

2:5020/715→2:292/854→+1h 4m2:292/854→-48m2:280/5003.0
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-06 23:59 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 02:01 local – D'Bridge 4
3 2:292/854 2026-09-07 01:03 UTC +1h 4m O/T-Track+ 2.85
4 2:280/5003.0 2026-09-07 00:15 UTC -48m FIDOGATE/ftntoss 4.4.14
Raw Via lines 
2:5020/715 @20260906.235949.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.020111 D'Bridge 4
2:292/854@Ward_Dossche @20260907.010359.UTC O/T-Track+ 2.85
2:280/5003.0 @20260907.001501.UTC FIDOGATE/ftntoss 4.4.14

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:280/2060
#NodeStampedElapsedSoftware
1 2:280/2060 2026-09-07 00:17 UTC – hpt/lnx 1.9.0-cur 2020-04-15
Raw Via lines 
2:280/2060 @20260907.001701.UTC hpt/lnx 1.9.0-cur 2020-04-15

Evidence

Replies

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

2026-10-19 00:17 UTC

pong unsecure PONG: PING

From AroundMyRooms Ping Robot, 2:280/2060 · answers 2:5001/100@fidonet 6ad55fc8

Path quoted in this reply

2:5001/100→+1s2:5020/715→2:292/854→+1h 4m2:292/854→-58m2:280/5003.0

This reply's own Via lines

  • 2:280/2060 @20261019.001701.UTC hpt/lnx 1.9.0-cur 2020-04-15

2026-10-05 00:26 UTC

pong unsecure PONG: PING

From AroundMyRooms Ping Robot, 2:280/2060 · answers 2:5001/100@fidonet 6ac2eac8

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:292/854→+1h 4m2:292/854→-49m2:280/5003.0

This reply's own Via lines

  • 2:280/2060 @20261005.002601.UTC hpt/lnx 1.9.0-cur 2020-04-15

2026-09-21 00:17 UTC

pong unsecure PONG: PING

From AroundMyRooms Ping Robot, 2:280/2060 · answers 2:5001/100@fidonet 6ab074e3

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:292/854→+1h 3m2:292/854→-53m2:280/5003.0

This reply's own Via lines

  • 2:280/2060 @20260921.001701.UTC hpt/lnx 1.9.0-cur 2020-04-15

2026-09-07 00:17 UTC

pong unsecure PONG: PING

From AroundMyRooms Ping Robot, 2:280/2060 · answers 2:5001/100@fidonet 6a9dfe76

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854→-48m2:280/5003.0

This reply's own Via lines

  • 2:280/2060 @20260907.001701.UTC hpt/lnx 1.9.0-cur 2020-04-15