Hi Chris, Thanks, we still see issues receiving measurements. I attached a stripped down version of the script we’ve been using for a number of years. The code basically sets up a stream and starts listening, printing all measurements it recieves. It has some threading left (we usually run this for a number of measurements). When starting this script and doing a tcpdump, I see nearly no data at all being received from the Atlas servers. I hope this helps, let me know if you need any additional info. Thanks! -- Teun Vink BIT | teun@bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE On 1 Mar 2022, at 13:03, Chris Amin wrote:

Hi Teun,

I know that my colleagues have been in contact with you but I'm writing here in case others are having the same issue.

There were issues with the service when you sent this original mail, but I can no longer detect them and I understand you are still having the issue. If that's the case could you please send me the cousteau code you are using?

Thanks, Chris

On 23/02/2022 08:34, Teun Vink via ripe-atlas wrote:

...

Hi,

We’re seeing some issues with RIPE Atlas streams using the ripe.atlas.cousteau websocket library. Sockets seem to connect properly, but no data is received. tcpdumps show very little traffic. One of the already running receiver application (monitoring the exact same set of measurements) is receiving data, but any newly started daemon fails to receive data.

Is there an issue on the RIPE Atlas infrastructure?

Thanks,

-- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

Hi Chris, Yes, it seems to work again. https://bit.org/network/d/mmmxK8Gmk/ipv4-packetloss-to-bit?orgId=1&refresh=5s (one of our public tools using RIPE Atlas data) is showing measurements again. Thanks! Teun On 4 Mar 2022, at 13:27, Chris Amin wrote:

Hi Teun,

I found a possible cause of the issue and have deployed a fix. Could you tell me if it (continues to) work?

Regards, Chris

On 01/03/2022 22:35, Teun Vink wrote:

...

Hi Chris,

Thanks, we still see issues receiving measurements. I attached a stripped down version of the script we’ve been using for a number of years. The code basically sets up a stream and starts listening, printing all measurements it recieves. It has some threading left (we usually run this for a number of measurements). When starting this script and doing a tcpdump, I see nearly no data at all being received from the Atlas servers.

I hope this helps, let me know if you need any additional info.

Thanks!