This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Fifteen new RIPE Atlas anchors - including the first IPv4-only anchor
- Previous message (by thread): [atlas] "Invalid target" error for RFC 1918 space
- Next message (by thread): [atlas] Initiating a TCP, UDP, and ICMP traceroutes from the same probe at the same time
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michela Galante
mgalante at ripe.net
Mon Sep 19 11:30:55 CEST 2016
Dear colleagues, Fifteen new RIPE Atlas anchors have been activated since our last announcement in June, bringing the total number to 216: - us-abn-as54054, hosted by Deteque LLC in Ashburn, United States - us-sgu-as46309, hosted by Gartner Inc in Saint George, United States - lu-kay-as35733, hosted by EURid VZW in Kayl, Luxembourg - de-ham-as35258, hosted by akquinet Outsourcing in Hamburg, Germany - ua-iev-as24725, hosted by Hostmaster LLC in Kiev, Ukraine - ca-wnp-as18451, hosted by les.net in Winnipeg, Canada - de-dus-as12676, hosted by HKN GmbH in Düsseldorf, Germany - uk-lon-as34587, hosted by bet365 in London, United Kingdom - us-lax-as15133, hosted by Verizon Digital Media in Los Angeles, United States - us-lwc-as2495, hosted by KanREN Inc in Lawrence, United States - lb-bey-as12812, hosted by the American University of Beirut in Beirut, Lebanon (IPv4-only anchor) - pg-pom-as17828, hosted by Telikom PNG (sponsored by APNIC) in Port Moresby, Papua New Guinea - ch-zrh-as9092, hosted by Open Systems in Zurich, Switzerland - nl-ams-as34106, hosted by TMG/Telegraaf in Amsterdam, Netherlands - dk-hje-as39642, hosted by WNB ApS in Højer, Denmark You can find the full list of anchors, a map of their locations, a list of the hosting organisations and more information about RIPE Atlas anchors online: https://atlas.ripe.net/anchors/list/ As a follow-up to some discussion on this list, we wanted to reiterate that we made the decision to support IPv4-only anchors because the goal of RIPE Atlas is to measure as much of the Internet as possible, and right now, that includes IPv4-only networks. We also believe that measuring networks before and after they enable IPv6 provides useful data. IPv4-only anchors are clearly marked as such, and we will implement checks to ensure these anchors become IPv6-capable as soon as their ASNs begin announcing IPv6. In the meantime, the RIPE NCC will continue to actively promote IPv6 deployment through our training courses, IPv6 Act Now website, IPv6 Roadshows and other programs, and our IPv6 Program Manager will follow up with any hosts requesting an IPv4-only anchor to help them in any way possible. We believe that supporting IPv4-only anchors will provide a more comprehensive understanding of the Internet and that the entire Internet community will benefit from more measurement data. You can learn more in this RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ipv4-only-ripe-atlas-anchors-now-supported Interested in hosting a RIPE Atlas anchor? Learn more: https://atlas.ripe.net/get-involved/become-an-anchor-host/ 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. There are several organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, or for any other questions, please contact us at atlas at ripe.net And don’t forget to let us know if you’re doing something interesting with RIPE Atlas data - we always want to hear about your use cases, research and experiences! Regards, Michela Galante RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: </ripe/mail/archives/ripe-atlas/attachments/20160919/b37eb871/attachment.sig>
- Previous message (by thread): [atlas] "Invalid target" error for RFC 1918 space
- Next message (by thread): [atlas] Initiating a TCP, UDP, and ICMP traceroutes from the same probe at the same time
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]