Routed ping · 2026-10-18 22:59 UTC
No answer
Nothing came back within seven days of sending.
Routed ping · 2026-10-04 22:59 UTC
No answer
Nothing came back within seven days of sending.
Routed ping · 2026-09-20 22:55 UTC
No answer
Nothing came back within seven days of sending.
Routed ping · 2026-09-06 22:49 UTC
Answered in 30m
The robot at 1:1/119 bounced it back 30m after it left 2:5001/100.
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→1:229/426→-1h 0m1:229/426→+9m1:1/19
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:5020/715 | 2026-09-06 22:49 UTC | – | RNtrack 2.3.0/Lnx/Perl |
| 2 | 2:292/854 | 2026-09-07 00:51 local | – | D'Bridge 4 |
| 3 | 2:292/854 | 2026-09-06 23:53 UTC | +1h 4m | O/T-Track+ 2.85 |
| 4 | 1:229/426 | 2026-09-06 18:53 local | – | D'Bridge 4 |
| 5 | 1:229/426 | 2026-09-06 22:53 UTC | -1h 0m | O/T-Track+ 2.85 |
| 6 | 1:1/19 | 2026-09-06 23:02 UTC | +9m | mbfido 1.1.7.2 |
Raw Via lines
2:5020/715 @20260906.224948.UTC RNtrack 2.3.0/Lnx/Perl 2:292/854 @20260907.005107 D'Bridge 4 2:292/854@Ward_Dossche @20260906.235359.UTC O/T-Track+ 2.85 1:229/426 @20260906.185340 D'Bridge 4 1:229/426@fidonet @20260906.225340.UTC O/T-Track+ 2.85 1:1/19@fidonet @20260906.230250.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→+24s1:320/219→1:229/426→-20s1:229/426→2:292/854→+1h 14m2:292/854
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 1:320/319 | 2026-09-06 23:04 UTC | – | mbfido 1.1.7.2 |
| 2 | 1:320/219 | 2026-09-06 23:04 UTC | +24s | mbfido 1.1.7.2 |
| 3 | 1:229/426 | 2026-09-06 19:04 local | – | D'Bridge 4 |
| 4 | 1:229/426 | 2026-09-06 23:04 UTC | -20s | O/T-Track+ 2.85 |
| 5 | 2:292/854 | 2026-09-07 01:16 local | – | D'Bridge 4 |
| 6 | 2:292/854 | 2026-09-07 00:18 UTC | +1h 14m | O/T-Track+ 2.85 |
Raw Via lines
1:320/319@fidonet @20260906.230428.UTC mbfido 1.1.7.2 1:320/219@fidonet @20260906.230452.UTC mbfido 1.1.7.2 1:229/426 @20260906.190432 D'Bridge 4 1:229/426@fidonet @20260906.230432.UTC O/T-Track+ 2.85 2:292/854 @20260907.011611 D'Bridge 4 2:292/854@Ward_Dossche @20260907.001859.UTC O/T-Track+ 2.85
Evidence
Replies
Every netmail that came back about a ping to 1:1/119, newest first, as the sending node received it. Pongs and transit notices are matched to the ping they answer.
2026-09-06 23:19 UTC
pong Re: Your PING Request
From Ping service, 1:1/119 · answers 2:5001/100@fidonet 6a9dee0d
Path quoted in this reply
2:5020/715→2:292/854→+1h 4m2:292/854→1:229/426→-1h 0m1:229/426→+9m1:1/19
This reply's own Via lines
- 1:320/319@fidonet @20260906.230428.UTC mbfido 1.1.7.2
- 1:320/219@fidonet @20260906.230452.UTC mbfido 1.1.7.2
- 1:229/426 @20260906.190432 D'Bridge 4
- 1:229/426@fidonet @20260906.230432.UTC O/T-Track+ 2.85
- 2:292/854 @20260907.011611 D'Bridge 4
- 2:292/854@Ward_Dossche @20260907.001859.UTC O/T-Track+ 2.85
Software
MBSE-FIDO 1.1.7.2 (Linux-x86_64) --- MBSE BBS v1.1.7.2 (Linux-x86_64)
2026-09-06 23:14 UTC
trace Re: Your PING Request
From Ping TRACE service, 1:320/219 · answers 2:5001/100@fidonet 6a9dee0d
Path quoted in this reply
2:5020/715→2:292/854→+1h 4m2:292/854→1:229/426→-1h 0m1:229/426
This reply's own Via lines
- 1:320/219@fidonet @20260906.230250.UTC mbfido 1.1.7.2
- 1:229/426 @20260906.190255 D'Bridge 4
- 1:229/426@fidonet @20260906.230255.UTC O/T-Track+ 2.85
- 2:292/854 @20260907.010614 D'Bridge 4
- 2:292/854@Ward_Dossche @20260907.000859.UTC O/T-Track+ 2.85
Software
MBSE-FIDO 1.1.7.2 (Linux-x86_64) ---