- mat-wg - mailman.ripe.net

atlas vs nlring data available
by Randy Bush 06 Nov '14

06 Nov '14

From: Thomas Holterbach <thomasholterbach(a)gmail.com> > did you hear daniel karrenberg on making the data public? Yes, the data of the first experiment is already public and available on http://psg.com/~thomas/ Tomorrow I'll add the data of the second experiment.

1 0

Atlas Light Map
by Daniel Karrenberg 05 Nov '14

05 Nov '14

In the meeting George Michaelson referred to the light maps from space that were part of the the inspiration for RIPE Atlas as shown in http://www.slideshare.net/ripencc/ripe-atlas-a-real-big-measurement-network… Attached is a map of the RIPE Atlas probes in a similar colour scheme which I did a couple of months ago. It is large, you can zoom in. I leave it to your judgement how similar these are. Personally I am amazed how how well one can see things around Europe. Daniel

1 0

Atlas Sagan library and UDP tarceroute results: bug or feature?
by Jen Linkova 31 Oct '14

31 Oct '14

Hello, I've just found that using Sagan library for analyzing UDP traceroute measurement results may produce incorrect results: 'target_responded' variable is not be set to 'True' if the source address of the traceroute reply is not the target address of the traceroute, but any other address that belongs to the node. (From the traceroute.py code: def target_responded(self): if self._target_responded is not None: return self._target_responded self._target_responded = False if self.hops and self.hops[-1].packets: destination_address = IP(self.destination_address) for packet in self.hops[-1].packets: if packet.origin and destination_address == IP(packet.origin): self._target_responded = True return self.target_responded ) I don't think that's a valid assumption that a target node is *always* choosing the probe packet's destination address as a reply source. In particular, in case of UDP packets addressed to anycast, it might fail because the node can reply from another address. In particular, rfc4443 (ICMP for IPv6) says: 2.2. Message Source Address Determination A node that originates an ICMPv6 message has to determine both the Source and Destination IPv6 Addresses in the IPv6 header before calculating the checksum. If the node has more than one unicast address, it MUST choose the Source Address of the message as follows: (a) If the message is a response to a message sent to one of the node's unicast addresses, the Source Address of the reply MUST be that same address. (b) If the message is a response to a message sent to any other address, such as - a multicast group address, - an anycast address implemented by the node, or - a unicast address that does not belong to the node the Source Address of the ICMPv6 packet MUST be a unicast address belonging to the node. == and in the same RFC source address selection for ICMP echo reply messages is defined: The source address of an Echo Reply sent in response to a unicast Echo Request message MUST be the same as the destination address of that Echo Request message. An Echo Reply SHOULD be sent in response to an Echo Request message sent to an IPv6 multicast or anycast address. In this case, the source address of the reply MUST be a unicast address belonging to the interface on which the Echo Request message was received. ==== So, I'm sending this email, first, to warn those of you who is using Sagan to analyze UDP traceroute results, and, secondly, to discuss, if Sagan behavior is a bug (I believe it is) or a feature ;) -- SY, Jen Linkova aka Furry

1 0

New on RIPE Labs: Data Streaming in RIPE Atlas
by Mirjam Kuehne 31 Oct '14

31 Oct '14

Dear colleagues, RIPE Atlas data is now available as a live data stream, opening the door to a host of new applications and use cases. You can read more about this new functionality on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/data-streaming-in-ripe-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Updated Draft RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 29 Oct '14

29 Oct '14

Dear colleagues, On September 15 we announced the draft of new Terms and Conditions for the RIPE Atlas service, and the implementation procedure: https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service In the meantime, we received feedback from the community and we’d like to thank you for your input. It was summarized here: https://www.ripe.net/ripe/mail/archives/mat-wg/2014-October/000498.html Based on that, we published second revision of the proposed document, available here: https://atlas.ripe.net/legal/terms-conditions-draft/ Summary of changes: - article 3.2: word "critical" replaced with "important" - new article 3.4: Users are required to register and maintain a valid email address and contact details in the RIPE Atlas Portal. - article 4.4: grammar about "email addresses of hosts" fixed - article 6.1: link to MoU added - articles 7.1 & 7.2: security checks specified as "reasonable" - article 10.1: clarified that this refers to other documents, by inserting "Without prejudice to Article 2.3 ..." Please review the document and post your comments to the list, or during MAT working group at the RIPE69 Meeting. After the meeting we will coordinate with Working Group chairs to have a final draft of the document circulated and publish our implementation plan as soon as we get the go ahead from working group chairs. Kind regards, Vesna Manojlovic Community Builder for Measurements Tools

1 0

New on RIPE Labs: New RIPE Atlas Measurements User Interface
by Mirjam Kuehne 28 Oct '14

28 Oct '14

Dear colleagues, We're very excited to announce an all-new user interface for RIPE Atlas measurements. Users can now schedule, monitor and manage their own customised measurements more efficiently than ever before, and can now make use of the tagging feature when selecting probes for use in those measurements. Learn more about the new features on RIPE Labs and let us know what you think: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-new-measurem… Kind regards, Mirjam Kuehne RIPE NCC

1 0

RIPE Atlas Value Proposition Published
by Kaveh Ranjbar 24 Oct '14

24 Oct '14

Dear colleagues, During its meeting in September, the RIPE NCC presented the RIPE NCC Executive Board with a value proposition document detailing the value that RIPE Atlas can bring to network operators, researchers and the Internet community as a whole. The board asked the RIPE NCC to publish this document, which is available on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-value-propos… We also plan to incorporate much of the document's content into the RIPE Atlas website so that RIPE Atlas users can clearly understand the different ways this global Internet measurement network can be used and the many unique benefits it provides. We hope you will find this document useful and that you may even be inspired to make use of RIPE Atlas in new ways. Kind regards, Kaveh Ranjbar Chief Information Officer RIPE NCC

1 0

Draft agenda for MAT @ RIPE69
by Christian Kaufmann 20 Oct '14

20 Oct '14

Hello All, This is the draft agenda for the Measurement, Analysis and Tools Working Group session at RIPE69: A. Introduction: Welcome, Scribe, Jabber, Agenda (5m) B. On the suitability of two large-scale Internet measurement platforms (20m) Randy Bush D. The value of WLAN measurements for the R&E Community (20m) Brook Schofield E. OpenIPMap (crowdsourcing Internet infrastructure geolocation) (10m) Emile Aben F. "RIPE Atlas #dataviz” (10m) Vesna Manojlovic G. Python and RIPE ATLAS (20m) APIVaibhav Bajpai Z. AOB Timings are approximate. The session will take place at 14:00 local time on Wednesday 5th November. We are looking forward to see you all in London, Richard & Christian

2 1

Community Feedback on Draft RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 07 Oct '14

07 Oct '14

Dear colleagues, On September 15 we announced the new draft of the Terms and Conditions for the RIPE Atlas service: https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service We received feedback from the community and we’d like to thank you for your input. Below is a summary of the main points raised and our response. ------------------------------- Security audits and user assistance ------------------------------- We were asked to clarify what is meant by “security audits and checks” and what “assistance” users would be obliged to provide. We will clarify this in the next draft. -------------------------------------- Contradiction between Articles 2.3 and 10.1 -------------------------------------- We were asked to clarify the perceived contradiction between Articles 2.3 and 10.1 about informing users about the future changes to the Terms and Conditions (T&C). There was a strong preference stated to actively alert users about upcoming changes. It was suggested to allow for a window of time after notification before changes are applied (e.g. 30 days). We will inform users about the upcoming T&C changes by email, as outlined in the “implementation timeline” (point #3) in the RIPE Labs article. In reference to the articles, Article 2.3 is about amendments to the T&Cs and Article 10.1 is about other RIPE Documents that are created using different procedures and include points of references for the T&Cs. ---------------------- Minor editorial changes ---------------------- We were given several minor editorial suggestions. We will review the suggested edits. --------------------------- Strong legalese in the T&C -------------------------- Some people raised concern about the “strong legalese” included in the updated T&Cs. The inclusion of those provisions is to align the T&Cs with the other legal documents of the RIPE NCC. We felt that the document should reflect the RIPE NCC’s operational practices and should clarify the mutual responsibilities and expectations of probe hosts and the RIPE NCC. The Terms and Conditions is a legal document and the rights and obligations between both parties should be clearly and fully stated. Unfortunately legalese cannot be avoided. We would like to thank you again for your input. If you have any other comments about the text or the implementation procedure, please let us know. Please let us know if you have any other comments on the text or the implementation procedure. Kind regards, Vesna Manojlovic Community Builder for Measurements Tools

1 0

Re: [mat-wg] [routing-wg] Fwd: [ARIN-consult] Consultation on New Experimental Allocation
by Emile Aben 06 Oct '14

06 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/08/14 12:51, Job Snijders wrote: > On Tue, Aug 05, 2014 at 12:38:17PM +0200, Emile Aben wrote: >> I'd like to inform you of an experiment we propose doing together with >> ARIN about the routability of prefixes longer than /24 out of ARINs >> 23.128.0.0/10 block. For more details see ARIN's announcement below. >> >> If people have any feedback on this, please let us know. > > I recommend testing with and without proper route: objects for the small > prefixes. > > As a service provider I would accept smaller than /24... If and only if > there is an exact route object for the prefix, other providers just > discard anything smaller than a /24, regardless of the existance of > proper route objects. Would be good to quantify this. We plan to start announcing a couple of prefixes from AS12654 within the next hour for the purpose of reachability checking of prefixes longer than /24 out of ARINs 23.128.0.0/10 block: With route object: prefix pingable IP 23.128.24.0/24 23.128.24.1 23.128.25.0/25 23.128.25.1 23.128.25.240/28 23.128.25.241 Without route object: prefix pingable IP 23.128.124.0/24 23.128.124.1 23.128.125.0/25 23.128.125.1 23.128.125.240/28 23.128.125.241 best regards, Emile Aben RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJULRhIAAoJEKxthF6wloMOuR4QAJys9r18hwmu8DsF2nr6mCje wjYoKcJP/AAl0vQpQLMhR70D9b9v5XQArcMyvzoXRqcFYTfz5yAy9rsOD1pWOE8r dz/XmTzp45fmTRBMbCgQNVA4FLhv0Iq9Qx2eVSWhgLGSTNRNM9oGUTOVvzaIZ551 hx0+dbexz6AO9LlHeeam+rulHsIrsXXeMHhuLz1yU/MkW+MEyadJPQqLpMjIvCBs 4ENPDe358J4SQVMi7Ur55mXaF8vCJ4lP9CXCzcSvEa+S+iuoN9+xrDC6+QPHPj8k 1ZWiSN903ESQBcTG+uX69GH0qHCD/ADYswL705GEayRhXh0VlCdUwkfBCZdYKRn/ KB5hvJ+xkXIA+2mlBJYuJDWs3WB9xZ4ijID6hEbyqfiX1TqNQy0qPPS5HWrkeZg6 UCVBDFvZnn39z7BOSNLvf3bSc1VWK2AikS+6pzyyd8i4Pdk7GVPxFnsHdfEwkRJz n7h0Vjn7MOrnS6Fy29dJ1E+HC3PlN+W1hE9j4vO3sGrKHEc9tIW9MZ8Wg35qKi5c oUp9wylYhkjl3YKHxtc4bUXwzQqdYa7sxXPKIX5yfYLa+0mIdnQgWqK2Rzd+/rAa JfNPCrgJkxUrd8Gut6OkaV5EhgojYfvrGe3qfZj9OvhG4SQcDjbTW24rdySjtMJS mADNKNND94MRp43ehre3 =bh0Q -----END PGP SIGNATURE-----

1 1

Call for Presentations at RIPE 69 in London
by Christian Kaufmann 06 Oct '14

06 Oct '14

Dear MAT WG, We co-chairs are beginning to put together the agenda for the MAT working group meeting on wednesday 5th November at RIPE 69 in London and there are still 3 slots left. If you have something you would like to present, please let us know no later than Friday, 17th October 2014. Thanks a lot, Richard Barnes and Christian Kaufmann MAT Co-Chairs

2 1

Re: [mat-wg] [dns-wg] Final Call For Presentations RIPE 69, deadline 1 October 2014
by Daniel Karrenberg 25 Sep '14

25 Sep '14

The correct link for the draft program is: https://ripe69.ripe.net/programme/meeting-plan/draft-programme/

1 0

Call For Presentations RIPE 69, deadline 31 August 2014
by Benno Overeinder 24 Sep '14

24 Sep '14

Dear colleagues, Please find the CFP for RIPE 69 in London below. The deadline for submissions is 31 August 2014. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, RIPE PC http://www.ripe.net/ripe/meetings/ripe-meetings/pc --------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 69 will take place from 3-7 November 2014 in London, UK. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 69. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - 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 Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at https://ripe69.ripe.net/submit-topic/presentation-formats/ Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for "lightning talks", which are selected immediately before or during the conference. The following general requirements apply: - Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 31 August 2014, using the meeting submission system at https://ripe69.ripe.net/submit-topic/guidelines/. Proposals submitted after this date will be considered on a space-available basis. - Lightning talks should also be submitted using the meeting submission system (https://ripe69.ripe.net/submit-topic/submission-form/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. - Presenters should indicate how much time they will require. See more information on time slot allocations per presentation format at https://ripe69.ripe.net/submit-topic/presentation-formats/. - Proposals for talks will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, it is expected that most, if not all, presenters/panellists will be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. --------------------- -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 1

Feedback on draft RIPE Atlas Service Terms and Conditions
by Adam Piggott 16 Sep '14

16 Sep '14

Hello, Having read the draft I find the T&Cs quite sensible but have some points to bring up. 7.1. [...] The RIPE NCC may perform security checks and audits to determine unauthorised use of the RIPE Atlas Service. 7.2. Users must assist the RIPE NCC with security checks and audits. These are a very open-ended statements and I'm sure that RIPE NCC has no intention of visiting our homes or places of work to perform "security checks and audits". The terms are written in a "legalese" form of language and hence must be taken at face value by those who accept them. I would not be comfortable agreeing to these two points without some sort of clarification as to what "security audits and checks" could be, and what "assistance" I would be obliged to provide. 10.1. All the RIPE Documents referred to in this agreement are available on http://www.ripe.net/. The Probe Host will regularly take notice of updated RIPE Documents on the website. I cannot accept this term. I can only accept to be bound to new terms if they are sent to me directly, for example by email. Article 2.3 seems to infer that RIPE NCC will indeed contact users directly at least 30 days in advance, which is acceptable. Thanks to RIPE NCC for including the community in such an important process. -- Adam Piggott, Proprietor Proactive Services (Computing)

2 1

Seeking community feedback on draft RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 15 Sep '14

15 Sep '14

Dear colleagues, As RIPE Atlas transitions from a pilot project to a production service, we want to publish RIPE Atlas Service Terms and Conditions that describe the use of the service and spell out both the user's and the RIPE NCC's obligations. We have published these proposed terms and conditions, along with an implementation plan, on RIPE Labs. Please take a look and let us know what you think. Your feedback is valuable, and and want to ensure we keep the community involved in every step of the process. https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service The main discussion about this should happen on the MAT Working Group Mailing List. We are asking to receive all feedback by the end of the RIPE 69 meeting in London, which takes places 3-7 November. Once the MAT Working Group Chairs have determined that consensus has been reached, a final version of the terms and conditions will be published. We're aiming to do so before the end of the year, so that RIPE Atlas can become a full production service by January 2015. Kind regards, Vesna Manojlovic Senior Community Builder Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: RIPE Atlas Measurements with Tagged Probes coming soon
by Mirjam Kuehne 12 Sep '14

12 Sep '14

Dear colleagues, Please find a new article on RIPE Labs: RIPE Atlas: Measurements with Tagged Probes Coming Soon https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-measurements… If you have any comments or questions, please let us know. Kind regards, Mirjam Kuehne RIPE NCC

1 0

The Beta Version of the New DNSMON is Now Available
by Vesna Manojlovic 08 Sep '14

08 Sep '14

Dear colleagues, The DNS Monitoring Service (DNSMON) has been providing a comprehensive, objective and up-to-date overview of the quality of various global and regional DNS operators' services since 2003. We are in the process of integrating DNSMON within RIPE Atlas and the beta version of the new DNSMON is now publicly available: https://atlas.ripe.net/dnsmon We have also published a RIPE Labs article detailing what’s changed in the new DNSMON: https://labs.ripe.net/Members/fatemah_mafi/an-updated-dns-monitoring-service We invite you all to try the new service and provide your feedback. We’re confident that the new DNSMON will continue to meet your needs and hope that you'll be happy with the new features. Please send your comments and questions to the DNS Working Group Mailing List at dns-wg(a)ripe.net. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

7 11

New on RIPE Labs: Time Warner Cable Outage Measurements
by Mirjam Kuehne 28 Aug '14

28 Aug '14

Dear colleagues, The Time Warner Cable network suffered an outage yesterday. We looked at some interesting details of this outage using the RIPE Routing Information Service and RIPE Atlas. Please find the results on RIPE Labs: https://labs.ripe.net/Members/emileaben/time-warner-cable-outage Kind regards, Mirjam Kuehne RIPE NCC

1 0

Upcoming "Measurements Tools" Workshop for LIRs: 19 September 2014, in Amsterdam
by Vesna Manojlovic 27 Aug '14

27 Aug '14

Dear colleagues, Training Services, RIPEstat/RIPE Atlas developers and me will be giving a hands-on "Measurements Tools" Workshop on 19 September, in Amsterdam. Registration is possible for members of RIPE NCC via LIR Portal: https://lirportal.ripe.net/training/courses More information: https://www.ripe.net/lir-services/training/courses/tailor-made-workshops#to… Regards, Vesna

1 0

Fwd: [ARIN-consult] Consultation on New Experimental Allocation
by Emile Aben 05 Aug '14

05 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear colleagues, I'd like to inform you of an experiment we propose doing together with ARIN about the routability of prefixes longer than /24 out of ARINs 23.128.0.0/10 block. For more details see ARIN's announcement below. If people have any feedback on this, please let us know. We plan to publish the results on RIPE Labs. Kind regards, Emile Aben RIPE NCC > From: ARIN <info(a)arin.net> Subject: [ARIN-consult] Consultation on > New Experimental Allocation Date: 4 Aug 2014 19:18:13 GMT+2 To: > arin-consult(a)arin.net > > ARIN is soliciting community input on a proposed experiment that > will require the temporary use of space from 23.128.0.0/10, the > IPv4 addresses reserved to facilitate IPv6 deployment. (see NRPM > policy 4.10 https://www.arin.net/policy/nrpm.html#four10 ) > > There has been much discussion on the NANOG mailing list about the > usability / routability of prefixes longer than a /24. In order to > try to provide some additional data on this topic, the RIPE NCC > has requested a small block of address space from the reserved /10 > in order to run the following experiment: > > RIPE Routing Information System (RIS) plans to announce a few > blocks of sizes /24 to /28 (no more then ten at a time) out of the > 23.128/10. They will monitor how this address space propagates in > BGP and its reachability. > > * This experiment will provide the global community with insight > on whether prefixes longer than a /24 from 23.128/10 are useable > and reachable on the global Internet. > > * A description of this experiment, as well as the results of > this research, will be published on https://labs.ripe.net/ . > Additionally, ARIN will provide a link to the RIPE Labs page, as > well as the end date of this experiment in the public Whois record > of this registration. > > Do you support the use of this reserved space for this experiment > or not, and why? Please provide comments to arin-consult(a)arin.net. > > This consultation will remain open through 5:00 PM EDT on Monday, > 1 September 2014. > > Regards, > > Leslie Nobile Director of Registration Services American Registry > for Internet Numbers (ARIN) > > > > _______________________________________________ ARIN-Consult You > are receiving this message because you are subscribed to the ARIN > Consult Mailing List (ARIN-consult(a)arin.net). Unsubscribe or manage > your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/arin-consult Please contact > the ARIN Member Services Help Desk at info(a)arin.net if you > experience any issues. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlPgtBkACgkQj05ACITZaqqG+gD/YRg/U4t+5AcfJooBICUSkrQc CZgsPUjBNKPTyAZuo0wA/2OnoB2Ls7V4J0M9PGmr0yPUERhWO5KCpwvfoyMvVBux =7/LU -----END PGP SIGNATURE-----

2 2

Nine new RIPE Atlas anchors so far this summer
by Vesna Manojlovic 25 Jul '14

25 Jul '14

Dear colleagues, We are proud to announce that nine new RIPE Atlas anchors have been activated since my previous announcement last month: - two hosted by NTT Communications in United States: us-sea-as2914, in Seattle & us-atl-as2914, in Atlanta - us-dal-as7366, hosted by Lemuria Communications in Dallas, USA - mu-plu-as327681, hosted by AFRINIC in Port Louis, Mauritius, on behalf of the RIPE NCC - cz-prg-as2852, hosted by CESNET, in Prague, Czech Republic. - dk-blp-as59469, hosted by Solido Networks ApS in Ballerup, Denmark - be-anr-as2611, hosted by MOSAIC/University of Antwerp/iMinds, Belgium - uk-lon-as60157, hosted by Antheus Telecom LTD, London, UK - us-wct-as7922 is hosted by Comcast, West Chester, PA, USA This brings the total number of anchors to 69. All RIPE Atlas anchors can be seen on this list: where logged-in users can access each anchor's measurements: https://atlas.ripe.net/anchors/list/ And on the map: https://atlas.ripe.net/anchors/map/ We are still accepting new applications from individuals and organisations interested in hosting a RIPE Atlas anchor. We are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa, in order to add more geographical diversity to the measurement data. Learn more about RIPE Atlas anchors and the benefits of hosting an anchor at: https://atlas.ripe.net/about/anchors/ For detailed announcements and updates about RIPE Atlas, please join the RIPE Atlas mailing list: https://www.ripe.net/mailman/listinfo/ripe-atlas Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0

Read on RIPE Labs: Midsummer Update for RIPE Atlas
by Vesna Manojlovic 24 Jul '14

24 Jul '14

Dear colleagues, in these hot and slow summer days, we give you an overview of the current status of RIPE Atlas, new features since the last update during RIPE68, and an insight into past and future community activities: https://labs.ripe.net/Members/fatemah_mafi/ripe-atlas-midsummer-update-2014 Regards, Vesna -- Measurements Community Building team <MCB(a)ripe.net>

1 0

Last Part or our World Cup Analysis now available on RIPE Labs
by Mirjam Kuehne 14 Jul '14

14 Jul '14

Dear colleagues, The final part of our analysis of the World Cup 2014 is now available on RIPE Labs, with a look at what happened during the final four matches of the tournament: https://labs.ripe.net/Members/emileaben/internet-traffic-during-the-world-c… (section 4) If you have any comments or extra information, please let us know. Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: How RIPE Atlas Helped Wikipedia Users
by Mirjam Kuehne 09 Jul '14

09 Jul '14

Dear colleagues, Engineers from the Wikimedia foundation and the RIPE NCC recently collaborated on a project to measure the latency of Wikimedia sites for users worldwide. Together, we identified ways to decrease latency and improve performance for users around the world. Please find more information on RIPE Labs: https://labs.ripe.net/Members/emileaben/how-ripe-atlas-helped-wikipedia-use… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Part 2 of Internet Traffic during World Cup 2014
by Mirjam Kuehne 08 Jul '14

08 Jul '14

Dear colleagues, Please find on RIPE Labs part 2 of our World Cup 2014 analysis of IXP data, featuring extra time, penalty shootouts and much more: https://labs.ripe.net/Members/emileaben/internet-traffic-during-the-world-c… If you have any comments or extra information, please post it under the article. Kind regards, Mirjam Kuehne RIPE NCC

1 0