# Traceroute: why does "edst" ping.ripe.net show up? **URL:** \ **Category:** RIPE Atlas\ **Tags:** troubleshooting\ **Created:** [22 October 2025 17:23 UTC](https://forum.ripe.net/t/traceroute-why-does-edst-ping-ripe-net-show-up/1552 "2025-10-22T17:23:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jtheripper](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jtheripper](https://forum.ripe.net/u/jtheripper)\ **Post date:** [22 October 2025 17:23 UTC](https://forum.ripe.net/t/traceroute-why-does-edst-ping-ripe-net-show-up/1552/1 "2025-10-22T17:23:07Z")
Hi, I’ve ran a few traceroutes on RIPE Atlas and for a few of them I get ```json "edst": "193.0.0.4" ``` in some result hop. It’s always that IP address which seems to be `ping.ripe.net`. I’ve never traceroute’d towards `ping.ripe.net` which is why I’m a bit confused to why this shows up. An example is [this](https://atlas.ripe.net/api/v2/measurements/132392034/results/?format=json) traceroute. My best guess would be that the traceroute interferes with some other measurement on the same probe that goes towards `ping.ripe.net`. For example, with one of the basic connectivity checks (see [docs](https://atlas.ripe.net/docs/getting-started/probe-tags#basic-connectivity)). But I’m not sure. I’d appreciate if anybody has an idea. Best, J. ---
**Author:** ![jtheripper](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jtheripper](https://forum.ripe.net/u/jtheripper)\ **Post date:** [23 October 2025 18:57 UTC](https://forum.ripe.net/t/traceroute-why-does-edst-ping-ripe-net-show-up/1552/2 "2025-10-23T18:57:34Z")
I looked a bit more into it and found that there are also other `"edst”` IP addresses, namely `193.0.14.129` which is `k.root-servers.net` and `192.5.5.241` which is `f.root-servers.net`. This would match my guess that these might be results from other measurements that each RIPE Atlas probe runs periodically (at least `k.root-servers.net` is listed in the “Basic connectivity” section of the docs). Still not sure though.