- ripe-atlas - mailman.ripe.net

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

RIPE Atlas API Swagger 2.0
by av＠ipmn.io 04 Nov '19

04 Nov '19

Hey guys, Are there any plans to migrate API spec from swagger 1.2 to 2.0? It will let us use more modern code generators...

2 1

Looking for Atlas credits
by av＠ipmn.io 28 Oct '19

28 Oct '19

6 6

Latest data point shown is from 2019-08-15 07:05 UTC
by Randy Bush 28 Oct '19

28 Oct '19

why do a number of my probes, e.g. 4959 and 4981, show all the built-ins as Latest data point shown is from 2019-08-15 07:05 UTC or whatever? randy

1 0

Looking for RIPE Atlas credits
by Nils Rodday 25 Oct '19

25 Oct '19

Dear RIPE Atlas users, I am a PhD-student and would need RIPE Atlas credits in order to perform large-scale traceroute experiments. If you have credits to share, I would appreciate it. Recipient: nils.rodday(a)unibw.de Thanks. :) Kind regards, Nils

5 4

Credits for Research
by r.sommese＠utwente.nl 24 Oct '19

24 Oct '19

Dear All, I am Raffaele Sommese, a PhD student at University of Twente. I am running out of credit for my experiment and I need other 20 Million credit. Can anyone help me? My account is: r.sommese(a)utwente.nl Thanks, Raffaele Sommese

4 3

Error: No suitable probes and delayed results
by Moritz Muller 03 Oct '19

03 Oct '19

Hi, In our experiment we’re trying to assign certain probes to a ping measurement but until now we always get the error message "NO SUITABLE PROBES”. According to the documentation, this is a sign that a probe might not have enough resources. However, when I check on the measurement a few hours later I do see results, but its state is still "NO SUITABLE PROBES”. See https://atlas.ripe.net/measurements/23016956/#!probes Is that a common problem when selecting certain probes for measurements? Moritz

2 2

Re: [atlas] credits not getting updated com243.249.483
by kiran.gunana＠colruytgroup.com 30 Sep '19

30 Sep '19

Hello Robert, Thanks alot for the quick help robert !! Probe ID : 32256, Also check the attachement for the image of probe in our possession. rg, kiran. ----- Original Message: com243.247.331 --------------------------------- From: Robert Kisteleki (robert(a)ripe.net) To: kiran.gunana(a)colruytgroup.com, ripe-atlas(a)ripe.net Subject: Re: [atlas] credits not getting updated com243.209.765 Date: 30 September 2019 (12:00) Hi, We don't have problems with crediting/debiting in general. Please send me details (probe ID, since when you think you have the issue) in private so I can check. Regards, Robert On 2019-09-30 08:15, kiran.gunana(a)colruytgroup.com wrote: > Hello Ripe, > > Probe which I am using is up and running since more than few months, > however I dont see any credits being added up, I am afraid I would loose > all my credits and will end up with no monitoring for the services I am > depended on. > > Can you please do the needfull asap ? > > Thanks & Regards, > Kiran Gunana > > > > > / > > Dit bericht is onderworpen aan de voorwaarden beschikbaar op _onze > website <http://www.colruytgroup.com/nl/algemene-voorwaarden>_ > > Ce message est soumis aux conditions disponibles sur _notre site web > <http://www.colruytgroup.com/fr/conditions-g%C3%A9n%C3%A9rales>_ > > This message is subject to the terms and conditions available on _our > website <http://www.colruytgroup.com/en/terms-use>_ > > / Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

credits not getting updated com243.209.765
by kiran.gunana＠colruytgroup.com 30 Sep '19

30 Sep '19

Hello Ripe, Probe which I am using is up and running since more than few months, however I dont see any credits being added up, I am afraid I would loose all my credits and will end up with no monitoring for the services I am depended on. Can you please do the needfull asap ? Thanks & Regards, Kiran Gunana Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

2 1

Re: [atlas] Requesting RIPE ATLAS credits for research
by Ponikierski, Grzegorz 30 Sep '19

30 Sep '19

I sent you some more so you can use more than just pings (traceroutes are expensive). When you finish don't forget to publish results on RIPE Labs :D Regards, Grzegorz From: "Mohan, Nitinder" <nitinder.mohan(a)helsinki.fi> Date: Thursday 2019-09-26 at 14:59 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Requesting RIPE ATLAS credits for research Dear all, Greetings from Finland! I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). My RIPE NCC account is <nitinder.mohan at helsinki.fi>. Any help would be highly appreciated. Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki https://www.nitindermohan.com/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.nitindermohan.com_…>

1 0

Requesting RIPE ATLAS credits for research
by Mohan, Nitinder 28 Sep '19

28 Sep '19

Dear all, Greetings from Finland! I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). My RIPE NCC account is <nitinder.mohan at helsinki.fi>. Any help would be highly appreciated. Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki <http://www.cs.helsinki.fi/u/nmohan/>https://www.nitindermohan.com/

11 11

Software probes ?
by Toussaint OTTAVI 27 Sep '19

27 Sep '19

Hi, I just saw a survey last June about software probes. I would be greatly interested by them. Can we have some news about this project ? I know I can deploy software anchors. But I'm on a tiny island. I have very few bandwidth, and it's very expensive; then I can't afford spending too much of it :-) Kind regards, -- *Toussaint OTTAVI* *MEDI INFORMATIQUE* Tel : 04 95 20 10 03 GSM : 06 10 28 41 72 Email : t.ottavi(a)medi.fr

3 4

Re: [atlas] Requesting RIPE ATLAS credits for research
by James Gannon 26 Sep '19

26 Sep '19

Sent you a million, have fun! From: ripe-atlas <ripe-atlas-bounces(a)ripe.net> on behalf of "Mohan, Nitinder" <nitinder.mohan(a)helsinki.fi> Date: Thursday, 26 September 2019 at 08:59 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Requesting RIPE ATLAS credits for research Dear all, Greetings from Finland! I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). My RIPE NCC account is <nitinder.mohan at helsinki.fi>. Any help would be highly appreciated. Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki https://www.nitindermohan.com/

1 0

User Tags missing [ProbeTag object]
by ripe＠brite.cz 18 Sep '19

18 Sep '19

Hi team, all User Tags on all probes I checked are showing string "ProbeTag object" only. Please have a look. Thank you Jiri

5 7

DNS issue with Atlas or with the ISP?
by Stephane Bortzmeyer 09 Sep '19

09 Sep '19

RIPE Atlas Web site displays a lot of "undefined" for the tests in AS 3125. See for instance <https://atlas.ripe.net/measurements/22766270/#!probes> or <https://atlas.ripe.net/measurements/22766942/#!probes> But the DNS resolution from this AS seems to work. Checking the raw results in JSON, I see that we have a lot of failures on one IPv6 resolver: "dst_name": "fe80::a63e:51ff:fe77:e26", "error": { "socket": "connect failed Invalid argument" }, We do not see such IPv6 problem in other AS (see for instance <https://atlas.ripe.net/measurements/22766995#!probes>) I assume that the "connect failed Invalid argument" is the fault of the ISP, which advertises a wrong DNS resolver? Or is the Atlas probe unable to query link-local addresses for DNS resolution? Even if it is so, is it a good idea for the Atlas Web site to display "undefined" where the raw results show that other resolvers worked?

3 5

SSL Certificates for ripe anchors
by Jóhann B. Guðmundsson 04 Sep '19

04 Sep '19

Hi Has there been any dialog about moving the anchors away from using self signed certificates to Let's Encrypt? Regards Jóhann B.

14 32

Apply for next RIPE NCC hackathons, in six locations!
by Vesna Manojlovic 04 Sep '19

04 Sep '19

Dear colleagues, as our tenth event, we are hosting our first IoT-themed hackathon (Internet of Things) on the weekend of 12-13 October in Rotterdam: https://labs.ripe.net/Members/becha/iot-hackathon-at-ripe-79-in-rotterdam This is planned for the weekend just before RIPE 79: http://ripe79.ripe.net You can apply at: https://www.ripe.net/participate/forms/apply/iot-hackathon-rotterdam-2019/ The application deadline is *9 September 2019*. Shortly after that, for the first time ever, we are holding the hackathon simultaneously in five connected 'nodes' across Europe: Delft, Dublin, Padua, Paris and Sarajevo! Topic is Quantum Internet, and dates 5 & 6 November. The first application deadline is *15 September 2019*. This will probably be extended due to the summer & academic holidays. You can find more information about the event on RIPE Labs: https://labs.ripe.net/Members/ulka_athale_1/take-part-in-pan-european-quant… You can apply at: https://www.ripe.net/participate/forms/apply/peqi/ Warm regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

Measurement with msm probe type isn't working
by Hugo Salgado 02 Sep '19

02 Sep '19

Dear Atlas team. I have a script to launch a new measurement using an old measurement list of probes ids, using type:msm. This script worked ok several times (last time like 1 month ago), but now it gives me the error: {"error":{"detail":"There was a problem with your request","status":400,"title":"Bad Request","code":102,"errors":[{"source":{"pointer":"/probes/0/value"},"detail":"The measurement you selected for your probe request does not exist"}]}} However I still can see the old measurement on the web page! I solved it downloading the list of probes using a GET to https://atlas.ripe.net/api/v2/measurements//<OLD_MEASUREMENT_ID>?fields=probes' and then giving the complete probes list to my script. Is there any recent change with the type:msm call? Thanks, Hugo

2 2

"Anchor Details" on the probe pages
by Alexey Troshchanovich 30 Aug '19

30 Aug '19

Hello team, Is it normal that the probe pages contain an empty "Anchor Details" section? <section id="anchor-measurements" class="anchor_measurements"> > <h4 class="wide">Anchor Details</h4> > ... > </section> > Thank you. Alexey

2 1

Network name missing at http://sg-pub.ripe.net/petros/population_coverage/country.html?name=CZ
by ripe＠brite.cz 01 Aug '19

01 Aug '19

Hi team, RIPE Atlas Population Coverage tool ( http://sg-pub.ripe.net/petros/population_coverage/country.html?name=CZ ) is missing Network Names (column "Network Name") in more than half rows. It seems it is the same for multiple/all countries. Please have a look. Thank you Jiri

2 1

Feature Request to consider: DNS response IP header
by Jen Linkova 22 Jul '19

22 Jul '19

Hello, I have a number of use cases when it would be very useful to have access to the IP header of the measurement response packets. In my scenario I'd like to see TTL/Hop Limit of packets received in DNS measurements. So I'm curious if anyone else think it would be a useful feature and if there is some demand for such a feature - maybe the Atlas team could consider implementing it? Thanks! -- SY, Jen Linkova aka Furry

4 4

Question about built-in first/second hop latency measurements
by Joel Sommers 22 Jul '19

22 Jul '19

Hello all, For the built-in latency measurements to first/second hops, my assumption has pretty much always been that these are done with hop-limited probes (i.e., with TTL or hop limit set to 1 or 2). Is that true, or are these measurements taken using “direct” pings? Thanks! Joel

2 1

Scheduled work on RIPE Atlas
by Robert Kisteleki 18 Jul '19

18 Jul '19

Dear RIPE Atlas users, We have planned maintenance on the main RIPE Atlas backend database tomorrow (Tuesday, 16 July) starting at 08:00 UTC, 10:00 Amsterdam local time. We expect complete unavailability of the service for a short while and further intermittent delays during the day. During this time the website (UI and APIs) will not be responding (properly). This also means that requests for new measurements will be denied or delayed. Data from existing measurements will still be collected normally, though access to them will be impacted. Our apologies for the inconvenience. Regards, Robert Kisteleki

3 4

Re: [atlas] how to earn credits com236.294.813
by kiran.gunana＠colruytgroup.com 11 Jul '19

11 Jul '19

Hello Johan, My probe ID is 32256, It is registered and reachable from last 3 weeks, can you please check if I still need to do something to earn my credits. rg, kiran. ----- Original Message: com236.291.250 --------------------------------- From: Johan ter Beest (jterbeest(a)ripe.net) To: kiran.gunana(a)colruytgroup.com Copy: ripe-atlas(a)ripe.net Subject: Re: [atlas] how to earn credits com236.259.148 Date: 11 July 2019 (12:07) Hi Kiran, You earn credits for the uptime of a probe and the delivered results for measurements that other hosts run towards your probe. Everything is explained here: https://atlas.ripe.net/docs/credits/ If your probe is not earning you any credits then there are two possible reasons: - your probe is not connected - you have not registered your probe so we don’t know who to give the credits to. I don’t know your probe ID so I. Cannot check but it’s most likely that it’s not registered. You can do that here: https://atlas.ripe.net/register/ If you send me a private email with your probe ID, I will give you the credits you should have earned in the last three weeks. Kind regards, Johan ter Beest RIPE Atlas. Team On 11 Jul 2019, at 09:10, kiran.gunana(a)colruytgroup.com wrote: Hello Michael, Thanks alot for the good gesture, me too got some good number of credits for now however just wondering after 3 months I will loose them all if I keep doing the same measurments. So looking for a way to earn some credits. rg, kiran ----- Original Message: com236.253.880 --------------------------------- From: Michael J. Oghia (mike.oghia(a)gmail.com) To: kiran.gunana(a)colruytgroup.com Copy: ripe-atlas(a)ripe.net Subject: Re: [atlas] how to earn credits com236.252.126 Date: 11 July 2019 (08:34) Can we just transfer you some credits? Most of us have a massive surplus. Let us know your preferred email address. Best, -Michael On Thu, Jul 11, 2019, 8:16 AM <kiran.gunana(a)colruytgroup.com> wrote: Hello, I am running my probe since 3 weeks and I spent almost 1milion credits for measuring some metrics, however I am not able to earn any credits. Can some give me the steps to enable me earning some credits as well. rg, kiran. Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

Re: [atlas] how to earn credits com236.259.148
by kiran.gunana＠colruytgroup.com 11 Jul '19

11 Jul '19

Hello Michael, Thanks alot for the good gesture, me too got some good number of credits for now however just wondering after 3 months I will loose them all if I keep doing the same measurments. So looking for a way to earn some credits. rg, kiran ----- Original Message: com236.253.880 --------------------------------- From: Michael J. Oghia (mike.oghia(a)gmail.com) To: kiran.gunana(a)colruytgroup.com Copy: ripe-atlas(a)ripe.net Subject: Re: [atlas] how to earn credits com236.252.126 Date: 11 July 2019 (08:34) Can we just transfer you some credits? Most of us have a massive surplus. Let us know your preferred email address. Best, -Michael On Thu, Jul 11, 2019, 8:16 AM <kiran.gunana(a)colruytgroup.com> wrote: Hello, I am running my probe since 3 weeks and I spent almost 1milion credits for measuring some metrics, however I am not able to earn any credits. Can some give me the steps to enable me earning some credits as well. rg, kiran. Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

3 2

how to earn credits com236.252.126
by kiran.gunana＠colruytgroup.com 11 Jul '19

11 Jul '19

Hello, I am running my probe since 3 weeks and I spent almost 1milion credits for measuring some metrics, however I am not able to earn any credits. Can some give me the steps to enable me earning some credits as well. rg, kiran. Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

2 1

Re: [atlas] DNS RTT over TCP: twice as long than UDP?
by Ponikierski, Grzegorz 10 Jul '19

10 Jul '19

Just to confirm I verified what exactly dig measures. For example, this dig takes 8ms (which is always rounded): [gponikie@krk-mptoy atlas_day68_step1]$ dig +tcp example.com @1.1.1.1 ; <<>> DiG 9.14.3 <<>> +tcp example.com @1.1.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14416 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1452 ;; QUESTION SECTION: ;example.com. IN A ;; ANSWER SECTION: example.com. 5212 IN A 93.184.216.34 ;; Query time: 8 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Tue Jul 09 13:17:55 CEST 2019 ;; MSG SIZE rcvd: 56 If you check it with wireshark it looks like this: No. Time Source Destination Protocol Length Window size value Shift count Info 1 13:17:55.014898 192.168.1.83 1.1.1.1 TCP 78 65535 6 53593 → 53 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 TSval=676915370 TSecr=0 SACK_PERM=1 2 13:17:55.029784 1.1.1.1 192.168.1.83 TCP 74 29200 10 53 → 53593 [SYN, ACK] Seq=0 Ack=1 Win=29200 Len=0 MSS=1412 SACK_PERM=1 WS=1024 3 13:17:55.029883 192.168.1.83 1.1.1.1 TCP 54 4096 53593 → 53 [ACK] Seq=1 Ack=1 Win=262144 Len=0 4 13:17:55.030041 192.168.1.83 1.1.1.1 DNS 108 4096 Standard query 0x3850 A example.com OPT 5 13:17:55.038351 1.1.1.1 192.168.1.83 TCP 68 29 53 → 53593 [ACK] Seq=1 Ack=55 Win=29696 Len=0 6 13:17:55.038572 1.1.1.1 192.168.1.83 DNS 120 29 Standard query response 0x3850 A example.com A 93.184.216.34 OPT 7 13:17:55.038624 192.168.1.83 1.1.1.1 TCP 54 4095 53593 → 53 [ACK] Seq=55 Ack=59 Win=262080 Len=0 8 13:17:55.039580 192.168.1.83 1.1.1.1 TCP 54 4096 53593 → 53 [FIN, ACK] Seq=55 Ack=59 Win=262144 Len=0 9 13:17:55.047201 1.1.1.1 192.168.1.83 TCP 68 29 53 → 53593 [FIN, ACK] Seq=59 Ack=56 Win=29696 Len=0 10 13:17:55.047273 192.168.1.83 1.1.1.1 TCP 54 4096 53593 → 53 [ACK] Seq=56 Ack=60 Win=262144 Len=0 From this traffic looks like dig measures time between packets 4 (DNS query) and 6 (DNS response) which is precisely 8.5ms and matches what dig shows. Including TCP handshake it takes 23.7ms, 2.8x longer which is expected . RTT can be measured on different layers for the same communication stream. In case of DNS over UDP we just ignores UDP overhead because it doesn't add any packets. With TCP additional packets are added which significantly increase time that end-user have to wait from first packet to get information that he/she needs. IMO RTT should always be measured from 1st packet to packet which has information that you have actual data. If we want to measure raw DNS performance without overhead then it must be explicitly market it measurement description. Regards, Grzegorz From: Giovane Moura <giovane.moura(a)sidn.nl> Date: Friday 2019-07-05 at 14:34 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] DNS RTT over TCP: twice as long than UDP? Folks, This page at Atlas provides a great visualization on the RTT of DNS queries over TCP/UDP to the Root DNS servers: https://atlas.ripe.net/results/maps/root-server-performance/ We can see that the RTT of TCP queries is at least twice as long than UDP ones (which, according to the page " TCP is expected to be 2-3 times " longer. I cannot replicate these results in my setup, even in large scale from various vantage points: I always get very similar results for either TCP or UDP. Example: UDP: * $ dig example.nl @ns1.dns.nl Query time: 8 msec TCP: * $dig +tcp example.nl @ns1.dns.nl Query time: 9 msec I think there might be something with the definition of RTT. My hypothesis is that the field *rtt* on DNS queries on Atlas[1], for TCP, is, in fact, measuring 2 RTTs: the RTT of the TCP handshake, and the RTT of query/response itself. By definition, however, RTT is "the length of time it takes for a signal to be sent plus the length of time it takes for an acknowledgement of that signal to be received."[2]. So if DNS TCP measurements starts measuring from the SYN packet, that', in fact, be two RTTs. Is this the case with Atlas? I know it may sound a bit like nitpicking, but I just want to be sure of what's exactly being measured. thanks a lot, /giovane [1] https://atlas.ripe.net/docs/data_struct/#v4750_dns [2] https://en.wikipedia.org/wiki/Round-trip_delay_time

2 2

New on RIPE Labs: Internet Tools BoF Discovers Common Challenges for Network Operators
by Michela Galante 09 Jul '19

09 Jul '19

Dear colleagues, Here is a great summary provided by Sofia Silva Berenguer (APNIC) of the outcomes of the Internet Tools BoF organised at the recent LACNIC 31 meeting: https://labs.ripe.net/Members/sofia_silva_berenguer/internet-tools-bof-disc… Kind regards, Michela Galante RIPE NCC

1 0

DNS RTT over TCP: twice as long than UDP?
by Giovane Moura 05 Jul '19

05 Jul '19

Folks, This page at Atlas provides a great visualization on the RTT of DNS queries over TCP/UDP to the Root DNS servers: https://atlas.ripe.net/results/maps/root-server-performance/ We can see that the RTT of TCP queries is at least twice as long than UDP ones (which, according to the page " TCP is expected to be 2-3 times " longer. I cannot replicate these results in my setup, even in large scale from various vantage points: I always get very similar results for either TCP or UDP. Example: UDP: * $ dig example.nl @ns1.dns.nl Query time: 8 msec TCP: * $dig +tcp example.nl @ns1.dns.nl Query time: 9 msec I think there might be something with the definition of RTT. My hypothesis is that the field *rtt* on DNS queries on Atlas[1], for TCP, is, in fact, measuring 2 RTTs: the RTT of the TCP handshake, and the RTT of query/response itself. By definition, however, RTT is "the length of time it takes for a signal to be sent plus the length of time it takes for an acknowledgement of that signal to be received."[2]. So if DNS TCP measurements starts measuring from the SYN packet, that', in fact, be two RTTs. Is this the case with Atlas? I know it may sound a bit like nitpicking, but I just want to be sure of what's exactly being measured. thanks a lot, /giovane [1] https://atlas.ripe.net/docs/data_struct/#v4750_dns [2] https://en.wikipedia.org/wiki/Round-trip_delay_time

3 2

Atlas problems this morning?
by Stephane Bortzmeyer 01 Jul '19

01 Jul '19

#22170557, #22171022 and #22171068 terminate but no results are available. Is there some problem going on?

2 1

Search for Probe
by Sascha Groetzner 01 Jul '19

01 Jul '19

Hello, I would like to take part at the ripe atlas grip. I applied already for a probe and still waiting for delivery since a long time. Does anyone have a probe which isn`t in use or would like to transfer? best regards Sascha Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

Streaming API Losses
by Marcel Flores 28 Jun '19

28 Jun '19

Hi all, We've been exploring the use of the Streaming API to collect result stream data for a set of user defined measurements, in particular using the interface available in Cousteau. However, we've found that the Streaming API seems to be "lossy", with only a fraction of the results reported through the usual system making their way into the stream. I've not been able to find any sort of pattern on what does and doesn't make it through. Does anyone else have experience with this? Are there known limitations with the Streaming API? If so, has anyone worked out any clever workflows to accommodate? Thanks very much! -- *Marcel Flores, PhD* | Sr. Research Scientist research.verizondigitalmedia.com | AS15133 <https://www.peeringdb.com/asn/15133> p: +1 310.593.6880 e: marcel.flores(a)verizondigitalmedia.com 13031 W Jefferson Blvd. Building 900, Los Angeles, CA 90094

1 0

Filter for all results of a probe within a given timeintervall
by Lars Prehn 28 Jun '19

28 Jun '19

Hi everyone, I'm currently trying to retrieve ping and/or traceroute results for a specific probe in a given time interval via cousteau and/or the measurement API directly. It seems like I'm not clever enough to get it done. Is there a possibility to achieve this goal without iterating over each and every measurement to check whether or not the probes and the time match? Best regards, Lars

1 0