Netmail PING 1:320/319

← All PING/TRACE nodes Node history for 1:320/319

Routed ping · 2026-10-18 23:39 UTC

No answer

Nothing came back within seven days of sending.

No answer

MSGID: 2:5001/100@fidonet 6ad558c1
First hop: 2:5020/715@fidonet (rule)
Handed over: 2026-10-18 23:39 UTC
Transit notices: 1
Note: no answer within 168h0m0s

Routed ping · 2026-10-04 23:39 UTC

No answer

Nothing came back within seven days of sending.

No answer

MSGID: 2:5001/100@fidonet 6ac2e3c1
First hop: 2:5020/715@fidonet (rule)
Handed over: 2026-10-04 23:39 UTC
Transit notices: 1
Note: no answer within 168h0m0s

Routed ping · 2026-09-20 23:35 UTC

No answer

Nothing came back within seven days of sending.

No answer

MSGID: 2:5001/100@fidonet 6ab06ddc
First hop: 2:5020/715@fidonet (rule)
Handed over: 2026-09-20 23:35 UTC
Transit notices: 1
Note: no answer within 168h0m0s

Routed ping · 2026-09-06 23:29 UTC

Answered in 10m

The robot at 1:320/319 bounced it back 10m after it left 2:5001/100.

Answered

MSGID: 2:5001/100@fidonet 6a9df76f
First hop: 2:5020/715@fidonet (rule)
Handed over: 2026-09-06 23:29 UTC
Answered: 2026-09-06 23:39 UTC by Ping service, 1:320/319
Robot: MBSE-FIDO 1.1.7.2 (Linux-x86_64)
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 4m2:292/854→-59m1:320/219

#	Node	Stamped	Elapsed	Software
1	2:5020/715	2026-09-06 23:29 UTC	–	RNtrack 2.3.0/Lnx/Perl
2	2:292/854	2026-09-07 01:31 local	–	D'Bridge 4
3	2:292/854	2026-09-07 00:33 UTC	+1h 4m	O/T-Track+ 2.85
4	1:320/219	2026-09-06 23:34 UTC	-59m	mbfido 1.1.7.2

Raw Via lines

2:5020/715 @20260906.232955.UTC RNtrack 2.3.0/Lnx/Perl
2:292/854 @20260907.013114 D'Bridge 4
2:292/854@Ward_Dossche @20260907.003359.UTC O/T-Track+ 2.85
1:320/219@fidonet @20260906.233459.UTC mbfido 1.1.7.2

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.

1:320/319→+20s1:320/219→1:229/426→-54s1:229/426→2:292/854

#	Node	Stamped	Elapsed	Software
1	1:320/319	2026-09-06 23:35 UTC	–	mbfido 1.1.7.2
2	1:320/219	2026-09-06 23:36 UTC	+20s	mbfido 1.1.7.2
3	1:229/426	2026-09-06 19:35 local	–	D'Bridge 4
4	1:229/426	2026-09-06 23:35 UTC	-54s	O/T-Track+ 2.85
5	2:292/854	2026-09-07 01:39 local	–	D'Bridge 4

Raw Via lines

1:320/319@fidonet @20260906.233548.UTC mbfido 1.1.7.2
1:320/219@fidonet @20260906.233608.UTC mbfido 1.1.7.2
1:229/426 @20260906.193514 D'Bridge 4
1:229/426@fidonet @20260906.233514.UTC O/T-Track+ 2.85
2:292/854 @20260907.013910 D'Bridge 4

Evidence

Replies

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

2026-10-18 23:59 UTC

trace Re: Your PING Request

From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6ad558c1

Path quoted in this reply

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

This reply's own Via lines

1:320/219@fidonet @20261018.234448.UTC mbfido 1.1.7.2
1:229/426 @20261018.194459 D'Bridge 4
1:229/426@fidonet @20261018.234459.UTC O/T-Track+ 2.85
2:292/854 @20261019.015616 D'Bridge 4
2:292/854@Ward_Dossche @20261019.005859.UTC O/T-Track+ 2.85

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64) ---

2026-10-05 00:05 UTC

trace Re: Your PING Request

From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6ac2e3c1

Path quoted in this reply

2:5001/100→+10m2:5020/715→2:292/854→+1h 4m2:292/854

This reply's own Via lines

1:320/219@fidonet @20261004.235513.UTC mbfido 1.1.7.2
1:229/426 @20261004.195542 D'Bridge 4
1:229/426@fidonet @20261004.235542.UTC O/T-Track+ 2.85
2:292/854 @20261005.020104 D'Bridge 4
2:292/854@Ward_Dossche @20261005.010400.UTC O/T-Track+ 2.85

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64) ---

2026-09-20 23:49 UTC

trace Re: Your PING Request

From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6ab06ddc

Path quoted in this reply

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

This reply's own Via lines

1:320/219@fidonet @20260920.233932.UTC mbfido 1.1.7.2
1:229/426 @20260920.193912 D'Bridge 4
1:229/426@fidonet @20260920.233912.UTC O/T-Track+ 2.85
2:292/854 @20260921.014915 D'Bridge 4

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64) ---

2026-09-06 23:39 UTC

trace Re: Your PING Request

From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6a9df76f

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854

This reply's own Via lines

1:320/219@fidonet @20260906.233458.UTC mbfido 1.1.7.2
1:229/426 @20260906.193417 D'Bridge 4
1:229/426@fidonet @20260906.233417.UTC O/T-Track+ 2.85
2:292/854 @20260907.013910 D'Bridge 4

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64) ---

2026-09-06 23:39 UTC

pong Re: Your PING Request

From Ping service, 1:320/319 · answers 2:5001/100@fidonet 6a9df76f

Path quoted in this reply

2:5020/715→2:292/854→+1h 4m2:292/854→-59m1:320/219

This reply's own Via lines

1:320/319@fidonet @20260906.233548.UTC mbfido 1.1.7.2
1:320/219@fidonet @20260906.233608.UTC mbfido 1.1.7.2
1:229/426 @20260906.193514 D'Bridge 4
1:229/426@fidonet @20260906.233514.UTC O/T-Track+ 2.85
2:292/854 @20260907.013910 D'Bridge 4

Software

MBSE-FIDO 1.1.7.2 (Linux-x86_64) --- MBSE BBS v1.1.7.2 (Linux-x86_64)