NodelistDB

Netmail PING — 2:550/0

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

← All PING/TRACE nodes Node history for 2:550/0

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

Answered in 9h 53m

The robot at 2:550/0 bounced it back 9h 53m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad574e0
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:39 UTC
Answered
2026-10-19 11:32 UTC by PING Robot, 2:550/0
Transit notices
1

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→+8h 47m2:240/1120
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 01:39 UTC – FidoMail 65fd0ae9
2 2:5020/715 2026-10-19 01:39 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 03:41 local – D'Bridge 4
4 2:292/854 2026-10-19 02:44 UTC +1h 4m O/T-Track+ 2.85
5 2:240/1120 2026-10-19 11:31 UTC +8h 47m Itrack+ 2.0 FP000190
Raw Via lines 
2:5001/100@fidonet @20261019.013942.UTC FidoMail 65fd0ae9
2:5020/715 @20261019.013944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.034116 D'Bridge 4
2:292/854@Ward_Dossche @20261019.024400.UTC O/T-Track+ 2.85
2:240/1120@FidoNet @20261019.113109.91.UTC Itrack+ 2.0 FP000190

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:550/278→+44s2:5020/715
#NodeStampedElapsedSoftware
1 2:550/278 2026-10-19 11:32 UTC – hpt/lnx 1.9 2023-02-24
2 2:5020/715 2026-10-19 11:32 UTC +44s RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:550/278 @20261019.113212.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20261019.113256.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 15m

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

Answered
MSGID
2:5001/100@fidonet 6ac2ffde
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:39 UTC
Answered
2026-10-05 01:54 UTC by PING Robot, 2:550/0
Transit notices
1

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→-53m2:240/1120→+26s2:240/1120
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 01:39 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 01:39 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 03:41 local – D'Bridge 4
4 2:292/854 2026-10-05 02:43 UTC +1h 4m O/T-Track+ 2.85
5 2:240/1120 2026-10-05 01:50 UTC -53m NMUPD 1.40 20120901
6 2:240/1120 2026-10-05 01:50 UTC +26s Itrack+ 2.0 FP000190
Raw Via lines 
2:5001/100@fidonet @20261005.013942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.013943.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.034107 D'Bridge 4
2:292/854@Ward_Dossche @20261005.024359.UTC O/T-Track+ 2.85
2:240/1120 @20261005.035000.52.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20261005.015026.94.UTC Itrack+ 2.0 FP000190

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:550/278→+3m2:5020/715
#NodeStampedElapsedSoftware
1 2:550/278 2026-10-05 01:51 UTC – hpt/lnx 1.9 2023-02-24
2 2:5020/715 2026-10-05 01:54 UTC +3m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:550/278 @20261005.015126.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20261005.015441.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 14m

The robot at 2:550/0 bounced it back 14m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab089f9
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 01:35 UTC
Answered
2026-09-21 01:50 UTC by PING Robot, 2:550/0
Transit notices
1

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 3m2:292/854→-57m2:240/1120→+6s2:240/1120
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 01:35 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 01:35 UTC +1s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 03:36 local – D'Bridge 4
4 2:292/854 2026-09-21 02:39 UTC +1h 3m O/T-Track+ 2.85
5 2:240/1120 2026-09-21 01:42 UTC -57m NMUPD 1.40 20120901
6 2:240/1120 2026-09-21 01:42 UTC +6s Itrack+ 2.0 FP000190
Raw Via lines 
2:5001/100@fidonet @20260921.013553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.013554.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.033613 D'Bridge 4
2:292/854@Ward_Dossche @20260921.023900.UTC O/T-Track+ 2.85
2:240/1120 @20260921.034200.31.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20260921.014206.40.UTC Itrack+ 2.0 FP000190

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:550/278→+7m2:5020/715
#NodeStampedElapsedSoftware
1 2:550/278 2026-09-21 01:42 UTC – hpt/lnx 1.9 2023-02-24
2 2:5020/715 2026-09-21 01:50 UTC +7m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:550/278 @20260921.014248.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20260921.015012.UTC RNtrack 2.3.0/Lnx/Perl

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

Answered in 14m

The robot at 2:550/0 bounced it back 14m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9e10b2
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 01:17 UTC
Answered
2026-09-07 01:31 UTC by PING Robot, 2:550/0
Transit notices
1

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 6m2:292/854→-55m2:240/1120→+12s2:240/1120
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 01:17 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 03:21 local – D'Bridge 4
3 2:292/854 2026-09-07 02:23 UTC +1h 6m O/T-Track+ 2.85
4 2:240/1120 2026-09-07 01:28 UTC -55m NMUPD 1.40 20120901
5 2:240/1120 2026-09-07 01:28 UTC +12s Itrack+ 2.0 FP000190
Raw Via lines 
2:5020/715 @20260907.011739.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.032111 D'Bridge 4
2:292/854@Ward_Dossche @20260907.022359.UTC O/T-Track+ 2.85
2:240/1120 @20260907.032800.39.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20260907.012812.08.UTC Itrack+ 2.0 FP000190

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:550/278→+3m2:5020/715
#NodeStampedElapsedSoftware
1 2:550/278 2026-09-07 01:28 UTC – hpt/lnx 1.9 2023-02-24
2 2:5020/715 2026-09-07 01:31 UTC +3m RNtrack 2.3.0/Lnx/Perl
Raw Via lines 
2:550/278 @20260907.012844.UTC hpt/lnx 1.9 2023-02-24
2:5020/715 @20260907.013145.UTC RNtrack 2.3.0/Lnx/Perl

Evidence

Replies

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

2026-10-19 11:39 UTC

trace Ping Trace Reply

From Ping Robot, 2:240/1120 · answers 2:5001/100@fidonet 6ad574e0

This reply's own Via lines

  • 2:5001/100@fidonet @20261019.013942.UTC FidoMail 65fd0ae9
  • 2:5020/715 @20261019.013944.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:292/854 @20261019.034116 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.024400.UTC O/T-Track+ 2.85
  • 2:240/1120@FidoNet @20261019.113109.91.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261019.133606 D'Bridge 4

Software

ITR+ 2.0 FP000190   --- FidoMail v0.1.5-2-g65fd0ae9

2026-10-19 11:32 UTC

pong PING reply: PING

From PING Robot, 2:550/0 · answers 2:5001/100@fidonet 6ad574e0

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:292/854→+1h 4m2:292/854→+8h 47m2:240/1120

This reply's own Via lines

  • 2:550/278 @20261019.113212.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20261019.113256.UTC RNtrack 2.3.0/Lnx/Perl

2026-10-05 02:00 UTC

trace Ping Trace Reply

From Ping Robot, 2:240/1120 · answers 2:5001/100@fidonet 6ac2ffde

This reply's own Via lines

  • 2:5001/100@fidonet @20261005.013942.UTC FidoMail d6aaa2b3
  • 2:5020/715 @20261005.013943.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:292/854 @20261005.034107 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.024359.UTC O/T-Track+ 2.85
  • 2:240/1120 @20261005.035000.52.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20261005.015026.94.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261005.035607 D'Bridge 4

Software

ITR+ 2.0 FP000190   --- FidoMail v0.1.4-211-gd6aaa2b3

2026-10-05 01:54 UTC

pong PING reply: PING

From PING Robot, 2:550/0 · answers 2:5001/100@fidonet 6ac2ffde

Path quoted in this reply

2:5001/100→+1s2:5020/715→2:292/854→+1h 4m2:292/854→-53m2:240/1120→+26s2:240/1120

This reply's own Via lines

  • 2:550/278 @20261005.015126.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20261005.015441.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-21 01:50 UTC

pong PING reply: PING

From PING Robot, 2:550/0 · answers 2:5001/100@fidonet 6ab089f9

Path quoted in this reply

2:5001/100→+1s2:5020/715→2:292/854→+1h 3m2:292/854→-57m2:240/1120→+6s2:240/1120

This reply's own Via lines

  • 2:550/278 @20260921.014248.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20260921.015012.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-21 01:49 UTC

trace Ping Trace Reply

From Ping Robot, 2:240/1120 · answers 2:5001/100@fidonet 6ab089f9

This reply's own Via lines

  • 2:5001/100@fidonet @20260921.013553.UTC FidoMail 97f43bf5
  • 2:5020/715 @20260921.013554.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:292/854 @20260921.033613 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.023900.UTC O/T-Track+ 2.85
  • 2:240/1120 @20260921.034200.31.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260921.014206.35.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260921.034612 D'Bridge 4

Software

ITR+ 2.0 FP000190   --- FidoMail v0.1.4-122-g97f43bf5

2026-09-07 01:31 UTC

pong PING reply: PING

From PING Robot, 2:550/0 · answers 2:5001/100@fidonet 6a9e10b2

Path quoted in this reply

2:5020/715→2:292/854→+1h 6m2:292/854→-55m2:240/1120→+12s2:240/1120

This reply's own Via lines

  • 2:550/278 @20260907.012844.UTC hpt/lnx 1.9 2023-02-24
  • 2:5020/715 @20260907.013145.UTC RNtrack 2.3.0/Lnx/Perl

2026-09-07 01:29 UTC

trace Ping Trace Reply

From Ping Robot, 2:240/1120 · answers 2:5001/100@fidonet 6a9e10b2

This reply's own Via lines

  • 2:5020/715 @20260907.011739.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:292/854 @20260907.032111 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.022359.UTC O/T-Track+ 2.85
  • 2:240/1120 @20260907.032800.39.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260907.012812.08.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260907.032910 D'Bridge 4

Software

ITR+ 2.0 FP000190   --- FidoMail v0.1.4-23-ga499114