- ripe-atlas - mailman.ripe.net

Globalping
by Ernst J. Oud 27 Aug '24

27 Aug '24

L.S. It might be “cursing in the church” as we say in NL, but does anyone here have experience with the Globalping monitoring tools? Not as comprehensive as Atlas and a lot less probes but at first glance it has some useful features. Your thoughts? Regards, Ernst J. Oud

3 2

Call for presentations for LACNIC's Internet Measurements Working Group (IMWG)
by Elisa 27 Aug '24

27 Aug '24

Hi all, Call for presentations is now open! Seeking presentations on Internet Measurements (including, but not limited to, Atlas). The Internet Measurements Working Group session will be held at the LACNIC42/LACNOG2024 meeting in Asunción, Paraguay, on October 11. Presentations can be remote or in-person. Submission deadline September 20. Instructions: https://listas.nog.lat/archives/list/imwg@listas.nog.lat/thread/VSNIWWLMXGI… Kind regards, -- Elisa Peirano *Analista de Datos I+D* R&D Data Analyst /www.lacnic.net <http://www.lacnic.net> Latin American and Caribbean Internet Addresses Registry/

1 0

Update on RIPE Atlas Service Issues
by Robert Kisteleki 26 Aug '24

26 Aug '24

Dear colleagues, After the mails to this list over the weekend, we just wanted to confirm that we are aware of the issues some of you are having and we are working to resolve them. A service announcement has already been posted, as some of you have already pointed out. We would also like to note that probes will automatically try to re-connect to the RIPE Atlas infrastructure as long as they are operational. This is not something the host can control and so there is no action needed on your part. Currently, we are in the final stages of re-working the probe-controlling parts of the RIPE Atlas infrastructure, and while we’re careful to keep the machinery running, we expect to encounter some hiccups as we complete this work. During this period, there might be additional issues that arise which affect network performance or the connectivity of probes. We will try to keep this list updated, but note that you can always find the status of our services on status.ripe.net, and we encourage you to check if there are known issues. Regards, Robert Kisteleki RIPE NCC

1 0

Disconnected probes…
by Ernst J. Oud 26 Aug '24

26 Aug '24

All, Some of my disconnected probes have connected again, but probe 60200 has not. This is not a network issue since on that router a SW probe (1005072) now connects fine (it was disconnected earlier today) Would restarting probe 60200 help? It is in an inconvenient place but if restarting helps let me know. Regards, Ernst J. Oud

2 1

Probe v3 id #22785 - BADMD-APP
by Cassiano Aquino 26 Aug '24

26 Aug '24

Hi, I have a probe with id #22785 that completed 10 years online last July, but today in the morning it stopped working. I tried the common procedure, remove the USB, which was the same the probe came with, never had major issues with it, restart, wait 10 minutes, put the USB drive back again. Usually this solved any problems I had in the past, but not today, after trying 4 different USB drives, I'm seeing the same error message on the SOS log: BADMD-APP-5080-d41d8cd98f00b204e9800998ecf8427e Is there anything else I can do? Considering that after ten years, this probe is almost part of the family, is there any hope to recover? I have another TP-LINK TL-MR3020 that I bought and almost never used, is it possible somehow to install the firmware on it to have it replacing the current probe? Thanks in advance, and I do understand if there is nothing we can do, but probe #22785, you will be missed! Cheers, Cassiano Aquino - EI5HPB

3 3

Fwd: Your RIPE Atlas Probe (ID: 60200) has reconnected
by Ernst J. Oud 25 Aug '24

25 Aug '24

> We're just letting you know that your probe (#60200 ) has re-established its link to our network and we are again receiving data from it. Good! After over 3 days. Connected to controller ctr-nue17. Not to ctr-dub anymore. Ernst

2 1

Probe v3, problems
by Phillip Remaker 24 Aug '24

24 Aug '24

I tried to replace by failing v2 probe with a v3 probe I had mailed to me from a closed site https://atlas.ripe.net/probes/16058/' The first led is on, second is off, and 3rd is slow-blink, which indicates a "network problem"? I tried a different power supply, replaced the network cable, tried other ports and even put in a new power supply, all with no change. The DHCP server does not see it. Any other suggestions?

1 1

Disconnected #27262
by Victor TALVAZ 24 Aug '24

24 Aug '24

Hi everyone, It seems that I've been totally disconnected for 2 hours, 8 minutes, is the controller ctrl-dub-hw01 alive ? Probe #27262. Thanks, Regards, *Victor TALVAZ*

3 2

Another probe disconnected
by Ernst J. Oud 23 Aug '24

23 Aug '24

Hi, And just now probe 1004467 also has been disconnected. What is going on? Regards, Ernst J. Oud

6 9

Re: Auto reconnect?
by Ernst J. Oud 23 Aug '24

23 Aug '24

Ok. Hope so. But it is weird that probes try to connect to a controller that clearly is not responding. I have six probes, 5 work fine, 1 is now disconnected for 34 hours. If it would connect to the controller it always used to connect to - ctr-nue14- all would be well but it appears it persists to connect to a non functioning controller, probably ctr-dub-hw01. Or something else is going awry in fail over between controllers perhaps? I know this is a free non-critical service but the lack of communication here wonders me a bit. Especially since the downtime is longer than ever before. Ernst > On 23 Aug 2024, at 17:56, Nick Hilliard (INEX) <nick(a)inex.ie> wrote: > > Ernst J. Oud wrote on 23/08/2024 16:54: >> Do we need to take actions to have disconnected probes reconnect “over the weekend”? Or is a reconnect in this case automatically? > probes automatically reconnect, as far as I'm aware. > > Nick

1 0