This is an unexpected effect of time:
PING CRITICAL – Packet loss = -400%, RTA = 1029419237376.00 ms
The absurd Round-Trip Average (RTA)
1029419237376.00 milliseconds ~ 32.64 years.
This happened because the system time went backwards during the ping test.
It works by sending a small data packet (an ICMP echo request) and waiting for a reply, while stamping the “send time” and “receive time” using the system clock.
If the clock suddenly jumps back, the “receive time” can appear to be earlier than the “send time.”
This creates a negative round-trip time, which is interpreted as a large number because the system stores the value as an “unsigned” (only positive) integer; a small negative value is displayed as a large positive number.
But why did packet loss become -400%?
Packet loss is calculated as a percentage of packets that were expected but never received. The formula is something like:Packet Loss % = ((Packets Sent - Packets Received) / Packets Sent) * 100
A negative packet loss means the system believes it received more packets than it sent. But how could that happen?
When the system clock moves backwards, the ping tool’s internal accounting gets confused. It can miscount the replies, often because duplicate replies are suddenly counted as new, separate packets. If it sent 5 packets but, due to the glitch, counted 25 replies, the math becomes: ((5 - 25) / 5) * 100 = -400 (%).
Challenge
Can you determine the time shift that occurred while the check was running, and what are the odds that the system time changes backwards during the time interval between an echo request and echo reply?
Non-technical explanation
Imagine you’re timing a race with a stopwatch. You click ‘start’ when the runner leaves, but the clock fails and resets to midnight; when the runner finishes, after you click ‘stop’, the watch shows a negative time. If the stopwatch wasn’t designed to display negative numbers, it will display a huge, meaningless number instead.