NodelistDB

Netmail PING — 2:5010/278

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

← All PING/TRACE nodes Node history for 2:5010/278

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

Answered in 7m

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

Answered
MSGID
2:5001/100@fidonet 6ad56dd7
First hop
2:5020/715@fidonet (rule)
Answered
2026-10-19 01:16 UTC by PING Robot, 2:5010/278

Outbound path

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

2:5001/100→+3s2:5020/715→+15s2:5010/352
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:09 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:09 UTC +3s RNtrack 2.3.0/Lnx/Perl
3 2:5010/352 2026-10-19 01:10 UTC +15s RNtrack 2.3.1/FBSD
Raw Via lines 
2:5001/100@fidonet @20261019.010942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.010945.UTC RNtrack 2.3.0/Lnx/Perl
2:5010/352 @20261019.011000.UTC RNtrack 2.3.1/FBSD

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:5010/278→+38s2:550/278→+29s2:5020/715
#NodeStampedElapsedSoftware
1 2:5010/278 2026-10-19 01:15 UTC – hpt/lnx 1.9 2023-02-24
2 2:550/278 2026-10-19 01:16 UTC +38s hpt/lnx 1.9 2023-02-24
3 2:5020/715 2026-10-19 01:16 UTC +29s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5010/278 @20261019.011549.UTC hpt/lnx 1.9 2023-02-24
2:550/278 @20261019.011627.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20261019.011656.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 22m

The robot at 2:5010/278 bounced it back 22m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2f8d7
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:09 UTC
Answered
2026-10-05 01:31 UTC by PING Robot, 2:5010/278

Outbound path

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

2:5001/100→+4s2:5020/715→+14s2:5010/352
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:09 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:09 UTC +4s RNtrack 2.3.0/Lnx/Perl
3 2:5010/352 2026-10-05 01:10 UTC +14s RNtrack 2.3.1/FBSD
Raw Via lines 
2:5001/100@fidonet @20261005.010942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.010946.UTC RNtrack 2.3.0/Lnx/Perl
2:5010/352 @20261005.011000.UTC RNtrack 2.3.1/FBSD

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:5010/278→+8m2:550/278→+3m2:5020/715
#NodeStampedElapsedSoftware
1 2:5010/278 2026-10-05 01:20 UTC – hpt/lnx 1.9 2023-02-24
2 2:550/278 2026-10-05 01:28 UTC +8m hpt/lnx 1.9 2023-02-24
3 2:5020/715 2026-10-05 01:31 UTC +3m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5010/278 @20261005.012014.UTC hpt/lnx 1.9 2023-02-24
2:550/278 @20261005.012839.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20261005.013141.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 15m

The robot at 2:5010/278 bounced it back 15m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab082f2
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:05 UTC
Answered
2026-09-21 01:21 UTC by PING Robot, 2:5010/278

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→+5s2:5010/352
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:05 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:05 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:5010/352 2026-09-21 01:06 UTC +5s RNtrack 2.3.1/FBSD
Raw Via lines 
2:5001/100@fidonet @20260921.010553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.010555.UTC RNtrack 2.3.0/Lnx/Perl
2:5010/352 @20260921.010600.UTC RNtrack 2.3.1/FBSD

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:5010/278→+1m2:550/278→+9s2:5020/715
#NodeStampedElapsedSoftware
1 2:5010/278 2026-09-21 01:20 UTC – hpt/lnx 1.9 2023-02-24
2 2:550/278 2026-09-21 01:21 UTC +1m hpt/lnx 1.9 2023-02-24
3 2:5020/715 2026-09-21 01:21 UTC +9s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5010/278 @20260921.012012.UTC hpt/lnx 1.9 2023-02-24
2:550/278 @20260921.012126.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20260921.012135.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 23m

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

Answered
MSGID
2:5001/100@fidonet 6a9e0c85
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:11 UTC
Answered
2026-09-07 01:23 UTC by PING Robot, 2:5010/278

Outbound path

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

2:5020/715→+1m2:5010/352
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:11 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:5010/352 2026-09-07 01:13 UTC +1m RNtrack 2.3.1/FBSD
Raw Via lines 
2:5020/715 @20260907.011159.UTC RNtrack 2.3.0/Lnx/Perl
2:5010/352 @20260907.011300.UTC RNtrack 2.3.1/FBSD

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:5010/278→+48s2:550/278→+2m2:5020/715
#NodeStampedElapsedSoftware
1 2:5010/278 2026-09-07 01:20 UTC – hpt/lnx 1.9 2023-02-24
2 2:550/278 2026-09-07 01:20 UTC +48s hpt/lnx 1.9 2023-02-24
3 2:5020/715 2026-09-07 01:23 UTC +2m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:5010/278 @20260907.012010.UTC hpt/lnx 1.9 2023-02-24
2:550/278 @20260907.012058.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20260907.012346.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-10-19 01:16 UTC

pong PING reply: PING

From PING Robot, 2:5010/278 · answers 2:5001/100@fidonet 6ad56dd7

Path quoted in this reply

2:5001/100→+3s2:5020/715→+15s2:5010/352

This reply's own Via lines

  • 2:5010/278 @20261019.011549.UTC hpt/lnx 1.9 2023-02-24
  • 2:550/278 @20261019.011627.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20261019.011656.UTC RNtrack 2.3.0/Lnx/Perl

2026-10-05 01:31 UTC

pong PING reply: PING

From PING Robot, 2:5010/278 · answers 2:5001/100@fidonet 6ac2f8d7

Path quoted in this reply

2:5001/100→+4s2:5020/715→+14s2:5010/352

This reply's own Via lines

  • 2:5010/278 @20261005.012014.UTC hpt/lnx 1.9 2023-02-24
  • 2:550/278 @20261005.012839.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20261005.013141.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-21 01:21 UTC

pong PING reply: PING

From PING Robot, 2:5010/278 · answers 2:5001/100@fidonet 6ab082f2

Path quoted in this reply

2:5001/100→+2s2:5020/715→+5s2:5010/352

This reply's own Via lines

  • 2:5010/278 @20260921.012012.UTC hpt/lnx 1.9 2023-02-24
  • 2:550/278 @20260921.012126.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20260921.012135.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-07 01:23 UTC

pong PING reply: PING

From PING Robot, 2:5010/278 · answers 2:5001/100@fidonet 6a9e0c85

Path quoted in this reply

2:5020/715→+1m2:5010/352

This reply's own Via lines

  • 2:5010/278 @20260907.012010.UTC hpt/lnx 1.9 2023-02-24
  • 2:550/278 @20260907.012058.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20260907.012346.UTC RNtrack 2.3.0/Lnx/Perl