- ripe-atlas - mailman.ripe.net

Probe disconnects every 2 hours
by Daniel AJ Sokolov 21 Dec '17

21 Dec '17

Hello, the logs for my probe (version 1) show that is has been disconnecting very regularly every 2 hours. The uptimes are always +/- 1 hour 50 minutes, followed by a disconnect period of 5, 8, or 11 minutes. Out of my last 25 connects, 20 are like that. 3 have double the uptime (about 3 hours and 50 minutes), only one has almost 24 hours, and the current one is 6 hours and counting. The disconnects there were, again, 5, 8, or 11 minutes. However, I to not notice similar disconnects as a user of the same network. I sometimes listen to online streams for more then 2 hours without interruption. I work on my computer for more than 2 hours and don't notice these interruptions of my internet access. It's all IPv4; no IPv6 here. The controller is ctr-fnc01. What could be the cause of these log entries? BR Daniel AJ

2 3

Any recommendations on how I can get ATLAS admins to reset my two-step verification?
by Jan Galkowski 20 Dec '17

20 Dec '17

Hi I have an ATLAS probe, long connected with a lot of credits. I have a RIPE NCC account, where the email and passcode are both recognized. Unfortunately, I apparently also have two-step verification set up. I don't recall doing that, but, then, it's probably my memory is at fault. And I do not know where, if anywhere, I put the notes for the 32 bit "emergency" code. The guidance at the site is to reach out to the ATLAS administrations in this situation for, I presume a reset. I have looked for additional information, and opened tickets. Unfortunately, the link to the FAQ describing this security facility is "404", and the tickets have gone acknowledged by the ticketing system, but not responded to. My interest is keen, because I was hoping to get some measurements research done by the start of the New Year. Alas. I have things I can do towards this, but has anyone else been in a similar situation? Advice? Thanks very much, Merry Newtonmas, and best wishes for the New Year. - Jan Galkowski, Westwood, MA.

2 2

Second Part of RIPE Atlas as IoT Devices - The RIPE Atlas Architecture
by Mirjam Kuehne 19 Dec '17

19 Dec '17

Dear colleagues, Here is the second part of the story about RIPE Atlas as IoT Devices. This time we we give some insights into the overall architecture of the RIPE Atlas network and how we manage secure communication with our probe flock. https://labs.ripe.net/Members/kistel/ripe-atlas-architecture-how-we-manage-… Kind regards, Mirjam Kühne RIPE NCC

1 0

Missing servers in DNSMON
by Chris Amin 13 Dec '17

13 Dec '17

Dear colleagues, It was recently brought to our attention that a small number of name servers were not being included in the visualisations on DNSMON. This issue has now been fixed, but you may notice a gap between mid-September and mid-December when visualising large time ranges for the affected servers. Apologies for any confusion or inconvenience caused. The affected zones and nameservers are: hk. - 203.119.87.218 xn--j6w193g. - 203.119.87.218 il. - 128.139.35.5 il. - 194.146.106.122 il. - 2001:67c:1010:31::53 mx. - 2001:13c7:7000::1 pl. - 2001:1a68:0:17::238 pl. - 2001:a10:121:1::156 pl. - 2a00:4120:8000:2::186 Kind regards, Chris Amin RIPE NCC

1 0

New on RIPE Labs: Measuring Network Behaviour with RIPE Atlas
by Mirjam Kuehne 08 Dec '17

08 Dec '17

Dear colleagues, In this article Marcel Flores and Stephen McQuistin describe how they used RIPE Atlas to understand the network behaviours their end-users are experiencing: https://labs.ripe.net/Members/verizon_digital/seeing-the-world-with-ripe-at… Kind regards, Mirjam Kühne RIPE NCC

1 0

ULA detected by probe?
by JORDI PALET MARTINEZ 06 Dec '17

06 Dec '17

Hi, I’ve two probes in two networks, with exactly the same config in both routers (which are the same, using LEDE). ULA is NOT configured in the router and no other device in the network can see the ULA. However, one of the probes, shows the TAG “IPv6 ULA” And Addresses fd3f:4830:fd21:0:220:4aff:febf:ffaf/64 2001:…. How is that possible and how to clean up it? Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

2 1

Problem with new Openipmap
by Klaus Darilion 06 Dec '17

06 Dec '17

Hi! I just noticed the new interface of Openipmap. Nice, but unfortunately not as useful as the old one: 1. clicking on the graph does not show the trace 2. it does not show 50 traces as the last one (I need plenty of traceroutes for network optimization, not only 10) 3. there should be a possibillity to mark a location as wrong. E.g. see https://atlas.ripe.net/measurements/10418213/#!openipmap Openipmap display Warsaw as target where all this traces terminate in New York as this IP address is an Anycast IP address and therefore it must no be mapped to a single location. hence, for Anycast IPs there should be feature to mark the IP as Anycast. Then the final target is usually the location of the IP address before. regards Klaus

3 2

Effect of "Resolve on Probe"-option
by Tim Wattenberg 04 Dec '17

04 Dec '17

Hi everyone, I think I don’t quite understand the effect of the „Resolve on Probe“ option when creating a measurement. The form says it forces the probe to do DNS resolution, the API reference says that it indicates that a name should be resolved (using DNS) on the probe otherwise it will be resolved on the RIPE Atlas servers. Could someone explain what this means for example if I have a simple measurement for querying the A record of a given domain via the probe’s resolvers? Thanks, Tim

4 4

map distinction between "no data yet" and "timeout"
by Ben Clifford 01 Dec '17

01 Dec '17

I was just trying to get a map view for a nameserver that appeared to not be responding to people in some geographical areas. I fired off a measurement across a load of probes and get a map back. In my particular case, the result I'm looking for is whether a response came back from the target server at all. But the map doesn't distinguish between probes that haven't measured yet, and probes that have attempted a measurement but timed out, as far as I can tell. --

1 0

dig +trace equivalency
by dikshie 29 Nov '17

29 Nov '17

Hi, I use to use +trace option in dig command. Is there any same function equivalency in Atlas's DNS measurement tool? Thank you in advance. -- -dikshie-

3 4

Trying to measure Quad9 latency
by Eduardo Duarte 29 Nov '17

29 Nov '17

Hi all, After the recent launch of the Quad9 service I try to discover if it had a best response time them my actual resolver, that is google public DNS. To do this I launch a comparing measurement using atlas that would run during one day to the same address from the probes in my ISP. The address that I was trying has a very high TTL so I was expecting to always hit the cache of the servers and them get a good comparison base. I know that there are other factors involve in server response time but to my home connection I fill that this where enough. When I got the results from the measurement they were not what I expected.... The measurements to Quad9 had high value of REFUSAL. Does any one as a clue why??? The measurement result is available at https://atlas.ripe.net/measurements/10269508 Best regards, -- Eduardo Duarte Gestão e Desenvolvimento de Projetos l Project Development Management *DNS.PT* Rua Latino Coelho, n.º 13, 5.º piso | 1050-132 Lisboa | Portugal Tel: (+351) 211 308 200 Fax: (+351) 211 312 720 dns.pt <http://www.dns.pt> | dnssec.pt <http://www.dnssec.pt> | 3em1.pt <https://www.3em1.pt> | facebook.com/dns.pt <https://www.facebook.com/dns.pt> | pt.linkedin.com/in/dnspt <http://pt.linkedin.com/in/dnspt> Aviso de Confidencialidade/Disclaimer: Este e-mail foi escrito de acordo com o novo acordo ortográfico. Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail and delete it immediately. [ Antes de imprimir esta mensagem pense no ambiente. Before printing this message, think about environment ]

8 9

New on RIPE Labs: Last sponsored RIPE Atlas anchors for 2017
by Alun Davies 27 Nov '17

27 Nov '17

Dear colleagues, New on RIPE Labs, read all about the last phase of the RIPE NCC’s 2017 campaign to sponsor fifteen RIPE Atlas anchors: https://labs.ripe.net/Members/alun_davies/last-sponsored-ripe-atlas-anchors… Kind regards, Alun Davies RIPE NCC

1 0

New on RIPE Labs: RIPE Atlas on the Go
by Mirjam Kuehne 15 Nov '17

15 Nov '17

Dear colleagues, Ollivier Robert just released a tool that provides access to the RIPE Atlas API in Go. Please find more details on RIPE Labs: https://labs.ripe.net/Members/ollivier_robert/ripe-atlas-on-the-go Kind regards, Mirjam Kühne RIPE NCC

1 0

New vendor for RIPE Atlas v3 anchors
by Alun Davies 15 Nov '17

15 Nov '17

Dear all, Meconet, the latest addition to our list of vendors for RIPE Atlas v3 anchors, is offering the new anchor hardware fully assembled with 3 years warranty. The RIPE Atlas anchor from Meconet comes in a 19” chassis with integrated power supply: https://shop.meconet.de/a/117330?language=en <https://shop.meconet.de/a/117330?language=en> Whilst Meconet is currently the only one offering the device fully assembled, there are other vendors listed on the following page: https://atlas.ripe.net/get-involved/become-an-anchor-host/ <https://atlas.ripe.net/get-involved/become-an-anchor-host/> Updated information on the latest generation of RIPE Atlas anchors can be found in the following RIPE Labs article: https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors <https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors> Best regards, Alun Davies RIPE NCC

4 3

Running RIPE probe VM
by Evgeniy Sudyr 14 Nov '17

14 Nov '17

Hello All, I'm interesting for running RIPE probe on VM or Docker container. Any chance to get this idea real? -- With regards, Eugene Sudyr

2 2

A Go library to talk to RIPE Atlas
by Stephane Bortzmeyer 14 Nov '17

14 Nov '17

https://blog.keltia.net/2017/11/13/ripe-atlas-is-usable-dot-dot-dot/ [Still a bit rough...]

1 0

Probe disconnected – cold reboot required (ctr-ams08)
by Christian Schrötter 13 Nov '17

13 Nov '17

Hello Atlas-Users! Do you have any problems with your probes today? Mine disconnected two times in the last ~15 hours and never came back online. Internet is stable and SD-card looks ok. I had to force a cold restart to get it back online. Strange thing, it's the first time in two years. Old uptime was 99 days... :-/ -- With kind regards, Christian Schrötter

1 0

New on RIPE Labs: Verfploeter: Broad and Load-aware Anycast Mapping
by Mirjam Kuehne 13 Nov '17

13 Nov '17

Dear colleagues, Here is a summary of a research paper written by Wes Hardaker, Wouter de Vries and Ricardo Schmidt: Verfploeter: Broad and Load-aware Anycast Mapping IP anycast provides DNS operators and CDNs with automatic fail-over and reduced latency by breaking the Internet into catchments, each served by a different anycast site. https://labs.ripe.net/Members/wouter_de_vries/verfploeter-broad-and-load-aw… Kind regards, Mirjam Kühne RIPE NCC

1 0

Recent TLS supported by probes?
by Stephane Bortzmeyer 13 Nov '17

13 Nov '17

I cannot get the certificate for <https://dns-resolver.yeti.eu.org/> (measurement #10174881): "alert" is "{u'description': 40, u'level': 2}". It works with other, more "mainstream", HTTPS sites (see #10174883). I suspect this is because the probes don't handle the recent TLS stuff. Can anyone confirm or infirm?

2 1

Atlas Measurements
by Tom Glass 13 Nov '17

13 Nov '17

Hello all, Hope you are having a great weekend. I just stopped by to ask if you guys would know where/if I can add new probes to an existing measurement. A new probe has appeared in the area we are monitoring and I was hoping there was a way of adding it without recreating the measurement? Cheers, all, Tom

2 1

Odd queries from probe
by Jared Mauch 10 Nov '17

10 Nov '17

While doing some debugging of my home network, I noticed some odd queries from the probe, namely this one: 02:28:36.921622 IP6 fe80::a2f3:c1ff:fec4:479f.51123 > 2001:558:feed::2.53: 23808+ A? 12920.atlas.ripe.net.b61065696c194ac3. (55) Is this some captive portal/wildcarding detection, or perhaps some other software issue? curious, - Jared

2 1

IPv4 leading zeroes and weird interface behaviour
by Max Grobecker 30 Oct '17

30 Oct '17

Hello, is there - by standard - a definition on how to represent an IPv4 address? I have (for example) the IP address "73.0.255.229", which can IMHO also be written as "073.000.255.229" as the leading zeroes are not giving any changes to the binary representation of this address. Am I right on this? But: When I lookup this IP address on https://stat.ripe.net/073.000.255.229 the first octet is internally getting swapped to "59". This can be explained, if you take "073" as an octal value and convert it to a decimal value. It is definitely a octal-to-decimal conversion thing, as for example also the value "010" is getting replaced by "8" and so on. Now I'm puzzled: Of course, writing IPv4 octets with leading zeroes is not very common. But: Is it officially prohibited or discouraged? This weird conversion also happens inside the "geoiplookup" tool by MaxMind and I'm not sure if I'm going to be the moron in this story or if I found the same bug inside multiple softwares at once ;-) Thanks and greetings from Wuppertal Max

8 7

Segmentation fault (core dumped)
by Antonio D 26 Oct '17

26 Oct '17

I upgraded UBUNTU from 17.04 to 17.10 and I discovered that ripe-atlas-tools had disappeared. So I tried reinstalling it with "pop install ripe-atlas-tools", but the process crashed with the following error: Segmentation fault (core dumped) Can you help me solve the problem? Thank you Antonio Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

Why did I get "Over the limit on number of results"?
by Eduardo Duarte 25 Oct '17

25 Oct '17

Hello, I schedule some measurements to run during today but I got an error on some of them. The error is "Over the limit on number of results". I have enough credits to run all the measures so I don't understand this message. Thank you and best regards, -- Eduardo Duarte Gestão e Desenvolvimento de Projetos l Project Development Management *DNS.PT* Rua Latino Coelho, n.º 13, 5.º piso | 1050-132 Lisboa | Portugal Tel: (+351) 211 308 200 Fax: (+351) 211 312 720 dns.pt <http://www.dns.pt> | dnssec.pt <http://www.dnssec.pt> | 3em1.pt <https://www.3em1.pt> | facebook.com/dns.pt <https://www.facebook.com/dns.pt> | pt.linkedin.com/in/dnspt <http://pt.linkedin.com/in/dnspt> Aviso de Confidencialidade/Disclaimer: Este e-mail foi escrito de acordo com o novo acordo ortográfico. Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail and delete it immediately. [ Antes de imprimir esta mensagem pense no ambiente. Before printing this message, think about environment ]

3 2

New on RIPE Labs: RIPE Atlas Probes as IoT Devices
by Mirjam Kuehne 20 Oct '17

20 Oct '17

Dear colleagues, As a follow-up to the presentation Robert Kisteleki gave during the IoT Roundtable Meeting in September [1], we have published a RIPE Labs article describing RIPE Atlas probes as IoT devices and some initial design decisions that we thought were important for such an infrastructure: https://labs.ripe.net/Members/kistel/ripe-atlas-probes-as-iot-devices Kind regards, Mirjam Kuhne RIPE NCC [1] https://www.ripe.net/participate/meetings/roundtable/september-2017/ripe-io…

1 0

status is confusing
by Dave 18 Oct '17

18 Oct '17

Hi, The status page of one of my probes says: I’ve been bitten a few times by misinterpreting this. Could these 2 things be put on separate lines? This does suggest the probe is up but only when you missed the red colour and didn’t get the meaning of the icon. Also, when you read the mail it may be hours later than when it was sent. So keep in mind that a receiver’s probe could be back online in the meantime. Often a mail will be checked on the mobile. The status on a small screen must be clear too. I’ll restart the probe and modem and it will work again but I would have done that on day 1 if the message was more clear. Thanks, Dave

1 0

New on RIPE Labs: Insights from RIPE Atlas Probe Disconnections
by Mirjam Kuehne 17 Oct '17

17 Oct '17

Dear colleagues, There are all kinds of reasons why RIPE Atlas probes might become disconnected. So, even though we'd like all probes to be connected all the time, disconnects can also tell us a useful story. Please find this new article by Emile Aben on RIPE Labs exploring what insights we can gain from RIPE Atlas probe disconnections: https://labs.ripe.net/Members/emileaben/insights-from-ripe-atlas-probe-disc… Kind regards, Mirjam Kuhne RIPE NCC

1 0

What is the meaning of 127.0.0.1 as probe resolver?
by Baptiste Jonglez 16 Oct '17

16 Oct '17

Hi, While looking at the result of built-in DNS measurements that use the probe resolvers, I noticed that a significant fraction of probes have "127.0.0.1" as a resolver. And the results are strange: performance is really bad, for instance measurement 30002 gives a median resolution time of 300 ms for these probes! What could be the meaning of this? It almost looks like a recursive resolver with no cache at all is running on the probes themselves. I was looking at this measurement: https://atlas.ripe.net/measurements/30002/ And here are some example probes that exhibit this "127.0.0.1" symptom: 6001, 6087, 6162, 6235, 6308. Any reasonable explanation is welcome! Thanks, Baptiste

2 2

Problem in status checks?
by Stephane Bortzmeyer 14 Oct '17

14 Oct '17

Error 500 when trying to retrieve status checks: % curl -v 'https://atlas.ripe.net/api/v2/measurements/2060427/status-check?permitted_t…' ... > GET /api/v2/measurements/2060427/status-check?permitted_total_alerts=3 HTTP/1.1 > Host: atlas.ripe.net > User-Agent: curl/7.52.1 > Accept: */* > < HTTP/1.1 500 Internal Server Error < Server: nginx/1.10.2 < Date: Sat, 14 Oct 2017 07:09:10 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 38403 < Connection: keep-alive < Vary: Accept-Encoding, Cookie < X-Frame-Options: SAMEORIGIN < Strict-Transport-Security: max-age=15768000

2 1

Plan to Implement RIPE Atlas WiFi Measurements
by Robert Kisteleki 09 Oct '17

09 Oct '17

Dear colleagues, We wanted to update the community and let you know that we plan to start work on the proposed experiment with WiFi measurements in mid-2016. As we communicated in a recent RIPE Labs article, we will work with GÉANT as a test partner to learn more about the operational effects of introducing WiFi measurements to the RIPE Atlas system, in addition to the benefits we believe this could provide for the entire RIPE Atlas community. Please see the article for more details if you are interested: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-wifi-measure… We will continue to update you once we’ve begun work on this plan, and we welcome your comments in the meantime. Regards, Robert Kisteleki RIPE NCC

3 3

Probe disconnects
by RIPE 09 Oct '17

09 Oct '17

Hi, I have a probe ( #22583 ) at home connected via my DSL link, for IPv6 connectivity I use a Hurricane Electric ( tunnelbroker.net ) /48 tunnel. I noticed on the monthly report that my probe is showing lots of short ( 1-2 min) disconnects. But it only seems to happen when the connection address in the probe’s network tab is the IPv6 address. In that case the IPv4 Connection address is empty. If it’s showing the IPv4 the probe stays connected for days ( until the DSL link really disconnects). Is there a way to get the probe to ignore the IPv6 for connection status ? Or to mark it as disconnected when both iPv4 and IPv6 are disconnected ? Best regards, Paul van der Zwan

3 2

Charity IT Pulse :) one more sleep till Bytenight Action for Children 2017
by Colin Johnston 05 Oct '17

05 Oct '17

> > Dear all, one more sleep until ByteNight events across the UK on Friday night. > Please donate if you can electronically > > > See mydonate page linked to Byte Night https://mydonate.bt.com/fundraisers/colinjohnston1 <https://mydonate.bt.com/fundraisers/colinjohnston1> > > For more information go to www.bytenight.org.uk <http://www.bytenight.org.uk/> or to donate Text Byte17 and the amount to 70070. > > In just 1 days time, on Friday 6 October, I am spending one night sleeping rough for Byte Night. Byte Night works to support some of the 83,000 young people who are homeless in the UK. One in four young people who are homeless have been diagnosed with mental health issues and one in five will have self-harmed due to their situation at home. £10 could provide an hour’s support with a mental health practitioner for 1 young people to help them get through their issues. Action for Children has supported many young people to a safe and happy future. Unfortunately, so many more still need our help. You can help support young people across the UK by generously donating to my page > > > > Yours > > Colin Johnston > > Colin Johnston <https://myprofile.bt.com/Person.aspx?accountname=IUSER%5C600969844> > IT Support Senior Professional, Core IT Infrastructure > BT Technology Service & Operations <https://intra.bt.com/bt/tso/Pages/index.aspx> | Tel: 01313001324 <tel:01313001324> | MyProfile <https://myprofile.bt.com/Person.aspx?accountname=IUSER%5C600969844> | colin.johnstone(a)bt.com <mailto:colin.johnstone@bt.com> | http://fixit.bt.com/ <http://fixit.bt.com/> > > BT Group plc Registered office: 81 Newgate Street London EC1A 7AJ. Registered in England and Wales no. 4190816 This electronic message contains information from BT Group plc which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please delete it and notify me immediately by telephone or email.

1 0

ipv6 ping to root name servers failing?
by Tapio Sokura 04 Oct '17

04 Oct '17

Hello, I noticed a few days ago from the built-in probe graphs that ipv6 pings started to fail to the a-root name server instance serving the probe I host. Now also the j-root serving the probe is dropping pings. Some other instances of the same root servers at the moment are still answering pings. If it is intentional that root name servers are starting to drop pings, something should probably be done to the built-in probe measurements/graphs. Does someone know more about this, will all roots be dropping pings in the future or is this just a Verisign thing (a and j operator)? Tapio

2 1

List of Atlas probes subjected to DNS traffic interception (MITM)
by Baptiste Jonglez 29 Sep '17

29 Sep '17

Hi, I am looking for a list of Atlas probes that suffer from DNS traffic interception, to exclude them from my measurements. What I mean by "traffic interception" is that DNS queries from the probe to a third-party DNS server do not reach the server, but are intercepted and answered by a middle-box instead. I started building this list myself, but it's a long and potentially error-prone process. It seems that the "DNS Root Instances" map could be used for that purpose, because DNS traffic interception shows up as if the probe was contacting an "Unknown" root instance. To get the list of probes, I ended up using an URL like the following, showing probes for all possible "unknown" root instance hostnames: https://atlas.ripe.net/results/maps/root-instances/?server=1&question=10300… ... However, there seems to be a limit on the size of the URL so I cannot get all probes, and they are just displayed on the map without any obvious way to get the raw list of probes instead. Is there a way to get the raw list of probes from this map? Or has anybody already done this classification work independently? I also looked for DNS-related tags on probes, but could not find anything useful. Thanks, Baptiste

4 6

New on RIPE Labs: Celebrating 10, 000 Active RIPE Atlas Probes
by Mirjam Kuehne 29 Sep '17

29 Sep '17

Dear colleagues, In August 2017, just short of seven years after RIPE Atlas was launched, the number of connected RIPE Atlas probes hit 10,000. Thank you all for making this happen! Find some more details and an overview of recent developments on RIPE Labs: https://labs.ripe.net/Members/alun_davies/celebrating-10000-active-ripe-atl… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New RIPE Labs article on RIPE Atlas v3 Anchors
by Alun Davies 29 Sep '17

29 Sep '17

Dear colleagues, In this RIPE Labs article the RIPE NCC looks into hardware specifications and logistics for the next generation of RIPE Atlas anchors: https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors Best regards, Alun Davies RIPE NCC

3 3

New on RIPE Labs: Measuring your Web Server Reachability with TCP Ping
by Mirjam Kuehne 27 Sep '17

27 Sep '17

Dear colleagues, HTTP measurements from RIPE Atlas probes are only possible towards RIPE Atlas anchors. However, when it comes to measuring the connectivity and latency of web servers on the network level, an alternative exists, which we call TCP Ping: a traceroute with special options that mimic the TCP handshake that takes place when an HTTP connection is established. In this RIPE Labs article we compare the results of large scale HTTP and TCP Ping measurements: https://labs.ripe.net/Members/wilhelm/measuring-your-web-server-reachabilit… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: PoE-ing a RIPE Atlas Probe
by Mirjam Kuehne 18 Sep '17

18 Sep '17

Dear colleagues, In this new RIPE Labs article Geert Jan de Groot explains how to "PoE" a RIPE Atlas Probe: https://labs.ripe.net/Members/geert_jan_de_groot/poe-ing-the-ripe-atlas-pro… Kind regards, Mirjam Kuhne RIPE NCC

1 0

RIPE Atlas v3 Anchor Hardware
by Alun Davies 12 Sep '17

12 Sep '17

Dear all, The RIPE NCC has chosen a new model for the RIPE Atlas v3 Anchors. The hardware we finally opted for is the PC Engines APU2. As well as being cheaper than the previous generation of anchors, this model meets the majority of requirements we laid out for the next generation of anchors. To be clear, given that there are still a couple of minor logistical details to resolve, we are still keeping applications on hold for the time being. That said, we look set to meet our September deadline to resume shipping of RIPE Atlas anchors. For more information and future updates, please read our article on RIPE Labs: https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas… <https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas…> Kind regards, Alun Davies Comms RIPE NCC

4 3

Can Atlas probe handle Truncated response ?
by Davey Song(宋林健) 12 Sep '17

12 Sep '17

Hi folks, I once setup a measurement of DNS UDP to see if the number of timeout increase due to large response. The answer is yes. But I wonder if the timeout is no answer after three times of retries or also includes TCP fallback. Is it true that the probe in DNS UDP measurement will not use TCP to retry even after it receives a truncated response. Best regards, Davey

3 2

IPv6 issues with ATLAS and DNSMON
by Romeo Zwart 12 Sep '17

12 Sep '17

dear all, Due to a human error on our side, there have been problems with IPv6 connectivity to/from many of our servers, including atlas anchors since approximately 9:30 UTC this morning. The problem has been corrected and systems are recovering, but you may still see some problems in RIPE Atlas and DNSMON. We're still investigating the full impact of the problem and will have more information at a later stage. We apologise for any inconvenience. Romeo Zwart

1 1

Infrastructure upgrades
by Robert Kisteleki 06 Sep '17

06 Sep '17

Dear all, Yesterday we began infrastructure (OS) upgrades on our controllers. As a consequence each probe will be disconnected for an hour or two. This can trigger notifications, if you have that configured to a sensitive enough setting. Regards, Robert Kisteleki RIPE NCC

3 4

Is there a problem with ctr-ams07 right now?
by Max Mühlbronner 06 Sep '17

06 Sep '17

Hi, my probe is online (ping) and it shows SOS messages (reboots - This probe probably last rebooted on 2017-07-06 12:23:08) on the probe page. Disconnected since 59 minutes. Is this a general problem, e.g. of the controller or is it just my probe? Does someone see similar problems right now? BR Max M.

3 3

[Training] Launching RIPE NCC::Educa - Online Learning Event
by Sandra Bras 04 Sep '17

04 Sep '17

Dear colleagues, The RIPE NCC has a new way to dive deep into a topic without having to travel or leave your desk. RIPE NCC::Educa are free, online learning events that bring industry experts together to share insight, expertise and best practice with those that want more in-depth knowledge on a particular subject. Our first event focuses on RIPE Atlas on Thursday, 5 October from 8:00 - 13:00 UTC. Reserve your place here: https://www.ripe.net/support/training/ripe-ncc-educa <https://www.ripe.net/support/training/ripe-ncc-educa> You can join us for one session, multiple sessions or the full programme. We’re updating the agenda constantly, so be sure to check here for the latest additions: https://www.ripe.net/support/training/ripe-ncc-educa/agenda <https://www.ripe.net/support/training/ripe-ncc-educa/agenda> For more information on RIPE NCC::Educa, check out our RIPE Labs article: https://labs.ripe.net/Members/sandra_bras/introducing-ripe-ncc-educa <https://labs.ripe.net/Members/sandra_bras/introducing-ripe-ncc-educa> If you have any questions, please get in touch with us: <e-learning(a)ripe.net <mailto:e-learning@ripe.net>> Warm regards, Sandra Brás E-Learning Program Manager RIPE NCC

1 0

Sharing Credits seems broken .....
by Barry Raveendran Greene 24 Aug '17

24 Aug '17

Hi Team, We have a problem with the sharing credits. I’ve got plenty of credits on my account. I’ve granted access to my colleague (Jim Gilbert) and a test group account (atlas-network(a)akamai.com). Just to be clear, it states: Sharing Access - If you don’t want to set limits on the number of credits you share, you can also allow other RIPE Atlas users to use your credits directly for their own measurements. Select the “Share Access” tab on your credits page and enter the RIPE Atlas users you want to give access to. Users who have been given access to others’ credits will be able to choose whose account to charge when they create a new measurement from a drop-down menu. This option can also be set via the measurement API. A running measurement can be stopped by both you and the person with access to your credits. If you decide to stop giving someone else access to your credits, any measurements they have running will start using their own credits instead. This means I should be able to log into atlas-network(a)akamai.com select “bgreene(a)senki.xn--org-9o0a and create/run test. Correct???? This is what I get: What are we missing? Barry

2 2

DNS results visualisation
by Dave . 22 Aug '17

22 Aug '17

Hi, For the traceroute results there is a icon at the right side where you can get the complete traceroute. (View Latest Result) This is beautifully presented. Could we please have a similar icon for DNS results? Thanks, Dave Boonstra

2 2

measurement UI on 12hour clock?
by Rene Wilhelm 22 Aug '17

22 Aug '17

See attached screenshot. I created a couple of measurements which were to start at 16:05 local time, 14:05 UTC. The measurement page https://atlas.ripe.net/measurements however states a start time of 22-08-2017 02:05 UTC which is of course 12 hours in the past and had me worried for a bit I made a mistake filling in the form. Can this be fixed? it is confusing and looks a bit clumsy :) -- Rene

2 1

[rfc-editor@rfc-editor.org: RFC 8193 on Information Model for Large-Scale Measurement Platforms (LMAPs)]
by Stephane Bortzmeyer 22 Aug '17

22 Aug '17

This recent RFC on the data model for Internet measurements platform is of course of interest for RIPE Atlas. Note that their model separates controller and collector, which are one in Atlas.

1 0

New on RIPE Labs: Processing RIPE Atlas Results with jq
by Mirjam Kuehne 21 Aug '17

21 Aug '17

Dear colleagues, Please find this new article by Stephane Bortzmeyer on RIPE Labs: Processing RIPE Atlas Results with jq https://labs.ripe.net/Members/stephane_bortzmeyer/processing-ripe-atlas-res… Kind regards, Mirjam Kuhne RIPE NCC

1 0

Notify time setting does not work
by Marat Khalili 18 Aug '17

18 Aug '17

Probes have very handy feature of sending a notification when the probe is disconnected. I have mine set to 10 minutes, however last two such notifications only arrived 30 minutes after the probe was disconnected. Probe #26656 if that's important. One would think that probe itself was slow to react, but last time I monitored outage from the very beginning and the probe's page correctly showed "Disconnected for: 1 minute" and so on. Neither it is a case of slow email arrival, since according to Received header in the email it was indeed received from worker1.atlas.ripe.net 30+ minutes after disconnection time mentioned in the email body. Can it be that "Notify time" setting just doesn't work and some default value of 30 minutes is used? -- With Best Regards, Marat Khalili

4 7