- ripe-atlas - mailman.ripe.net

Re: [atlas] Rate limits on Atlas
by Emile Aben 09 Sep '16

09 Sep '16

On 08/09/16 14:01, Anant Shah wrote: > Hi Emile, > > Roya and I are working on a geolocation paper and want to use the atlas > probes to ping target IPs. > > I think I am hitting the rate limit on atlas even with 99 concurrent > measurements. All my measurements now show Forbidden status. Is there a > way to increase the limit? yes, ask the team at atlas(a)ripe.net (cc-ed). the folks there can extend limits (not unlimited of course, these limits are there for a reason :) ), but would need some info from you: - what is the experiment you'd like to perform - what would you want the new limit to be (and why what you want to do can't be done with the current limits and/or existing measurements) - when does your experiment end (ie. when can we put the limits back to the default) - promise us that you'll acknowledge RIPE Atlas in a paper - send us a link/copy of the paper once it's published (i hope i'm not forgetting things :) ) cheers, emile

1 0

API probe search
by Hank Nussbacher 08 Sep '16

08 Sep '16

When searching for specific ASN probes via: https://atlas.ripe.net/probes/ and entering a search like "ASxxxx", why does the API ignore the letters AS and respond with probes that have an id of yxxxx or xxxxy or ASN yxxxy? Shouldn't it be if I specify a specific string of ASxxx the response should be *only *those probes in ASxxx or at the worst also ASxxxy? Thanks, Hank

3 5

Data delays on RIPE Atlas
by Romeo Zwart 08 Sep '16

08 Sep '16

Dear colleagues, We are performing some maintenance work on the backend clusters supporting RIPE Atlas. Unexpectedly, this is having an impact on the insertion speed of new data. This means that new data insertion is behind for a few hours. The maintenance work is expected to complete before the end of the day, at which point the backlog of data will be cleared up very quickly. We apologise for any inconvenience caused. Kind regards, Romeo

1 0

New on RIPE Labs: Using RIPE Atlas to Measure Cloud Connectivity
by Mirjam Kuehne 06 Sep '16

06 Sep '16

Dear colleagues, Please find this new article on RIPE Labs describing how to compare connectivity of cloud services using RIPE Atlas measurements. This article has been contributed by Jason Read: https://labs.ripe.net/Members/jason_read/using-ripe-atlas-to-measure-cloud-… Kind regards, Mirjam Kuehne RIPE NCC

2 1

Changes in LatencyMon
by Marat Khalili 05 Sep '16

05 Sep '16

Dear list, LatencyMon <https://atlas.ripe.net/docs/tools-latencymon/> changed for me recently with only minimum latency value shown now instead of all three. I wonder if other people see this and what are the reasons behind the change? (Cannot say yet if changes are for better or worse, but I can find no announcement and so suspect that this can be unintentional.) -- With Best Regards, Marat Khalili

2 1

New on RIPE Labs: Another Look at RIPE Atlas Probe Lifetimes
by Mirjam Kuehne 26 Aug '16

26 Aug '16

Dear colleagues, We took another, more detailed look at probe lifetimes and the dynamics of probes connecting and disconnecting from the RIPE Atlas infrastructure to try to understand how to keep the network growing in the long term. https://labs.ripe.net/Members/wilhelm/another-look-at-ripe-atlas-probe-life… Kind regards, Mirjam Kuehne RIPE NCC

7 6

Reconnecting probe 3508 - troubleshooting
by Michael-John Turner 24 Aug '16

24 Aug '16

Hi I've just reconnected probe 3508 to the network after a number of years offline (I think it was last online in November 2012?). Under the SOS history, I can see that it's making DNS queries successfully (using the DNS servers it receives by DHCP), but it's not connecting correctly to the RIPE network. The following is also displayed under SOS history: "This probe cannot connect on port 443 (HTTPS)". Any thoughts on where I can start troubleshooting? For test purposes I've connected the probe to my LAN, with full internet access. Cheers, MJ -- Michael-John Turner * mj(a)mjturner.net * http://mjturner.net/

7 10

Atlas Sagan error_message
by Wenqin SHAO 24 Aug '16

24 Aug '16

Dear list, I was using ripe.atlas.sagan to parse some ping measurements, one of them looks like the following in JSON format: rec = {u'af': 4, u'prb_id': 15843, u'result': [{u'error': u'connect failed: Network is unreachable'}], u'avg': -1, u'size': 20, u'from': u'88.174.18.20', u'proto': u'ICMP', u'timestamp': 1470009620, u'dup': 0, u'type': u'ping', u'sent': 0, u'msm_id': 1010, u'fw': 4730, u'max': -1, u'step': 240, u'src_addr': u'192.168.0.22', u'rcvd': 0, u'msm_name': u'Ping', u'lts': 641089, u'dst_name': u'192.228.79.201', u'min': -1, u'dst_addr': u'192.228.79.201'} Suppose that the above measurement is stored in a variable called rec as a dict, and I parse it using PingResult: from ripe.atlas.sagan import PingResult parsed_rec = PingResult(rec) I was expecting a no-empty string for parsed_rec.error_message, as we can see the measurement result contains an error string, however the parsed_rec.error_message is None. type(parsed_rec.error_message) <type 'NoneType’> Probably I misunderstood some part of the doc: error_message str If the result is an error, the message string is in here Could someone please clarify the exact functionality of this error_message? Many thanks in advance. Best, wenqin

1 0

Probe 10973 problem
by Vladislav Solovei 17 Aug '16

17 Aug '16

Hi. I have connected probe 10973 (which was offline several years) to the network. Firmware updated from 3.3.8 to 4010. "Status" said that "Your probe is currently connected." But on probe page i see the message: "Note: this probe is most likely not operational, and as such it has been written off as of 2013-12-03 15:44 UTC. The most likely reason for this is that the host could not be contacted." It is ok? :) Do i need to upgrade FW to latest version (tried to reboot probe several times, but fw version still 4010)? Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

RIPE Atlas "Commercial use" policy
by Robert Kisteleki 17 Aug '16

17 Aug '16

Dear colleagues, A few different organisations have approached us about using RIPE Atlas data for commercial products, services, reports, etc. We’ve now published conditions for the commercial use of RIPE Atlas data: https://atlas.ripe.net/get-involved/commercial-use/ Please read these conditions carefully if you plan on using RIPE Atlas data for any commercial purpose, and don’t hesitate to contact us if you have any questions. Regards, Robert Kisteleki RIPE NCC

1 0