Meaning of ripe-atlas probe log file message: mismatch for paris

RIPE Atlas
1

Random question.

I have a software probe located in Netherlands, running for nearly a month now. The probe is IPV4 only (my ISP doesn’t do IPV6).

Seeing a bunch of lines in my Probe log including the text ‘mismatch for paris’.
Seeing nearly 40 variants of this message.
Below a few examples

ripe-atlas-1  | ready_callback4: mismatch for paris, got 0x1fc6, expected 0x1 (79.135.106.48)
ripe-atlas-1  | ready_callback4: mismatch for paris, got 0x849a, expected 0x1 (104.234.31.4)
ripe-atlas-1  | ready_callback4: mismatch for paris, got 0xe006, expected 0x1 (45.157.175.37)
ripe-atlas-1  | ready_callback4: mismatch for paris, got 0x7ac3, expected 0x1 (185.157.231.49)
ripe-atlas-1  | ready_callback4: mismatch for paris, got 0xc0f6, expected 0x1 (84.54.64.38)
ripe-atlas-1  | ready_callback4: mismatch for paris, got 0xe07b, expected 0x1 (23.133.168.197)
2

Small update.
This is not Paris, Texas - nor is it Paris, France.

Rather refers to an updated version of the command ‘traceroute’.

More info here: https://paris-traceroute.net/

3

Hey, I ran into the same “Mismatch” message while checking my probe logs for Paris recently. From what I gathered, this typically happens when there’s a discrepancy between the expected results from the probe and what it actually receives, which can sometimes be caused by network issues or routing anomalies.

It’s also possible that the probe might be connecting through a different path than expected due to changes in the network or temporary congestion. Sometimes, the issue clears up after a while, but it’s always good to keep an eye on it, especially if you notice it happening frequently.

I would recommend checking the probe’s connectivity and ensuring it’s on the right network. If it continues, it might be worth reporting to RIPE support with the specific details, so they can investigate further.

Anyone else experienced this consistently? Would love to hear if there are any other fixes or insights on this.