- ripe-atlas - mailman.ripe.net

Probes were incorrectly not tagged with the stability tags
by Chris Amin 21 Feb '20

21 Feb '20

Dear colleagues, Over the past month there have been issues with the "system-ipv[45]-stable-{1,30,90}d" tags, which were not applied to many of the probes that should have had them. This was caused by accidental data format changes from a backend migration. The issue should now be fixed, so probes will have the correct tags applied. If you notice any persisting issues then please let us know! Apologies for any inconvenience. Kind regards, Chris

2 2

atlas probe down
by MAYER Hans 19 Feb '20

19 Feb '20

Dear All, Our Atlas probe with ID 35603 is down since Wednesday exactly 12:00 LT. I unplugged power and powered on, but no success. After power on some LED's are blinking. Finally the power LED stays on and the LED next to it is blinking. But I can't ping this probe. Either on IPv4 nor on IPv6. We got this probe in summer 2018. So I can't believe it's EOL. Any ideas what I can do ? Kind regards Hans --

2 2

Can I issue a traceroute measurement with multiple targets?
by Vasileios Giotsas 11 Feb '20

11 Feb '20

If I have 100 IPs to target from a single probe, is it possible to create a single measurement with 100 targets similar to how I'd do if I wanted to target a single IP from 100 probes? I've read through the Atlas API documentation and couldn't find anything like that but it looks like some of the built-in measurements do that. Thanks, Vasilis

2 2

Atlas API stream broken?
by Teun Vink 10 Feb '20

10 Feb '20

Hi, Since ~13.30h CET this afternoon our Atlas data stream subscriptions (using the ripe.atlas.cousteau python library) stopped receiving updates. Earlier today we (at 11.27h) observed some issues with the backend where we received redis errors, which were resolved at ~12.09h CET. I heard these were related to some firewall issues, could these problem be related? Regards, -- Teun Vink BIT | teun(a)bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE

2 1

Graphs and measurements are scaled by a factor of 1000
by Enrico Ardizzoni 07 Feb '20

07 Feb '20

Starting from 06/02/2020 at 6.00 AM UTC all graphs and measurements are scaled by a factor of 1000. Something went wrong on probes backend... "An error occurred while retrieving measurement data. We apologise and do our best to fix it asap!" See: https://atlas.ripe.net/probes/249/#!tab-builtins https://atlas.ripe.net/probes/12120/#!tab-builtins E. -- | ENRICO ARDIZZONI | Responsabile Ufficio Reti e Sistemi | Università degli Studi di Ferrara

2 3

Planned Atlas downtime on 29 January
by Robert Kisteleki 06 Feb '20

06 Feb '20

Dear RIPE Atlas users, Please be aware that we plan to do maintenance work in the RIPE Atlas core infrastructure two weeks from now, on Wednesday 29 January, between 9:00-12:00 CET (Amsterdam time). The RIPE Atlas website, UI and API will be unavailable in this period. The probes should remain connected and results will be collected normally, although during this period they can only be accessed real-time via the streaming service. Apologies for the inconvenience this may cause. Regards, Robert Kisteleki

2 3

Using Atlas for Monitoring of Anycast DNS
by Klaus Darilion 20 Jan '20

20 Jan '20

Hello! I want to restart this old thread and ask for available tools. For our Anycast DNS cloud, I want to measure the "performance", ie the RTT from Atlas probes. 1. Create measurements (I can do that already ;-) 2. Analyze this measurements: - fetch measurement - analyze the probe locations (ie. country, continent) - create reports with average RTT from certain countries and continents This second step I have partly in old scripts using influxdb and grafana dashboard - but that was a proof of concept with bad code. So, before starting coding from the base - are there some available scripts which can do the second part? Is https://github.com/RIPE-NCC/ripe.atlas.sagan still the way to go for measurement processing or are there meanwhile some better/smarter libraries? ie something for php? Thanks Klaus Am 20.11.2014 um 16:32 schrieb Klaus Darilion: > Hi! > > I want to monitor an Anycasted authoritative name server: > - are all nodes responding > - are all nodes in routing > ... > > > So I thought about starting a long term DNS measurement with plenty of > probes and NSID queried. Then, checking the results I should see every > possible NSID if there are for more probes than Anycast-nodes. > > Does anybody have done that (or similar) already and want to share code? > > Can the RIPE Atlas Status Checks be used for such monitoring? > > Thanks > Klaus >

4 4

Probe is offline but shown online
by Andre Heinrichs 19 Jan '20

19 Jan '20

I’ve just discovered my probe #29384 blinking frantically while the website claims it had been online for more than a day (which can’t be true as my DSL had to get a new connection with a different IP). I tried rebooting the probe but all that got me is lower values of Power-Up time in the SOS requests the probe sends every couple of minutes. From what I can guess it looks like something in RIPE ATLAS isn’t working right. Would be great if someone could have a look. TIA, Andre, Who’s trying to get some sleep now.

3 2

Probe stability tags
by Chris Amin 08 Jan '20

08 Jan '20

Dear RIPE Atlas users, Due to an error in our backend systems, the probe stability tags ("system: IPv4 Stable 30d" etc) had been gradually becoming stale over the past three months, meaning that probes were not gaining or losing these tags when they should. This has now been fixed, so probes are once again tagged appropriately. We have improved our internal monitoring so this kind of issue will be noticed more quickly next time. Apologies for any inconvenience caused. Kind regards, Chris Amin RIPE NCC

1 0

New RIPE Atlas Terms&Conditions
by Robert Kisteleki 08 Jan '20

08 Jan '20

Dear RIPE Atlas users, We'd like to inform you that a new version of the RIPE Atlas Terms & Conditions has just been published. Most changes in this version are needed for the introduction of "software probes". The new version (3.4) is available at https://atlas.ripe.net/legal/terms-conditions/ and will be effective as of 11 February 2020. Regards, Robert Kisteleki

1 0

Maintenance or incident?
by Stephane Bortzmeyer 07 Jan '20

07 Jan '20

% curl https://atlas.ripe.net/ curl: (7) Failed to connect to atlas.ripe.net port 443: Connection refused It started around 1015 UTC.

4 4

A new year's break for the probes
by Robert Kisteleki 03 Jan '20

03 Jan '20

Happy new year to all RIPE Atlas users! It seems we've given a little break to our probes so they can celebrate the new year too ... >From midnight 1 January until approximately noon 2 January there were no built-in measurements running. This is due to an overlooked fact where the built-in measurements had a pre-defined end date of 2020-01-01. The system dutifully observed this date and did not schedule these measurements any more. We fixed this setting on Thursday, 2 January and the system returned to normal operations shortly thereafter. As a consequence, there's a gap in the delivered measurement results for built-in measurements (i.e. IDs < 1 million). Results for the User-Defined Measurements were not affected. Please accept our apologies for the inconvenience this can cause. Regards, Robert Kisteleki

2 2

One-off measurements not terminating
by Steve Gibbard 30 Dec '19

30 Dec '19

Hi Atlas folks, I hope you’re having a good holiday season. Sorry to interrupt it by complaining about issues. On Christmas Eve my time (early Christmas morning your time) there was an Atlas issue where any attempt at reading measurements failed with an HTTP 500 status error. That appears to have gotten fixed on Christmas (a really big thank you to whoever worked on that) but since then it appears that while most of the one-off measurements we’ve created have delivered results very quickly, none of the measurements created since 17:00 UTC on 2019-12-25 have stopped running. As shown in the Atlas portal: 23722197 Traceroute www.globaltraceroute.com (AS13335) Test Traceroute 1 one-off 2019-12-25 22:24 Never 23722089 Traceroute archive.ubuntu.com (AS41231) Test Traceroute 1 one-off 2019-12-25 19:16 Never 23722088 Traceroute sps.prima.com.ar (AS10318) Test Traceroute 1 one-off 2019-12-25 19:14 Never 23721915 Traceroute www.globaltraceroute.com (AS13335) Test Traceroute 1 one-off 2019-12-25 17:00 Never And on for every measurement between then and now. Previously, the typical one-off measurement was listed with start and stop times less than 10 minutes apart. When a user has 100 measurements running concurrently, creation of new measurements fails, which is happening for me now. If somebody could take a look at this, I’d really appreciate it. Thanks, Steve

2 3

Deletion of erroneously scheduled measurements
by Nils Rodday 29 Dec '19

29 Dec '19

Dear Atlas folks, I have accidentially scheduled many faulty measurements via the API and am now looking for a way to remove them in order to minimize unnecessary burden on the Atlas system and not to pollute my account & limits with unnecessary measurements. However, the DELETE statement (AtlasStopRequest) only seems to be able to stop ongoing measurements [1]. I always get the following reply trying to remove any future measurement: {'error': {'detail': 'That measurement cannot be stopped', 'status': 400, 'title': 'Bad Request', 'code': 104}} Also, the AtlasChangeSource & AtlasChangeRequest of Cousteau [2] can only change ongoing experiments (as I wanted to set the probes in each measurement to 1 if I wasn´t allowed to delete any of them). But since they are upcoming, but not ongoing, I could also not alter them. I am also referring to a mailing-list post from October 2013 stating essentially the same problem [3]. Given the significant amount of time that has passed since then I wanted to raise this issue again. Is there any way to delete a measurement that is in the "SPECIFIED" state, which means that it will only be executed in the future? I understand that we might want to avoid deletion of measurements that have already been run in the past in order to allow others to benefit from the results, but why shouldn´t one be allowed to eliminate faulty measurements that have been scheduled by accident in the future? Thanks & a Happy New Year! Kind regards, Nils [1] https://atlas.ripe.net/docs/api/v2/manual/measurements/stop-measurements.ht… [2] https://ripe-atlas-cousteau.readthedocs.io/en/latest/use.html [3] https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-October/001058.html

1 0

measurement page broken?
by Dave . 16 Dec '19

16 Dec '19

Hi, I just started 2 measurements like 10 minutes ago but it does seem something broke. https://atlas.ripe.net/measurements/23631307/#!probes Same issue here: https://atlas.ripe.net/measurements/23631303/#!probes I get to see a spinner instead of the results. Thanks, Dave

2 5

Letsencrypt certificates on anchors
by Anand Buddhdev 13 Dec '19

13 Dec '19

Dear colleagues, Some time ago, there was discussion on this list about deploying Letsencrypt certificates on anchors. We had said we would investigate the possibility of doing this. We are pleased to report that we have worked out how to do this seamlessly. Early next week, all RIPE Atlas anchors will switch to Letsencrypt certificates. Note that we will re-use the existing keys on the anchors to request the Letsencrypt certificates. The TLSA records of all anchors are pinned to these private keys, and so they will not change. Regards, Anand Buddhdev RIPE NCC

3 2

Anchor VM security
by Rami Al-Dalky 12 Dec '19

12 Dec '19

Hi, If someone is planning to host a VM anchor, what are the security measures that RIPE Atlas can provide? For example, protecting the VM from being compromised by an attacker. Any information about this is highly appreciated because the plan is host several anchors. Thanks, Rami

2 1

Probes connected to 4G/LTE
by Ponikierski, Grzegorz 06 Dec '19

06 Dec '19

Hi all! I'm thinking about becoming ambassador to deploy more probes in Poland including rural areas where sometimes the only option to get access to the Internet is 4G/LTE. I'm interested what is your experience with 4G/LTE and Atlas probes. What tags you use to mark them? How stable they are? What RTT you see to first and second hop? Regards, Grzegorz

3 2

Long measurement delays
by Steve Gibbard 30 Nov '19

30 Nov '19

Hello, Atlas crew, I’ve been seeing delayed query responses to one-off measurements since November 22, with the exception of November 25. For www.globaltraceroute.com, which attempts to get responses for 90 seconds after submitting a query (and is usually fairly successful), this has meant a failure rate of 61% on average for those days, and as high as 83% on one of the days. I haven’t been tracking how long it does take for a response to come in in those cases, but my most recent test measurement, measurement ID 23502037, is still not returning any data an hour and 40 minutes after submission. My request format as a Python string is "https://atlas.ripe.net/api/v2/measurements/%s/latest/?key=%s" % (measurement_id, key). For these failures I’m receiving an empty list, so it looks like this might be something different than the “synchronizing” issue people were complaining about over the last few weeks. Trying to access that measurement via the Atlas Web UI, if I go to the “latest results” tab I get a spinning progress wheel, seemingly forever. I haven’t been tracking the Atlas “consumption delay” along with the results, so I’m not sure what it’s looked like during most of the failure periods. I checked at the time I submitted measurement 23502037 and it showed as green, although it’s showing as yellow now. Thanks for any help or attention you can provide on this. -Steve

3 2

Measurements "synchronizing"
by Stephane Bortzmeyer 30 Nov '19

30 Nov '19

It seems that, today, when querying the API about an existing measurement, I always get: {'id': None, 'name': 'synchronizing'} Which I've never seen. (Measurement #23238335 but it's not the only one.) A recent change? A temporay problem?

2 5

swagger spec 2.0
by av＠ipmn.io 30 Nov '19

30 Nov '19

Hi, I can't write to the previous post about swagger, so created the new one. I made some tooling auto conversion from 1.2 to 2.0 and a little bit of hand fixing to current spec. It would be nice if anybody could help with getting 2.0 version up to date. Here is what I have for now: https://app.swaggerhub.com/apis/akme/ripe-atlas_api_reference/v2.4.0

1 0

Unable to set probe location to Hong Kong
by Ponikierski, Grzegorz 28 Nov '19

28 Nov '19

Hi all! I was wondering why I see more probes in Hong Kong marked as Chinese probes. For test, I tried to set location of my probe to Hong Kong and even if I put location pin on map in the middle of Hong Kong it still ends assigned to China. Are we still able to assign RIPE Atlas probes to Hong Kong? If not, then what about probes which are still assigned to Hong Kong? How to reliably get via API list of probes located in Hong Kong? Should we parse geo coordinates and use 3rd party libraries to figure out where probe is really located? Regards, Grzegorz

2 2

Finding the NSID in the measurement results
by Roger Murray 28 Nov '19

28 Nov '19

Dear colleagues, We have a measurement with the NSID flag set to True: https://atlas.ripe.net/measurements/23444279/#!general and we are seeing the NSID responses in the web-gui for the measurement: https://atlas.ripe.net/measurements/23444279/#!probes So far so good, but when we download the raw measurement result data we are not able to locate the NSID information. We would really appreciate any help in finding the NSID in the result information. Thanks in advance, /rog The Swedish Internet Foundation https://internetstiftelsen.se/en/

2 1

Fwd: Probe 2317 is disconnected (home fibre)
by Colin Johnston 14 Nov '19

14 Nov '19

Any idea why went disconnected today, I think came back ok though AS connectivity was ok whilst probe said down though.. Any chance of enhancement to send email once connected again ? Connected (UTC) Connected for Disconnected (UTC) Disconnected for 2019-11-14 12:43:47 2h 13m Still Connected 2019-11-14 12:33:17 0h 0m 2019-11-14 12:33:49 0h 9m 2019-11-14 02:50:45 8h 49m 2019-11-14 11:39:46 0h 53m 2019-11-08 16:42:22 5d 9h 45m 2019-11-14 02:28:01 0h 22m 2019-11-08 13:19:26 3h 15m 2019-11-08 16:34:53 0h 7m 2019-11-05 12:32:57 2d 7h 34m 2019-11-07 20:07:40 17h 11m 2019-10-15 14:58:43 20d 21h 25m 2019-11-05 12:24:08 0h 8m > Begin forwarded message: > > From: RIPE Atlas (no reply) <no-reply(a)ripe.net> > Subject: Probe 2317 is disconnected (home fibre) > Date: 14 November 2019 at 12:00:01 GMT > To: colinj(a)mx5.org.uk > Reply-To: RIPE Atlas (no reply) <no-reply(a)ripe.net> > > Dear colin johnston, > > Your probe 2317 has been disconnected from the RIPE Atlas infrastructure since 2019-11-14 11:39:46 UTC. > > You may be able to learn more about the possible cause from the "Status" tab on your probe's information page: > > https://atlas.ripe.net/probes/2317/#!tab-status > > Probes are tagged with suspected problems every four hours, so if there is nothing listed under the Status tab and your probe has just gone offline, please check back in a few hours, as more information may be available. > > If you need further assistance or have any questions, please contact us at atlas(a)ripe.net. > > Kind regards, > > RIPE Atlas Team > > ********** > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 10 minutes. If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/, and click the "edit" button under "Notifications".

2 1

Request: RIPE Atlas Credits for Lab Course
by Trinh Viet Doan 11 Nov '19

11 Nov '19

Hello everyone, I am a PhD student at TUM and would require around 200M credits to perform large-scale measurements for a lab course that we are running with our master students (http://www.cm.in.tum.de/teaching/2019-imarl/ <http://www.cm.in.tum.de/teaching/2019-imarl/>). If you have any credits to share, we would greatly appreciate it! :) Thanks in advance and best regards, Viet

7 9