- ripe-atlas - mailman.ripe.net

Prototype of "Traceroute-consistency-check" completed
by Valentino Di Donato 31 Mar '15

31 Mar '15

Hello everybody, just to be fair I completed my prototype with the idea reported in my presentation. Everything is on github here: https://github.com/vdidonato/Traceroute-consistency-check This is just a snapshot: Best, Valentino -- Valentino Di Donato Department of Engineering <http://ingegneria.uniroma3.it> Roma Tre University <http://www.uniroma3.it/> Phone: +39.06.57333215 Fax: +39.06.57333612 www.dia.uniroma3.it/~didonato <http://www.dia.uniroma3.it/%7Edidonato> didonato(a)dia.uniroma3.it <mailto:didonato@dia.uniroma3.it>

1 0

New on RIPE Labs: Amsterdam Power Outage as Seen by RIPE Atlas
by Vesna Manojlovic 31 Mar '15

31 Mar '15

Dear colleagues, As you might have heard, there was a power outage last week Friday in the north of The Netherlands, a country with a very high density of RIPE Atlas probes. This density provides us with some interesting data and visualisation. You can find more details on RIPE Labs: https://labs.ripe.net/Members/andreas_strikos/amsterdam-power-outage-as-see… Kind regards, Vesna

2 1

probes on VMs
by Klaus Darilion 30 Mar '15

30 Mar '15

Hi! I just found an old thread about virtual probes: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2013-June/000849.html I second the problems of virtual hosts and that the results may not as good as other probes result, but there is a big advantage for virtual probes - I can host them in the cloud. For example, I just wanted to debug routing issues from the Microsoft Cloud in Brazil to our server. Unfortunately there are no probes in this Cloud's AS. With a virtual probe it would be quite easy. I order an VM with Microsoft, and have my probe in the chosen datacenter. The probe could be tagged with "VM" to show that it is running on shared resources. Of course the VM will produce extra costs, but there may be sponsors, and the smallest VM is usually enough. For example , one possibility would be, that the sponsor donates the money, e.g. 10-20€ per month, and chooses the cloud location. RIPE will then rent the VMs and run the probes. With several sponsors we could get a nice cloud coverage, and we could deploy probes in networks where the provider does not want to hosts physical probes. regards Klaus

4 4

NAT conntrack invalid ICMP(v4) type 11 code 0 packets dropped by edge router
by Gary Gapinski 30 Mar '15

30 Mar '15

2 1

Create new measurement from old measurment
by Klaus Darilion 30 Mar '15

30 Mar '15

Hi! Is there a simple way in the webinterface to start a new measurement identical to an old one? (just duplicate them with new start-stop settings, in my case I want to duplicate one-off measurements) Thanks Klaus

2 2

Short and immediate report from the RIPE Atlas hackathon
by Vesna Manojlovic 30 Mar '15

30 Mar '15

We had the first RIPE Atlas hackathon! Three days of intensive coding, cooperating, learning, connecting and having fun (& surviving massive power outage on Friday in Amsterdam) - - and the results have bee impressive! Ten final projects have been presented, and four have been chosen as worthy of the awards: 1. Disco: Combining the visalization of disconnection-events with localized Twitter feed & live weather data 2. Spatial Bucketing of RIPE Atlas Probes on Map Projections (aka Picketty — making the global probe selection more equal) 3. Traceroute stability check & BGP+traceroute (two projects sharing the 3rd place) We had 24 participants & 1 no-show, 6 jury members and 11 support staff (coincidentally: 42!) On behalf of the community, we are grateful to Comcast for sponsoring prizes and travel expenses, hackerspace Technologia Incognita for the inspiring location on Friday, and to RIPE NCC for the office facilities during the weekend, staff support, food & drinks & amazing data & tools & platform of RIPE Atlas. On behalf of the organizers (RIPE NCC & Comcast), we are grateful to everyone who took part & contributed, as well as to their family & employers, who let them get away for the weekend of combined work&fun. Longer and more detailed report will follow, once we all get some sleep & collect our notes from tweets, IRC, mailing list & pieces of papers. Cheers, Vesna

2 1

What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
by Philip Homburg 27 Mar '15

27 Mar '15

Dear community members, The RIPE Atlas team has a question what to do with probes that have only a Unique Local IPv6 Unicast Address (ULA) [RFC4193] as their IPv6 address. The question is whether to treat those probes as IPv6 capable or not. It is known that about 10% of the RIPE Atlas probes that have IPv6 addresses do not actually have IPv6 connectivity. This was documented by Stéphane Bortzmeyer in his RIPE Labs article "How Many RIPE Atlas Probes Believe They Have IPv6 (But Are Wrong)?" (https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-atlas-probes-bel…) As a way of dealing with this problem, the RIPE Atlas system now tags probes that have broken IPv6. Any probe that has an IPv6 address (other than link local) but cannot reach the global internet is tagged as "IPv6 Doesn't Work" (see https://atlas.ripe.net/docs/probe-tags/) At the moment, around 2800 probes are connected and have an IPv6 address. Of those probes, around 350 (12.5%) are tagged that IPv6 doesn't work. Of those 350 probes, 114 have the surprising condition that the connect system call fails immediately with the error 'Network is unreachable.' Those 114 probes have two things in common, they have only a ULA address and the do not have a default route. It is the lack of default route that causes the connect system call to fail immediately. This feature (ULA and no default route) is specified in RFC-7084 (IPv6 CE Router Requirements) requirement ULA-5 ("An IPv6 CE router MUST NOT advertise itself as a default router with a Router Lifetime greater than zero whenever all of its configured and delegated prefixes are ULA prefixes.") The surprising thing is that for some probes this condition persists for many months. For the Atlas project, the question is how we should treat these probes. Currently they are regarded as having broken IPv6 connectivity. However, an alternative is to consider those probes as having no IPv6 at all. Broader questions are: are CPEs doing the right thing here. Should a CPE announce a ULA on the local LAN even if there hasn't been any IPv6 internet connectivity for a very long time? It is already complex enough for normal users to understand that there is always a link local IPv6 address even if there is no IPv6 connectivity. Now we have to add ULA to that group as well. So the question to the community, should RIPE Atlas treat ULAs in the same way as RFC-1918, addresses that should be ignored unless a valid global address can be found elsewhere. Or should we keep the current approach where ULAs are treated just like other global IPv6 addresses and consider the probe host's network setup to be broken? Philip

15 31

Paris-traceroute flow identifier
by Ibrahim Coskun 26 Mar '15

26 Mar '15

Hello, This is Ibrahim Ethem Coskun from University of Nevada, Reno. I'm currently working on an Internet Measurement project with Professor Mehmet Hadi Gunes. We are modifying paris-traceroute's source code and set the flow identifier of each packet (both sending and returning packets) to a constant value for every traces. So that, we want a trace to follow the same path whenever we traceroute the same target. However, I get the below warning messages from each probe : paris-traceroute -T 500 -i -l -M 5 -p icmp -r 44000 -a hopbyhop -n " + target_ip [WARN](TracertImpl.cc, 335)ICMP reserved words 0 0 0 0 0 [WARN](TracertImpl.cc, 330)Bad return flow id 0xd24e from 4.69.152.80 So, what does this warning mean, I checked the source code but couldn't find and information regarding this issue, I also email paris-traceroute team, but no responses. I googled my question and found a similar question emailed to to you ( https://www.ripe.net/ripe/mail/archives/ripe-atlas/2012-July/000534.html). I would be very pleased if you can answer my question. Thank you;

2 1

FranceIX ( Paris, France) has joined RIPE Atlas Anchors
by Alastair Strachan 26 Mar '15

26 Mar '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called fr-par-as57734 and it is hosted by FranceIX in Paris, France. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

CarrierColo / IPB GmbH in (Berlin, Germany) has joined RIPE Atlas Anchors
by Alastair Strachan 25 Mar '15

25 Mar '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-ber-as20647 and it is hosted by CarrierColo / IPB GmbH in Berlin, Germany. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Feedback about the new webinterface
by Klaus Darilion 20 Mar '15

20 Mar '15

Hi! First, thanks for the new web interface. I really like how you show the most important parts of the results, e.g. decoding the NSID for DNS measurements, and showing the traceroute with editable geolocation. Nevertheless I have some feedback: On https://atlas.ripe.net/probes/, when I search for probes matching "6939", I get the results in a list view of matching probes. In the list view, I can see the probe's ASN. But when the result set is small (e.g. 2 probes only), I do not get a "list view" but view with bigger "thumbnails", but missing the ASN information. Also viewing the details of a probe does not reveal the probes ASN. Similar with IP addresses. When viewing the results of a measurement on the map, if a click on a probe I get the probe's IP addresses. But when watching a probe's details I can not see the IP addresses of the probe. For me it is strange to get the probe's IPs and ASN not when watching the probe's details. This is quite some interesting info when selecting probes or when analyzing why the result from a certain probe was bad. Thanks Klaus

1 0

SwissIX Internet Exchange (Glattbrugg, Switzerland) has joined RIPE Atlas Anchors
by Alastair Strachan 19 Mar '15

19 Mar '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called ch-gtg-as20612 and it is hosted by SwissIX Internet Exchange in Glattbrugg, Switzerland Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Exact semantics of DNS' use_probe_resolver
by Stephane Bortzmeyer 17 Mar '15

17 Mar '15

The DNS-specific option use_probe_resolver is mentioned in <https://atlas.ripe.net/docs/measurement-creation-api/> but with little indication of the semantics. My experience is that some probes (with the default retry=0) return several responses, with the same "prb_id", but different "from". I assume it means the probe had several resolvers configured and tried them all. Am I correct? It may question some conclusions of <https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-ripe-atlas-probe…>. Is there an option to switch to the more typical behaviour of a DNS client (try the first resolver configured and switch to the second if the first does not reply)?

2 2

Visualising RIPE Atlas Anchor Measurements
by Vesna Manojlovic 17 Mar '15

17 Mar '15

Dear colleagues, Salim Gasmi, one of the RIPE Atlas anchor hosts, visualised the measurements collected by the RIPE Atlas anchor. This monitoring page is publicly available and allows to analyse topology changes and helps debugging network issues. Please find more details on RIPE Labs: https://labs.ripe.net/Members/salim_gasmi/visualising-ripe-atlas-anchor-mea… Kind regards, Vesna

1 0

Re: [atlas] Please set your NIC handle for your RIPE Atlas anchor
by Paul Vlaar 17 Mar '15

17 Mar '15

Dear RIPE Atlas staff, I'm a little confused. I need to add a NIC handle, you say. "What is a NIC handle? A NIC handle is the unique identifier of a person. It is basically the person's unique ID and it helps to keep different people with the same name apart from each other. Whenever a person object is referenced in another object, they are referenced by their NIC handle ("nic-hdl:") and not by their name. See an example person object" How can a handle meant for a person be used for a machine? Is this correct? Thanks, Paul Vlaar Afilias On 11/3/15 12:59 PM, RIPE Atlas (no reply) wrote: > Dear Paul Vlaar, > > We noticed that you haven't added the NIC handle for your RIPE Atlas > anchor yet. Could you please add it as soon as possible? > > NIC handles are objects in the RIPE Database that contain contact > information. Having this information available for all anchors will > make it easier for other anchor hosts or members of the community to > communicate with one another by finding the appropriate technical or > administrative contacts. > > If you don't already have a NIC handle, you can learn more about what > it is and how to create one in the RIPE Database here: > http://www.ripe.net/lir-services/new-lir/first-steps-as-a-ripe-ncc-member#c… > > > Once you have a NIC handle, you can enter it on the RIPE Atlas > website under “My Atlas” > “Anchors” > "View". > > For any questions or issues with the creation of your NIC handle, > please contact ripe-dbm(a)ripe.net. > > Kind regards, > > Michela Galante RIPE Atlas Team RIPE NCC atlas(a)ripe.net > -- Paul Vlaar DNS Infrastructure Group Afilias e-mail: pvlaar(a)afilias.info phone: +1-416-673-4078

2 2

Re: [atlas] Probe #1047
by Ben Vaux 16 Mar '15

16 Mar '15

I had my Probe drop out a few times, I replaced the Apple USB Power Supply with a new one and it seem better now. Best regards, Ben Vaux From: Ben Choy <ben.choy(a)hkirc.hk> Date: Friday, 13 March 2015 06:16 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Probe #1047 Dear RIPE, Our probe #1047 has been playing up lately eg. keep dropping out after a few hours even after power cycle. Any chance of getting a replacement if we sent it back. BTW, it is one of the “Old” v1. Cheers. Benjamin ChoyProject Manager (System & Network)Hong Kong Internet Registration Corporation Limited (HKIRC) http://www.hkirc.hk <http://www.hkirc.hk/> http://互聯網註冊.香港 <http://互聯網註冊.香港/> Hong Kong Domain Name Registration Company Limited (HKDNR) http://www.hkdnr.hk <http://www.hkdnr.hk/> http://域名註冊.香港 <http://域名註.香港/> Tel: +852 2319 1313 / Fax: +852 2319 2626 / Direct: +852 2319 3819 / Email: ben.choy(a)hkirc.hk <http://www.hkirc.hk/> The information in this email is confidential and may be legally privileged. If you are not the intended recipient, please notify the sender immediately and then delete this e-mail entirely. You must not retain, copy, distribute or use this e-mail for any other purpose not intended by this email or disclose any of its content to others. The recipient should check the email and attachment for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.PROTECT OUR ENVIRONMENT - think before printing!

1 0

Probe #1047
by Ben Choy 13 Mar '15

13 Mar '15

Dear RIPE, Our probe #1047 has been playing up lately eg. keep dropping out after a few hours even after power cycle. Any chance of getting a replacement if we sent it back. BTW, it is one of the “Old” v1. Cheers. [hkirc] Benjamin Choy Project Manager (System & Network) Hong Kong Internet Registration Corporation Limited (HKIRC) http://www.hkirc.hk<http://www.hkirc.hk/> http://互聯網註冊.香港<http://互聯網註冊.香港/> Hong Kong Domain Name Registration Company Limited (HKDNR) http://www.hkdnr.hk<http://www.hkdnr.hk/> http://域名註冊.香港<http://域名註.香港/> Tel: +852 2319 1313 / Fax: +852 2319 2626 / Direct: +852 2319 3819 / Email: ben.choy(a)hkirc.hk [cid:image002.png@01CEAE2D.C3DA7B80]<http://www.hkirc.hk/> The information in this email is confidential and may be legally privileged. If you are not the intended recipient, please notify the sender immediately and then delete this e-mail entirely. You must not retain, copy, distribute or use this e-mail for any other purpose not intended by this email or disclose any of its content to others. The recipient should check the email and attachment for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. PROTECT OUR ENVIRONMENT - think before printing!

1 0

Internet Exchange Nepal (NPIX) has joined RIPE Atlas anchors
by Michela Galante 10 Mar '15

10 Mar '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called np-ktm-as45170 and it is hosted by the Internet Exchange Nepal (NPIX) in Kathmandu, Nepal, and sponsored by APNIC. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas(a)ripe.net

1 0

Mistakenly sent "please register your probe" emails
by Robert Kisteleki 05 Mar '15

05 Mar '15

Dear RIPE Atlas users, As part of our regular development schedule, the development team rolled out a new version of the infrastructure components yesterday. As a side-effect, due to a mistake on our end, some users received emails urging them to register their probe(s), even though this has already been done. If you got such a mail although you've done your part, then please ignore this mail. Our apologies for the confusion. Regards, Robert Kisteleki

1 0

University of Twente (Enschede, The Netherlands) has joined RIPE Atlas Anchors
by Alastair Strachan 27 Feb '15

27 Feb '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called nl-ens-as1133 and it is hosted by University of Twente in Enschede, The Netherlands Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

some probes not returning NSID
by Paul Vlaar 26 Feb '15

26 Feb '15

Hi all, it appears that some probes never return NSID, when requested, while others do, for the same query. For example: https://atlas.ripe.net/measurements/1875836/#!general As you can see NSID is set to True. These are the raw results from the two probes, for a one-off DNS UDM: results = { u'6012': [{u'lts': 230, u'proto': u'UDP', u'from': u'193.0.19.108', u'msm_id': 1875836, u'af': 4, u'timestamp': 1424384037, u'fw': 4670, u'msm_name': u'Tdig', u'prb_id': 6012, u'result': {u'abuf': u'OQGEAAABAAEAAAABA29yZwAABgABwAwABgABAAADhAAzAmEwA29yZwthZmlsaWFzLW5zdARpbmZvAANub2PAKHfjQ2sAAAcIAAADhAAJOoAAAVGAAAApEAAAAAAAACUAAwAhbnMwMDBiLmFwcDcubnJ0MS5hZmlsaWFzLW5zdC5pbmZv', u'rt': 312.971, u'NSCOUNT': 0, u'QDCOUNT': 1, u'answers': [{u'RNAME': u'noc.afilias-nst.info.', u'NAME': u'org.', u'MNAME': u'a0.org.afilias-nst.info.', u'TTL': 900, u'SERIAL': 2011382635, u'TYPE': u'SOA'}], u'ID': 14593, u'ARCOUNT': 1, u'ANCOUNT': 1, u'size': 132}, u'src_addr': u'193.0.19.108', u'group_id': 1875836, u'type': u'dns', u'dst_addr': u'199.19.56.1'}], u'10039': [{u'lts': 166, u'proto': u'UDP', u'from': u'96.237.232.254', u'msm_id': 1875836, u'af': 4, u'timestamp': 1424384040, u'fw': 4670, u'msm_name': u'Tdig', u'prb_id': 10039, u'result': {u'abuf': u'qxGAgAABAAEAAAABA29yZwAABgABwAwABgABAAAB3QAzAmEwA29yZwthZmlsaWFzLW5zdARpbmZvAANub2PAKHfjQ2UAAAcIAAADhAAJOoAAAVGAAAApD6AAAAAAAAA=', u'rt': 8.299, u'NSCOUNT': 0, u'QDCOUNT': 1, u'answers': [{u'RNAME': u'noc.afilias-nst.info.', u'NAME': u'org.', u'MNAME': u'a0.org.afilias-nst.info.', u'TTL': 477, u'SERIAL': 2011382629, u'TYPE': u'SOA'}], u'ID': 43793, u'ARCOUNT': 1, u'ANCOUNT': 1, u'size': 95}, u'src_addr': u'192.168.13.40', u'group_id': 1875836, u'type': u'dns', u'dst_addr': u'199.19.56.1'}] } Sagan tells me, for probe 6012, responses[0].abuf.raw_data is: {'HEADER': {'AA': True, 'QR': True, 'AD': False, 'NSCOUNT': 0, 'QDCOUNT': 1, 'ANCOUNT': 1, 'TC': False, 'RD': False, 'ARCOUNT': 1, 'CD': False, 'ReturnCode': 'NOERROR', 'OpCode': 'QUERY', 'RA': False, 'Z': 0, 'ID': 14593}, 'AnswerSection': [{'Retry': 900, 'Name': u'org.', 'NegativeTtl': 86400, 'Refresh': 1800, 'MasterServerName': u'a0.org.afilias-nst.info.', 'Expire': 604800, 'MaintainerName': u'noc.afilias-nst.info.', 'TTL': 900, 'Serial': 2011382635, 'Type': 'SOA', 'Class': 'IN', 'RDlength': 51}], 'QuestionSection': [{'Qclass': 'IN', 'Qtype': 'SOA', 'Qname': u'org.'}], 'EDNS0': {'ExtendedReturnCode': 0, 'Option': [{'OptionCode': 3, 'OptionName': 'NSID', 'NSID': u'ns000b.app7.nrt1.afilias-nst.info', 'OptionLength': 33}], 'UDPsize': 4096, 'Version': 0, 'Z': 0, 'Type': 'OPT', 'Name': u'.'}} NSID is present. And for 10039: {'HEADER': {'AA': False, 'QR': True, 'AD': False, 'NSCOUNT': 0, 'QDCOUNT': 1, 'ANCOUNT': 1, 'TC': False, 'RD': False, 'ARCOUNT': 1, 'CD': False, 'ReturnCode': 'NOERROR', 'OpCode': 'QUERY', 'RA': True, 'Z': 0, 'ID': 43793}, 'AnswerSection': [{'Retry': 900, 'Name': u'org.', 'NegativeTtl': 86400, 'Refresh': 1800, 'MasterServerName': u'a0.org.afilias-nst.info.', 'Expire': 604800, 'MaintainerName': u'noc.afilias-nst.info.', 'TTL': 477, 'Serial': 2011382629, 'Type': 'SOA', 'Class': 'IN', 'RDlength': 51}], 'QuestionSection': [{'Qclass': 'IN', 'Qtype': 'SOA', 'Qname': u'org.'}], 'EDNS0': {'ExtendedReturnCode': 0, 'Option': [], 'UDPsize': 4000, 'Version': 0, 'Z': 0, 'Type': 'OPT', 'Name': u'.'}} NSID is missing. Why is this? I've tried increasing the payload size, this makes no difference. I get the same when I try for SOA . @ k.root-servers.net: Compare these outcomes: https://atlas.ripe.net/measurements/1875933/ https://atlas.ripe.net/measurements/1875926/ It appears to me that probe 10039 (or its network) has a problem of sorts, causing this. It would be great if faulty probes can be weeded out, if this is really the case. BTW, I am always getting "null" on the NSID field in the web interface, regardless of whether it lives in abuf, or not. This seems to be a bug. ~paul

9 15

[ietf-secretariat@ietf.org: New Non-WG Mailing List: hops -- Measuring deployability of new transport protocols]
by Stephane Bortzmeyer 26 Feb '15

26 Feb '15

It could be interesting to use Atlas probes for such measurements, no?

2 1

Re: [atlas] Fwd: Re: Proble locations (Changed because of Geo-IP)
by Chris Amin 25 Feb '15

25 Feb '15

Dear Martin, I'm sorry for this, we recently made a change which keeps the location of those probes which are geolocated (i.e. *without* a manually set address) up to date. Previously such probes were geolocated once, and never again. It was never the intention to overwrite manually given locations. Unfortunately, it seems that a number of probes were erroneously marked as being automatically geolocated when in fact their owners had carefully provided a location. We are now looking at our logs to see how many probes might have been affected by this, and whether we can automatically revert the location in those cases. As for your point about not being able to enter the location, there is a text box above the map popup which should allow you to enter a textual address. If this isn't working for you, please let me know. Apologies once again. Kind regards, Chris Amin RIPE NCC On Wed, 25 Feb 2015 01:10:30 -0800 (PST), Martin Winter wrote: > I have actually the address in it. > The earlier webpage had a way to enter Lat/Lon for probes (which I can't > find anymore). > > I think a simple Geo-Lokup based on addresses in description would have > done a much better job. > But a field to enter lat/lon in it and take this as a preference (if > entered) without going to overwrite it would be a good start. > > I mainly worry on whatever happend there in this process may have > misplaced a lot of probes to the wrong location. > Anyone else noticed that their probe moved to a new (wrong) location? > > - Martin > > > On Wed, 25 Feb 2015, Grewal, Jas wrote: > >> Agreed, how about including this critical information in the >> description field to get around this, perhaps? >> >> -----Original Message----- >> From: ripe-atlas [mailto:ripe-atlas-bounces@ripe.net] On Behalf Of >> Martin Winter >> Sent: 25 February 2015 07:29 >> To: ripe-atlas(a)ripe.net >> Subject: [atlas] Proble locations (Changed because of Geo-IP) >> >> So I've noticed that (at least some) probes got the location >> automatically updated based on Geo IP. >> However, this is frequently fundamentially broken. One of my probe >> moved from San Jose, CA to somewhere in the middle of Texas. (Broken >> Geo-IP location for AT&T DSL users). >> (The example I talk about is proble #10770) >> >> Kind of sad... not sure how many had this happening. Specially as I >> took care to put the exact lat/lon in the User interface in the past. >> Now I can only reposition it by dragging on a map - and that seems to >> be broken as well (at least it fails to save when I try to correct >> this probes location on Chrome) >> >> I wonder how many and why there was a decision to change the location. >> I think the location were much better before they got force-changed. >> >> - Martin Winter >> >> >> >> > > > > >

2 1

FastVPS Eesti OU (Jõhvi, Estonia) has joined RIPE Atlas Anchors
by Alastair Strachan 25 Feb '15

25 Feb '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called ee-jvi-as198068 and it is hosted by FastVPS Eesti OU in Jõhvi, Estonia. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Delta Softmedia Ltd (Sofia, Bulgaria) has joined RIPE Atlas Anchors
by Alastair Strachan 25 Feb '15

25 Feb '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called bg-sof-as197216 and it is hosted by Delta Softmedia Ltd in Sofia, Bulgaria. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Proble locations (Changed because of Geo-IP)
by Martin Winter 25 Feb '15

25 Feb '15

So I've noticed that (at least some) probes got the location automatically updated based on Geo IP. However, this is frequently fundamentially broken. One of my probe moved from San Jose, CA to somewhere in the middle of Texas. (Broken Geo-IP location for AT&T DSL users). (The example I talk about is proble #10770) Kind of sad... not sure how many had this happening. Specially as I took care to put the exact lat/lon in the User interface in the past. Now I can only reposition it by dragging on a map - and that seems to be broken as well (at least it fails to save when I try to correct this probes location on Chrome) I wonder how many and why there was a decision to change the location. I think the location were much better before they got force-changed. - Martin Winter

2 2

New on RIPE Labs: Stopping Support for Internet Explorer 8 on Windows XP in RIPE Atlas and RIPEstat
by Mirjam Kuehne 24 Feb '15

24 Feb '15

Dear colleagues, Microsoft ended support for Windows XP as of April 2014. We're about to change RIPE Atlas and RIPEstat to stop support for Internet Explorer 8 running on these systems. Please find some more information on RIPE Labs: https://labs.ripe.net/Members/kistel/stopping-support-for-internet-explorer… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Brno University of Technology (CZ) has joined RIPE Atlas anchors
by Vesna Manojlovic 20 Feb '15

20 Feb '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called cz-brq-as197451 and is hosted by Brno University of Technology in Czech Republic. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0

Sagan: 'Response' object has no attribute 'edns0'
by Paul Vlaar 18 Feb '15

18 Feb '15

Hi all, I'm trying to do some basic DNS UDM result parsing using Sagan. I'd like to have an easy way to extract the NSID. I followed the instruction found here: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2014-May/001475.html 'from ripe.atlas.sagan import Result result = Result("your-JSON-result-blob-here") print(result.responses[0].edns0.options[0].nsid)' That didn't work, as I get: AttributeError: 'Result' object has no attribute 'responses' So I figured I need to use a DnsResult, instead. I then have the following Python code: from ripe.atlas.sagan import DnsResult import json url = "https://atlas.ripe.net/api/v1/measurement-latest/1873691/" results = json.load(urllib.urlopen(url)) for probe in results: sagan_result = DnsResult(results[probe][0]) print(sagan_result.responses[0].edns0.options[0].nsid) This gives me: print(sagan_result.responses[0].edns0.options[0].nsid) AttributeError: 'Response' object has no attribute 'edns0' After some digging through the Sagan documentation, I found out that the way to do this should be: print(sagan_result.responses[0].abuf.edns0.options[0].nsid) This might be of help to others. ~paul

1 0

problems creating measurements with old web interface
by Klaus Darilion 13 Feb '15

13 Feb '15

Hi! Today I created some DNS tests with the old web interface. The creation process was fine, but the measurements did not work. (my target was ignored and "use probe's resolver" was automatically enabled). See UDMs: 1841832, 1841839, 1841840 btw: I can not stop 1841839 and 1841840 via the new web interface The DNS measurements only work if I create them via the new web interface. regards Klaus PS: IMO the new web interface is not very user friendly when choosing the probes - eg I failed to select 100 probes word wide (how to do this in the map)? It would be nice to have a textual alternative as my browser gets incredibly slow when showing all the probes on the map.

2 3

Larsen Data ApS (Ballerup, Denmark ) has joined RIPE Atlas Anchors
by Alastair Strachan 12 Feb '15

12 Feb '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called dk-blp-as197495 and it is hosted by Larsen Data ApS based in Ballerup, Denmark. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Globalways AC (Frankfurt, Germany ) has joined RIPE Atlas Anchors
by Alastair Strachan 12 Feb '15

12 Feb '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-fra-as48918 and it is hosted by Globalways AC based in Frankfurt, Germany. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Globalways AC (Stuttgart, Germany ) has joined RIPE Atlas Anchors
by Alastair Strachan 12 Feb '15

12 Feb '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-str-as48918 and it is hosted by Globalways AC based in Stuttgart, Germany. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

MacOSX: probe add problems (create measurements)
by Hendrik Visage 12 Feb '15

12 Feb '15

Goodday, I'm trying to add some new measurements, but the probe selection's "+New Set - Manual" and "+Reuse a set from an old Measurement" both just flash the screen, looks like it opens a drop down windows, and closes it before I could even blink my eyes. This was tested on the Firefox 35.0.1 as well as on Safari 7.0.3 on MacOSX 10.9.3. Hendrik

2 1

Fwd: SEE4/RIPE NCC Regional Meeting: Registration Open!
by Vesna Manojlovic 09 Feb '15

09 Feb '15

Dear RIPE Atlas users, do you want to share your experiences with using RIPE Atlas with the community on "Balkans"? Please submit your talks - and see you there! Regards, Vesna -------- Forwarded Message -------- Subject: SEE 4/RIPE NCC Regional Meeting: Registration Open! Date: Mon, 26 Jan 2015 11:21:05 +0100 From: SEE <seeurope(a)ripe.net> To: ripe-list(a)ripe.net Dear colleagues, The fourth RIPE NCC Regional Meeting/South East Europe Meeting (SEE 4) takes places in Belgrade at the Metropol Palace Hotel on 21-22 April 2015. Join us there! The SEE 4/RIPE NCC Regional Meeting is open to everyone and attendance is free of charge. You can register for this meeting at: http://www.ripe.net/see-4/registration This meeting will build on the success of past meetings, which took place in Dubrovnik, Skopje and Sofia. These meetings demonstrated how vibrant the Internet community in the region is, as well as the knowledge-sharing and network-building benefits to be gained from meeting as a community. The meeting will cover a wide range of topics, including: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Efforts to establish IXPs in the region - Reports from existing IXPs - Regional success stories - Much, much more! Do you have expertise on some of these topics? An interesting case to share with your peers? Then please submit a presentation proposal here: https://www.ripe.net/ripe/meetings/regional-meetings/see-4/cfp Further information about the meeting can be found at: http://www.ripe.net/see4 See you there! Kind regards, Gergana -- Gergana Petrova Conference Coordinator RIPE Network Coordination Centre Singel 258, 1016 AB Amsterdam, The Netherlands T: +31 20 535 4444 www.ripe.net

1 0

Bug? RIPE Atlas interface mixing up legacy IP addresses
by Dan Luedtke 06 Feb '15

06 Feb '15

Hi all, I encountered some odd behaviour today using the Atlas web interface. It mixed up the octets of a legacy IP address in a funny way. Is this a bug? The corresponding probe seems to be down now /0\ I made a screen cap to document it. It was reproducible, but I am not sure if I broke it or if it is a general bug. —> http://youtu.be/Bhnyd9ogyNs Cheers Dan

2 2

Web Werks (IN) has joined RIPE Atlas anchors
by Michela Galante 02 Feb '15

02 Feb '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called in-bom-as33480 and it is hosted by Web Werks in Mumbai, India, and sponsored by APNIC. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas(a)ripe.net

2 1

Glitch in measurements today?
by Stephane Bortzmeyer 31 Jan '15

31 Jan '15

Many: {u'id': 7, u'name': u'Failed'} when querying measurements. It seems OK, now.

1 0

Implementing new RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 30 Jan '15

30 Jan '15

Dear colleagues, As agreed on the MAT-WG mailing list, we are in the process of implementing the new RIPE Atlas Service Terms and Conditions that clearly state the role and responsibilities for the RIPE NCC, RIPE Atlas hosts and users: https://atlas.ripe.net/legal/terms-conditions/ This is the implementation plan: - End of January, existing probe hosts will be notified by email about the upcoming transition to the new terms and conditions. - From next week (during February), existing users and probe hosts will be presented with a banner when they log in to the RIPE Atlas website, to inform them of the upcoming transition. - As of 2 March 2015, the new RIPE Atlas Service Terms and Conditions will come into effect; new probe hosts will be asked to agree to the new terms and conditions when applying for a probe; all existing probe hosts will be subject to the new terms and conditions. Thank you for your feedback and for helping us to refine these new terms. Regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 1

Hitech Service LLC (Kiev, Ukraine) has joined RIPE Atlas Anchors
by Alastair Strachan 27 Jan '15

27 Jan '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called ua-iev-as29632 and it is hosted by Hitech Service LLC in Kiev, Ukraine). Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

VNET a.s. (Bratislava, Slovakia) has joined RIPE Atlas Anchors
by Alastair Strachan 23 Jan '15

23 Jan '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called sk-bts-as29405 and it is hosted by VNET a.s. in Bratislav, Slovakia. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Proposal for public HTTP measurements
by Robert Kisteleki 22 Jan '15

22 Jan '15

Dear RIPE Atlas users, The topic of publicly available HTTP measurements in RIPE Atlas comes up from time to time. There were a number of discussions about pros and cons for this feature over the years (including exposing probe hosts to unnecessary risks of other users "measuring" just about any kind of HTTP content out there), with no firm outcome. While we understand that this feature would come handy for some of our users, it does not benefit everyone. Therefore our proposal is the following: 1. We'll enable HTTP measurements to be performed by all atlas users, from any probes. 2. The targets of such measurements can only be RIPE Atlas anchors (these already run HTTP servers, see https://atlas.ripe.net/docs/anchors/). 3. Parameters like costs, minimum frequency, maximum number of probes involved, etc. will be set by the development team, just as with the other measurements. 4. The RIPE NCC will still be able to support other, vetted HTTP measurements as long as it benefits the community, as well as other HTTP measurements that we deem operationally useful. These will be evaluated on a case by case basis. Please speak up at the MAT working group list (mat-wg(a)ripe.net) if you support / don't support this proposal, of if you have any other opinion about it. Regards, Robert Kisteleki RIPE NCC R&D manager, for the RIPE Atlas team

10 15

Re: [atlas] problems creating measurements with old web interface
by Massimo Candela 21 Jan '15

21 Jan '15

Hi, Thanks for the feedback! > > Subject: [atlas] problems creating measurements with old web interface > Date: Wed, 21 Jan 2015 13:49:48 +0100 > From: Klaus Darilion <klaus.mailinglists(a)pernau.at> > To: ripe-atlas(a)ripe.net > > Hi! > > Today I created some DNS tests with the old web interface. The creation > process was fine, but the measurements did not work. (my target was > ignored and "use probe's resolver" was automatically enabled). > See UDMs: 1841832, 1841839, 1841840 > > btw: I can not stop 1841839 and 1841840 via the new web interface > > > The DNS measurements only work if I create them via the new web interface. > > > regards > Klaus > > PS: IMO the new web interface is not very user friendly when choosing > the probes - eg I failed to select 100 probes word wide (how to do this > in the map)? You can do it by searching for “worldwide” (there is autosuggestion) and the widget will ask the number of probes and the tags you want to use. The number of probes is suggested and bounded according to the maximum number of probes selectable for the measurement. The idea is that whatever you write in the text field, it will try to help/guide you creating the valid (and, if needed, complex) selection you were looking for. E.g. you can do a combination by searching for “Canada ipv6” to select all the ipv6 probes in Canada Of course it can be improved, so let us know if you have other feedback! Best regards, Massimo > It would be nice to have a textual alternative as my > browser gets incredibly slow when showing all the probes on the map. > > > >

1 0

One hundred RIPE Atlas anchors online
by Vesna Manojlovic 16 Jan '15

16 Jan '15

Dear all, You have been hearing about each RIPE Atlas anchor as they get activated - and now we have reached a milestone with one hundred anchors online! We wrote an article on RIPE Labs to cover all the details: https://labs.ripe.net/Members/suzanne_taylor_muzzin/one-hundred-ripe-atlas-… To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0

DK Hostmaster A/S (Ballerup, Denmark) has joined RIPE Atlas Anchors.
by Alastair Strachan 14 Jan '15

14 Jan '15

Dear RIPE Atlas users, We're very excited to announce that the 100th RIPE Atlas anchor has joined the network! This anchor is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called dk-blp-as39839 and it is hosted by DK Hostmaster A/S in Ballerup, Denmark. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Nordiska Servercentralen (Solna, Sweden) has joined RIPE Atlas Anchors.
by Alastair Strachan 13 Jan '15

13 Jan '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called se-sln-as49515 and it is hosted by Nordiska Servercentralen in Solna, Sweden. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Deprecating the old measurement UI
by Robert Kisteleki 09 Jan '15

09 Jan '15

Dear all, In October last year, we introduced a new UI for browsing and scheduling measurements. For details, see: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-new-measurem… Your feedback about this was predominantly positive, and we’d like to thank everyone who helped this development with suggestions and bug reports. As stated at the time, we plan to deprecate and eventually remove the old interface (both the UI and the "API" it used). Our timeline is the following: 1. We'll make the new UI the default, and remove links to the old UI from the RIPE Atlas main menu, around 21 January. The old pages will still be accessible if one reaches them from somewhere else, such as a browser bookmark or hard-coded scripts. 2. Around the beginning of March, we'll remove the old pages from the system (/atlas/udm.html and related pages). This step will include the "deep links" that some of our users directly access to schedule and manage measurements from scripts (notably /atlas/*udm*.json). We'd like to encourage all of our users to switch to the new UI and API in the following weeks, if you haven't already done so. As always, we're happy to answer any questions or hear any feedback you might have. Regards, Robert Kisteleki, for the RIPE Atlas team

1 0

Coming soon: RIPE Atlas data visualization hackathon!
by Vesna Manojlovic 08 Jan '15

08 Jan '15

Dear all, we are happy to invite you to the first RIPE Atlas open data hackathon! In short: various groups will come together during the long weekend in Amsterdam, to make new visualisations (or modify existing ones) based on RIPE Atlas data, and to give that SW back to the community. We are inviting: programers, designers, operators, data-lovers, hackers, students... help us spread the word! Comcast is generously offering prizes and some coverage for travel expenses for several people -- to be awarded/selected by a jury. Dates: 27-28-29 March 2015 (Friday to Sunday) How to apply: https://www.ripe.net/s/XUJy More information, as always, in the RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-hackathon-20… Hope to see you there! Regards, Vesna

1 1

Open IP Map, crowdsourced geolocation
by d.baeza＠tvt-datos.es 28 Dec '14

28 Dec '14

Hi All! I know is in Beta, but only say when I try to submit[ok button] a Geolocation of a IP/Hostname, it keeps "loading" forever. Should I use any special set of code? Im trying City,Province,XX (XX = Country Code, in my case: ES) Thanks in advance! --Daniel

2 3

Sharing measurement
by Lukasz Trabinski 23 Dec '14

23 Dec '14

hi It's possible to share (graphical) measurement from my ripe probe without login to my account?

4 7