- ripe-atlas - mailman.ripe.net

Many timeout-failures for DNS over TCP
by Davey Song(宋林健) 11 May '17

11 May '17

Hi folks, I setup measurements for DNS queries over both TCP and UDP. I found the timeout and failures of TCP is far more than UDP. For example : DNS over TCP: https://atlas.ripe.net/measurements/8552847/#!probes DNS over UDP: https://atlas.ripe.net/measurements/8552846/#!probes Is it normal ? I mean is there any special timeout routine/parameters of atlas probes from normal resolver? Best regards, Davey

4 4

TraceMON follow up
by Massimo Candela 10 May '17

10 May '17

As a follow up to my talk at RIPE74 about TraceMON, here a link with some live examples: https://massimo.ripe.net/tracemon/widget/ <https://massimo.ripe.net/tracemon/widget/> Ciao, Massimo

1 0

Are there plans for faster than 1G anchors?
by Bryan Socha 20 Apr '17

20 Apr '17

We're finding it harder and harder to support the 1G nic interface on the anchors. We'd love to add more but would need a 10g port at minimum (25G or 40G would also work). Are there any plans to update them for networks that can't easily support a 1G nic? Bryan Socha Network Engineer DigitalOcean

4 4

status-check misbehaving
by Georg Kahest 19 Apr '17

19 Apr '17

Hello, Am I misunderstanding something or the status-checks are kind of broken: Yesterday i made new measurement: https://atlas.ripe.net/measurements/8038852/ I noticed some probes werent reaching my ipv6 host, so decided to remove them like you can see from the Probe specifications section. Now when i goto https://atlas.ripe.net/api/v2/measurements/8038852/status-check/ I can still see the removed probes in status-check page (which contains 17 errors ) in reality if i'm lookin at measurement probe page i should have only two errors. So it seems that status-check isnt updated once probes are removed from a measurement. -- Georg Kahest System Administrator / Süsteemiadministraator Eesti Interneti SA Paldiski mnt 80, 10617 Tallinn Tel 727 1016 www.internet.ee

2 1

Behind the scenes changes to measurement creation
by Chris Amin 18 Apr '17

18 Apr '17

Dear colleagues, Today we deployed behind-the-scenes changes to the measurement creation process, both when using the website and the REST API. These changes should not have any visible effects, with the exception of improvements to the measurement API reference[1] to make it easier to see which options belong to which measurement type. Although we've tested these changes extensively, they are significant so I am sending this mail to ask you to please let us know if you notice any problems or changes when creating measurements. Kind regards, Chris Amin RIPE NCC [1] https://atlas.ripe.net/docs/api/v2/reference/#!/api/Measurement_List_GET

2 3

RIPE Atlas Maintenance Today
by Anand Buddhdev 18 Apr '17

18 Apr '17

Dear colleagues, Today, between 11:15 and 16:00 (UTC+2) we will be performing maintenance on the RIPE Atlas infrastructure. Some probes may disconnect briefly during this time. Kind regards Anand Buddhdev Senior Engineer

1 0

New on RIPE Labs: TraceMON - Network Debugging Made Easy
by Mirjam Kuehne 11 Apr '17

11 Apr '17

Dear colleagues, TraceMON is a client-side tool for visualising network topology generated by traceroutes reaching one or more targets in a network. It provides a one-click access to a set of information useful during day to day operations. Please find more details on RIPE Labs: https://labs.ripe.net/Members/massimo_candela/tracemon-traceroute-visualisa… Kind regards, Mirjam Kuhne RIPE NCC

3 3

Problems trying to add a probe to a measurement
by Colin Strutt 07 Apr '17

07 Apr '17

I'm trying to add a probe, by probe number, to an existing, running measurement, using curl, following the example and description on page 84 of the "RIPE Atlas API v2 manual". However, I'm getting an error message that does not clearly point me to the problem, and thus allow me to correct my error. Here's what I'm entering (with the <.> as placeholders, explained below) curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST -d '{"probes":[{"action":"add","requested":1,"type":"probes","value":"<p>"}]}' https://atlas.ripe.net/api/v2/measurements/<m>/participation-requests/?key=< a> where: <p> is the number of the probe I'm trying to add, and I can access it at https://atlas.ripe.net/probes/<p> <m> is the measurement to which I'm trying to add it - it's a running measurement, and I can access it at https://atlas.ripe.net/measurements/<m> <a> is the API key, which is enabled and has "Update an existing measurement" granted The error I get back is: {"error":{"status":400,"code":104,"detail":"JSON parse error - No JSON object could be decoded","title":"Bad Request"}} In case it's relevant, I'm running curl 7.53.1 on Windows 10. Thanks in advance for any suggestions. colin

2 2

ipad air
by mostafa 23 Mar '17

23 Mar '17

Sent from my iPad

1 0

New on RIPE Labs: Update on First Five Sponsored RIPE Atlas Anchors
by Alun Davies 23 Mar '17

23 Mar '17

Hello all, We just released a RIPE Labs article giving an update on the RIPE NCC’s campaign to sponsor fifteen RIPE Atlas anchors: https://labs.ripe.net/Members/alun_davies/update-first-five-sponsored-ripe-… <https://labs.ripe.net/Members/alun_davies/update-first-five-sponsored-ripe-…> Best regards, Alun Davies RIPE NCC

1 0