ah yes, the good old "responds to pings but where is it?"
In some sense, traceroute does often give you some location information.
However, if you're talking about GPS or other geolocation information, even now if a machine supports IPv4 and/or IPv6 and isn't a phone, it likely doesn't know any geolocation information about itself. No provision for geolocation information was provided in the ICMP echo or echo response packets.
It was a silly hack that turned out to be clever and incredibly useful.
"[USSC logo] APPLICATION BLOCKED
You have attempted to access a blocked website. Access to this website has been blocked for operational reasons by the DOD Enterprise-Level Protection System.
APPLICATION: qos-mission-critical-pan"
Took us an afternoon trying to find out their origin and make sure they weren't malicious but in the end they were just eating watts.
It was happily chugging away, running our shitty phone system, and hadn't been restarted in 10+ years.
Edit: This also happened to me at a utility company I worked at. We had a server that ran some critical calculations for us but nobody could recall where it was physically located. It's way worse now that everything's virtualized - the cruft just sits there for years until you suddenly run out of resources and start looking closely.