NodelistDB

Netmail PING — 2:2448/1021

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

← All PING/TRACE nodes Node history for 2:2448/1021

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

Answered in 24m

The robot at 2:2448/1021 bounced it back 24m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ad55fc7
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-19 00:09 UTC
Answered
2026-10-19 00:34 UTC by PING, 2:2448/1021

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:2448/1021→2:240/5832→2:292/854
#NodeStampedElapsedSoftware
1 2:2448/1021 2026-10-19 02:20 local – FastEcho 1.46.1 42840
2 2:240/5832 2026-10-19 02:32 local – Itrack- 2.0
3 2:292/854 2026-10-19 02:34 local – D'Bridge 4
Raw Via lines 
2:2448/1021@fidonet @20261019.022002 FastEcho 1.46.1 42840
2:240/5832@fidonet.org @20261019.023238.23 Itrack- 2.0
2:292/854 @20261019.023414 D'Bridge 4

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

Answered in 25m

The robot at 2:2448/1021 bounced it back 25m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ac2eac7
First hop
2:5020/715@fidonet (rule)
Handed over
2026-10-05 00:09 UTC
Answered
2026-10-05 00:35 UTC by PING, 2:2448/1021

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:2448/1021→2:240/5832→2:292/854
#NodeStampedElapsedSoftware
1 2:2448/1021 2026-10-05 02:20 local – FastEcho 1.46.1 42840
2 2:240/5832 2026-10-05 02:32 local – Itrack- 2.0
3 2:292/854 2026-10-05 02:34 local – D'Bridge 4
Raw Via lines 
2:2448/1021@fidonet @20261005.022002 FastEcho 1.46.1 42840
2:240/5832@fidonet.org @20261005.023238.22 Itrack- 2.0
2:292/854 @20261005.023402 D'Bridge 4

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

Answered in 28m

The robot at 2:2448/1021 bounced it back 28m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6ab074e2
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-21 00:05 UTC
Answered
2026-09-21 00:34 UTC by PING, 2:2448/1021

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:2448/1021→2:240/5832→2:292/854→2:292/854
#NodeStampedElapsedSoftware
1 2:2448/1021 2026-09-21 02:10 local – FastEcho 1.46.1 42840
2 2:240/5832 2026-09-21 02:30 local – Itrack- 2.0
3 2:292/854 2026-09-21 02:31 local – D'Bridge 4
4 2:292/854 2026-09-21 01:33 UTC – O/T-Track+ 2.85
Raw Via lines 
2:2448/1021@fidonet @20260921.021002 FastEcho 1.46.1 42840
2:240/5832@fidonet.org @20260921.023019.74 Itrack- 2.0
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-06 23:59 UTC

Answered in 35m

The robot at 2:2448/1021 bounced it back 35m after it left 2:5001/100.

Answered
MSGID
2:5001/100@fidonet 6a9dfe75
First hop
2:5020/715@fidonet (rule)
Handed over
2026-09-06 23:59 UTC
Answered
2026-09-07 00:34 UTC by PING, 2:2448/1021

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:2448/1021→2:240/5832→2:292/854→2:292/854
#NodeStampedElapsedSoftware
1 2:2448/1021 2026-09-07 02:10 local – FastEcho 1.46.1 42840
2 2:240/5832 2026-09-07 02:30 local – Itrack- 2.0
3 2:292/854 2026-09-07 02:31 local – D'Bridge 4
4 2:292/854 2026-09-07 01:33 UTC – O/T-Track+ 2.85
Raw Via lines 
2:2448/1021@fidonet @20260907.021002 FastEcho 1.46.1 42840
2:240/5832@fidonet.org @20260907.023022.44 Itrack- 2.0
2:292/854 @20260907.023115 D'Bridge 4
2:292/854@Ward_Dossche @20260907.013359.UTC O/T-Track+ 2.85

Evidence

Replies

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

2026-10-19 00:34 UTC

pong PING

From PING, 2:2448/1021 · answers 2:5001/100@fidonet 6ad55fc7

This reply's own Via lines

  • 2:2448/1021@fidonet @20261019.022002 FastEcho 1.46.1 42840
  • 2:240/5832@fidonet.org @20261019.023238.23 Itrack- 2.0
  • 2:292/854 @20261019.023414 D'Bridge 4

2026-10-05 00:35 UTC

pong PING

From PING, 2:2448/1021 · answers 2:5001/100@fidonet 6ac2eac7

This reply's own Via lines

  • 2:2448/1021@fidonet @20261005.022002 FastEcho 1.46.1 42840
  • 2:240/5832@fidonet.org @20261005.023238.22 Itrack- 2.0
  • 2:292/854 @20261005.023402 D'Bridge 4

2026-09-21 00:34 UTC

pong PING

From PING, 2:2448/1021 · answers 2:5001/100@fidonet 6ab074e2

This reply's own Via lines

  • 2:2448/1021@fidonet @20260921.021002 FastEcho 1.46.1 42840
  • 2:240/5832@fidonet.org @20260921.023019.74 Itrack- 2.0
  • 2:292/854 @20260921.023112 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260921.013359.UTC O/T-Track+ 2.85

2026-09-07 00:34 UTC

pong PING

From PING, 2:2448/1021 · answers 2:5001/100@fidonet 6a9dfe75

This reply's own Via lines

  • 2:2448/1021@fidonet @20260907.021002 FastEcho 1.46.1 42840
  • 2:240/5832@fidonet.org @20260907.023022.44 Itrack- 2.0
  • 2:292/854 @20260907.023115 D'Bridge 4
  • 2:292/854@Ward_Dossche @20260907.013359.UTC O/T-Track+ 2.85