Hello, I have had recently the same problem like Radu described. The probe wasn't connecting with this message since 2025-11-07 09:45:52, so I have taken this probe to different ASN, but it didn't help. Today, after configuring the DNS servers in the original ASN to respond to queries coming from the probe’s temporary network, the probe was finally able to reconnect. It looks like the issue with DNS setting was a problem here. The probe was initially set to use static IP and IPv6 addresses. After changing a few weeks ago to dynamic ones it's still stuck with old DNS server settings. It's really hard to fix the USB issue with the probe using static addresses. The only working way was taking it to the network with working DHCP and/or IPv6 auto-configuration including RDNSS, plugging it without USB, waiting several minutes, plugging USB stick, waiting till it reboots, disconnecting from the network, and connecting back to the network for which static addresses were configured. Of course, if there were DHCP or RDNSS working in the original network, the troubleshooting would be far easier. Anyway, I have two requests for the RIPE Atlas operations team: - please ensure that DNS settings automatically switch to dynamic when changing a probe’s addressing mode from static to dynamic, - please allow users to change a probe’s addressing mode from static to dynamic even when the probe is currently offline. Cheers -- Marek Zarychta