NodelistDB

Netmail PING — 2:291/111

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

← All PING/TRACE nodes Node history for 2:291/111

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

Answered in 11h 0m

The robot at 2:291/111 bounced it back 11h 0m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad56220
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 00:19 UTC
Answered
2026-10-19 11:19 UTC by FMail PING bot, 2:291/111
Robot
FMail-W32 2.3.1.0

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→-59m2:291/111
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-19 00:19 UTC – FidoMail v0.1.5
2 2:5020/715 2026-10-19 00:19 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-19 02:21 local – D'Bridge 4
4 2:292/854 2026-10-19 01:24 UTC +1h 4m O/T-Track+ 2.85
5 2:291/111 2026-10-19 00:24 UTC -59m FMail-W32(Toss) 2.3.1.0
Raw Via lines 
2:5001/100@fidonet @20261019.001942.UTC FidoMail v0.1.5
2:5020/715 @20261019.001944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261019.022113 D'Bridge 4
2:292/854@Ward_Dossche @20261019.012400.UTC O/T-Track+ 2.85
2:291/111 @20261019.002443.310.UTC FMail-W32(Toss) 2.3.1.0

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:291/111→+10h 51m2:240/1120→2:292/854
#NodeStampedElapsedSoftware
1 2:291/111 2026-10-19 00:24 UTC – FMail-W32(Pack) 2.3.1.0
2 2:240/1120 2026-10-19 11:16 UTC +10h 51m Itrack+ 2.0 FP000190
3 2:292/854 2026-10-19 13:19 local – D'Bridge 4
Raw Via lines 
2:291/111 @20261019.002443.372.UTC FMail-W32(Pack) 2.3.1.0
2:240/1120@FidoNet @20261019.111608.75.UTC Itrack+ 2.0 FP000190
2:292/854 @20261019.131914 D'Bridge 4

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

Answered in 20m

The robot at 2:291/111 bounced it back 20m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2ed1f
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 00:19 UTC
Answered
2026-10-05 00:39 UTC by FMail PING bot, 2:291/111
Robot
FMail-W32 2.3.1.0

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→-58m2:291/111
#NodeStampedElapsedSoftware
1 2:5001/100 2026-10-05 00:19 UTC – FidoMail d6aaa2b3
2 2:5020/715 2026-10-05 00:19 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-10-05 02:21 local – D'Bridge 4
4 2:292/854 2026-10-05 01:23 UTC +1h 4m O/T-Track+ 2.85
5 2:291/111 2026-10-05 00:25 UTC -58m FMail-W32(Toss) 2.3.1.0
Raw Via lines 
2:5001/100@fidonet @20261005.001942.UTC FidoMail d6aaa2b3
2:5020/715 @20261005.001944.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20261005.022105 D'Bridge 4
2:292/854@Ward_Dossche @20261005.012359.UTC O/T-Track+ 2.85
2:291/111 @20261005.002508.917.UTC FMail-W32(Toss) 2.3.1.0

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:291/111→+7m2:240/1120→+11s2:240/1120→2:292/854→+1h 5m2:292/854
#NodeStampedElapsedSoftware
1 2:291/111 2026-10-05 00:25 UTC – FMail-W32(Pack) 2.3.1.0
2 2:240/1120 2026-10-05 00:33 UTC +7m NMUPD 1.40 20120901
3 2:240/1120 2026-10-05 00:33 UTC +11s Itrack+ 2.0 FP000190
4 2:292/854 2026-10-05 02:36 local – D'Bridge 4
5 2:292/854 2026-10-05 01:39 UTC +1h 5m O/T-Track+ 2.85
Raw Via lines 
2:291/111 @20261005.002508.986.UTC FMail-W32(Pack) 2.3.1.0
2:240/1120 @20261005.023300.68.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20261005.003311.61.UTC Itrack+ 2.0 FP000190
2:292/854 @20261005.023603 D'Bridge 4
2:292/854@Ward_Dossche @20261005.013900.UTC O/T-Track+ 2.85

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

Answered in 18m

The robot at 2:291/111 bounced it back 18m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab0773b
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 00:15 UTC
Answered
2026-09-21 00:34 UTC by FMail PING bot, 2:291/111
Robot
FMail-W32 2.3.1.0

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→-59m2:291/111
#NodeStampedElapsedSoftware
1 2:5001/100 2026-09-21 00:15 UTC – FidoMail 97f43bf5
2 2:5020/715 2026-09-21 00:15 UTC +2s RNtrack 2.3.0/Lnx/Perl
3 2:292/854 2026-09-21 02:16 local – D'Bridge 4
4 2:292/854 2026-09-21 01:18 UTC +1h 3m O/T-Track+ 2.85
5 2:291/111 2026-09-21 00:19 UTC -59m FMail-W32(Toss) 2.3.1.0
Raw Via lines 
2:5001/100@fidonet @20260921.001553.UTC FidoMail 97f43bf5
2:5020/715 @20260921.001555.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260921.021613 D'Bridge 4
2:292/854@Ward_Dossche @20260921.011859.UTC O/T-Track+ 2.85
2:291/111 @20260921.001926.644.UTC FMail-W32(Toss) 2.3.1.0

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:291/111→+8m2:240/1120→+10s2:240/1120→2:292/854→+1h 5m2:292/854
#NodeStampedElapsedSoftware
1 2:291/111 2026-09-21 00:19 UTC – FMail-W32(Pack) 2.3.1.0
2 2:240/1120 2026-09-21 00:28 UTC +8m NMUPD 1.40 20120901
3 2:240/1120 2026-09-21 00:28 UTC +10s Itrack+ 2.0 FP000190
4 2:292/854 2026-09-21 02:31 local – D'Bridge 4
5 2:292/854 2026-09-21 01:33 UTC +1h 5m O/T-Track+ 2.85
Raw Via lines 
2:291/111 @20260921.001926.707.UTC FMail-W32(Pack) 2.3.1.0
2:240/1120 @20260921.022800.40.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20260921.002810.84.UTC Itrack+ 2.0 FP000190
2:292/854 @20260921.023112 D'Bridge 4
2:292/854@Ward_Dossche @20260921.013359.UTC O/T-Track+ 2.85

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

Answered in 15m

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

Answered
MSGID
2:5001/100@fidonet 6a9e00ce
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 00:09 UTC
Answered
2026-09-07 00:24 UTC by FMail PING bot, 2:291/111
Robot
FMail-W32 2.3.1.0

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→-59m2:291/111
#NodeStampedElapsedSoftware
1 2:5020/715 2026-09-07 00:09 UTC – RNtrack 2.3.0/Lnx/Perl
2 2:292/854 2026-09-07 02:11 local – D'Bridge 4
3 2:292/854 2026-09-07 01:13 UTC +1h 4m O/T-Track+ 2.85
4 2:291/111 2026-09-07 00:14 UTC -59m FMail-W32(Toss) 2.3.1.0
Raw Via lines 
2:5020/715 @20260907.000949.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.021109 D'Bridge 4
2:292/854@Ward_Dossche @20260907.011359.UTC O/T-Track+ 2.85
2:291/111 @20260907.001454.498.UTC FMail-W32(Toss) 2.3.1.0

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:291/111→+8m2:240/1120→+9s2:240/1120→2:292/854
#NodeStampedElapsedSoftware
1 2:291/111 2026-09-07 00:14 UTC – FMail-W32(Pack) 2.3.1.0
2 2:240/1120 2026-09-07 00:23 UTC +8m NMUPD 1.40 20120901
3 2:240/1120 2026-09-07 00:23 UTC +9s Itrack+ 2.0 FP000190
4 2:292/854 2026-09-07 02:24 local – D'Bridge 4
Raw Via lines 
2:291/111 @20260907.001454.561.UTC FMail-W32(Pack) 2.3.1.0
2:240/1120 @20260907.022300.35.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20260907.002309.08.UTC Itrack+ 2.0 FP000190
2:292/854 @20260907.022411 D'Bridge 4

Evidence

Replies

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

2026-10-19 11:19 UTC

pong Pong: PING

From FMail PING bot, 2:291/111 · answers 2:5001/100@fidonet 6ad56220

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:292/854→+1h 4m2:292/854→-59m2:291/111

This reply's own Via lines

  • 2:291/111 @20261019.002443.372.UTC FMail-W32(Pack) 2.3.1.0
  • 2:240/1120@FidoNet @20261019.111608.75.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261019.131914 D'Bridge 4

Software

FMail-W32 2.3.1.0   --- FidoMail v0.1.5

2026-10-05 00:39 UTC

pong Pong: PING

From FMail PING bot, 2:291/111 · answers 2:5001/100@fidonet 6ac2ed1f

Path quoted in this reply

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

This reply's own Via lines

  • 2:291/111 @20261005.002508.986.UTC FMail-W32(Pack) 2.3.1.0
  • 2:240/1120 @20261005.023300.68.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20261005.003311.61.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261005.023603 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.013900.UTC O/T-Track+ 2.85

Software

FMail-W32 2.3.1.0   --- FidoMail v0.1.4-211-gd6aaa2b3

2026-09-21 00:34 UTC

pong Pong: PING

From FMail PING bot, 2:291/111 · answers 2:5001/100@fidonet 6ab0773b

Path quoted in this reply

2:5001/100→+2s2:5020/715→2:292/854→+1h 3m2:292/854→-59m2:291/111

This reply's own Via lines

  • 2:291/111 @20260921.001926.707.UTC FMail-W32(Pack) 2.3.1.0
  • 2:240/1120 @20260921.022800.40.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260921.002810.84.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260921.023112 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.013359.UTC O/T-Track+ 2.85

Software

FMail-W32 2.3.1.0   --- FidoMail v0.1.4-122-g97f43bf5

2026-09-07 00:24 UTC

pong Pong: PING

From FMail PING bot, 2:291/111 · answers 2:5001/100@fidonet 6a9e00ce

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854→-59m2:291/111

This reply's own Via lines

  • 2:291/111 @20260907.001454.561.UTC FMail-W32(Pack) 2.3.1.0
  • 2:240/1120 @20260907.022300.35.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260907.002309.08.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260907.022411 D'Bridge 4

Software

FMail-W32 2.3.1.0   --- FidoMail v0.1.4-20-g980f7aa