NodelistDB

Netmail PING — 2:371/52

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

← All PING/TRACE nodes Node history for 2:371/52

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

Answered in 11h 35m

The robot at 2:371/52 bounced it back 11h 35m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad56928
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 01:07 UTC
Answered
2026-10-19 12:24 UTC by PING Robot, 2:371/52
Transit notices
1

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:371/52→2:371/0→2:240/1120→2:292/854→+1h 6m2:292/854
#NodeStampedElapsedSoftware
1 2:371/52 – – Squish/386 1.11 Mon Oct 19 2026 at 12:50 UTC
2 2:371/0 2026-10-19 13:50 local – CrashMail II/Linux 1.7
3 2:240/1120 2026-10-19 12:17 UTC – Itrack+ 2.0 FP000190
4 2:292/854 2026-10-19 14:21 local – D'Bridge 4
5 2:292/854 2026-10-19 13:23 UTC +1h 6m O/T-Track+ 2.85
Raw Via lines 
Squish/386 1.11 2:371/52, Mon Oct 19 2026 at 12:50 UTC
2:371/0 @20261019.135034 CrashMail II/Linux 1.7
2:240/1120@FidoNet @20261019.121758.75.UTC Itrack+ 2.0 FP000190
2:292/854 @20261019.142106 D'Bridge 4
2:292/854@Ward_Dossche @20261019.132359.UTC O/T-Track+ 2.85

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

Answered in 1h 0m

The robot at 2:371/52 bounced it back 1h 0m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2f428
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 01:04 UTC
Answered
2026-10-05 01:50 UTC by PING Robot, 2:371/52
Transit notices
1

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:371/52→2:371/0→2:240/1120→+22s2:240/1120→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:371/52 – – Squish/386 1.11 Mon Oct 05 2026 at 02:40 UTC
2 2:371/0 2026-10-05 03:41 local – CrashMail II/Linux 1.7
3 2:240/1120 2026-10-05 01:44 UTC – NMUPD 1.40 20120901
4 2:240/1120 2026-10-05 01:44 UTC +22s Itrack+ 2.0 FP000190
5 2:292/854 2026-10-05 03:46 local – D'Bridge 4
6 2:292/854 2026-10-05 02:49 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
Squish/386 1.11 2:371/52, Mon Oct 05 2026 at 02:40 UTC
2:371/0 @20261005.034128 CrashMail II/Linux 1.7
2:240/1120 @20261005.034400.54.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20261005.014422.78.UTC Itrack+ 2.0 FP000190
2:292/854 @20261005.034603 D'Bridge 4
2:292/854@Ward_Dossche @20261005.024900.UTC O/T-Track+ 2.85

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

Answered in 33m

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

Answered
MSGID
2:5001/100@fidonet 6ab07e43
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 00:45 UTC
Answered
2026-09-21 01:19 UTC by PING Robot, 2:371/52
Transit notices
1

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:371/52→2:371/0→2:240/1120→+11s2:240/1120→2:292/854→+1h 4m2:292/854
#NodeStampedElapsedSoftware
1 2:371/52 – – Squish/386 1.11 Mon Sep 21 2026 at 02:10 UTC
2 2:371/0 2026-09-21 03:11 local – CrashMail II/Linux 1.7
3 2:240/1120 2026-09-21 01:14 UTC – NMUPD 1.40 20120901
4 2:240/1120 2026-09-21 01:14 UTC +11s Itrack+ 2.0 FP000190
5 2:292/854 2026-09-21 03:16 local – D'Bridge 4
6 2:292/854 2026-09-21 02:19 UTC +1h 4m O/T-Track+ 2.85
Raw Via lines 
Squish/386 1.11 2:371/52, Mon Sep 21 2026 at 02:10 UTC
2:371/0 @20260921.031138 CrashMail II/Linux 1.7
2:240/1120 @20260921.031400.35.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20260921.011411.94.UTC Itrack+ 2.0 FP000190
2:292/854 @20260921.031617 D'Bridge 4
2:292/854@Ward_Dossche @20260921.021900.UTC O/T-Track+ 2.85

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

Answered in 45m

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

Answered
MSGID
2:5001/100@fidonet 6a9e07d6
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-07 00:39 UTC
Answered
2026-09-07 01:24 UTC by PING Robot, 2:371/52
Transit notices
1

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:371/52→2:371/0→2:240/1120→+6s2:240/1120→2:292/854→+1h 5m2:292/854
#NodeStampedElapsedSoftware
1 2:371/52 – – Squish/386 1.11 Mon Sep 07 2026 at 02:11 UTC
2 2:371/0 2026-09-07 03:11 local – CrashMail II/Linux 1.7
3 2:240/1120 2026-09-07 01:18 UTC – NMUPD 1.40 20120901
4 2:240/1120 2026-09-07 01:18 UTC +6s Itrack+ 2.0 FP000190
5 2:292/854 2026-09-07 03:21 local – D'Bridge 4
6 2:292/854 2026-09-07 02:23 UTC +1h 5m O/T-Track+ 2.85
Raw Via lines 
Squish/386 1.11 2:371/52, Mon Sep 07 2026 at 02:11 UTC
2:371/0 @20260907.031134 CrashMail II/Linux 1.7
2:240/1120 @20260907.031800.38.UTC+0200 NMUPD 1.40 20120901
2:240/1120@FidoNet @20260907.011806.70.UTC Itrack+ 2.0 FP000190
2:292/854 @20260907.032111 D'Bridge 4
2:292/854@Ward_Dossche @20260907.022359.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-19 12:24 UTC

pong PING

From PING Robot, 2:371/52 · answers 2:5001/100@fidonet 6ad56928

This reply's own Via lines

  • Squish/386 1.11 2:371/52, Mon Oct 19 2026 at 12:50 UTC
  • 2:371/0 @20261019.135034 CrashMail II/Linux 1.7
  • 2:240/1120@FidoNet @20261019.121758.75.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261019.142106 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.132359.UTC O/T-Track+ 2.85

2026-10-19 12:24 UTC

pong PING

From PING Robot, 2:371/52 · answers 2:5001/100@fidonet 6ad56928

This reply's own Via lines

  • Squish/386 1.11 2:371/52, Mon Oct 19 2026 at 12:50 UTC
  • 2:371/0 @20261019.135034 CrashMail II/Linux 1.7
  • 2:240/1120@FidoNet @20261019.121758.80.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261019.142106 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.132359.UTC O/T-Track+ 2.85

2026-10-19 11:39 UTC

trace Ping Trace Reply

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

This reply's own Via lines

  • 2:5001/100@fidonet @20261019.004942.UTC FidoMail v0.1.5
  • 2:5020/715 @20261019.010728.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:292/854 @20261019.030910 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261019.021400.UTC O/T-Track+ 2.85
  • 2:240/1120@FidoNet @20261019.113109.80.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261019.133606 D'Bridge 4

Software

ITR+ 2.0 FP000190   --- FidoMail v0.1.5

2026-10-05 01:50 UTC

pong PING

From PING Robot, 2:371/52 · answers 2:5001/100@fidonet 6ac2f428

This reply's own Via lines

  • Squish/386 1.11 2:371/52, Mon Oct 05 2026 at 02:40 UTC
  • 2:371/0 @20261005.034128 CrashMail II/Linux 1.7
  • 2:240/1120 @20261005.034400.54.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20261005.014422.78.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261005.034603 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.024900.UTC O/T-Track+ 2.85

2026-10-05 01:50 UTC

pong PING

From PING Robot, 2:371/52 · answers 2:5001/100@fidonet 6ac2f428

This reply's own Via lines

  • Squish/386 1.11 2:371/52, Mon Oct 05 2026 at 02:40 UTC
  • 2:371/0 @20261005.034128 CrashMail II/Linux 1.7
  • 2:240/1120 @20261005.034400.54.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20261005.014422.78.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261005.034603 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.024900.UTC O/T-Track+ 2.85

2026-10-05 01:20 UTC

trace Ping Trace Reply

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

This reply's own Via lines

  • 2:5001/100@fidonet @20261005.004942.UTC FidoMail d6aaa2b3
  • 2:5020/715 @20261005.010425.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:292/854 @20261005.030606 D'Bridge 4
  • 2:292/854@Ward_Dossche @20261005.020900.UTC O/T-Track+ 2.85
  • 2:240/1120 @20261005.031400.52.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20261005.011426.72.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20261005.031604 D'Bridge 4

Software

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

2026-09-21 01:19 UTC

pong PING

From PING Robot, 2:371/52 · answers 2:5001/100@fidonet 6ab07e43

This reply's own Via lines

  • Squish/386 1.11 2:371/52, Mon Sep 21 2026 at 02:10 UTC
  • 2:371/0 @20260921.031138 CrashMail II/Linux 1.7
  • 2:240/1120 @20260921.031400.35.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260921.011411.94.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260921.031617 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.021900.UTC O/T-Track+ 2.85

2026-09-21 01:19 UTC

pong PING

From PING Robot, 2:371/52 · answers 2:5001/100@fidonet 6ab07e43

This reply's own Via lines

  • Squish/386 1.11 2:371/52, Mon Sep 21 2026 at 02:10 UTC
  • 2:371/0 @20260921.031138 CrashMail II/Linux 1.7
  • 2:240/1120 @20260921.031400.35.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260921.011412.00.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260921.031617 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.021900.UTC O/T-Track+ 2.85

2026-09-21 00:59 UTC

trace Ping Trace Reply

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

This reply's own Via lines

  • 2:5001/100@fidonet @20260921.004553.UTC FidoMail 97f43bf5
  • 2:5020/715 @20260921.004554.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:292/854 @20260921.024611 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.014859.UTC O/T-Track+ 2.85
  • 2:240/1120 @20260921.025400.34.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260921.005406.49.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260921.025614 D'Bridge 4

Software

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

2026-09-07 01:24 UTC

pong PING

From PING Robot, 2:371/52 · answers 2:5001/100@fidonet 6a9e07d6

This reply's own Via lines

  • Squish/386 1.11 2:371/52, Mon Sep 07 2026 at 02:11 UTC
  • 2:371/0 @20260907.031134 CrashMail II/Linux 1.7
  • 2:240/1120 @20260907.031800.38.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260907.011806.70.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260907.032111 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.022359.UTC O/T-Track+ 2.85

2026-09-07 01:24 UTC

pong PING

From PING Robot, 2:371/52 · answers 2:5001/100@fidonet 6a9e07d6

This reply's own Via lines

  • Squish/386 1.11 2:371/52, Mon Sep 07 2026 at 02:11 UTC
  • 2:371/0 @20260907.031134 CrashMail II/Linux 1.7
  • 2:240/1120 @20260907.031800.38.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260907.011806.75.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260907.032111 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.022359.UTC O/T-Track+ 2.85

2026-09-07 00:54 UTC

trace Ping Trace Reply

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

This reply's own Via lines

  • 2:5020/715 @20260907.003949.UTC RNtrack 2.3.0/Lnx/Perl
  • 2:292/854 @20260907.024114 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.014359.UTC O/T-Track+ 2.85
  • 2:240/1120 @20260907.024900.34.UTC+0200 NMUPD 1.40 20120901
  • 2:240/1120@FidoNet @20260907.004904.51.UTC Itrack+ 2.0 FP000190
  • 2:292/854 @20260907.025113 D'Bridge 4

Software

ITR+ 2.0 FP000190   --- FidoMail v0.1.4-20-g980f7aa