"Measuring the Internet" has become an increasingly essential practice in many different areas. The fact that we are living in an era where Cloud services and CDNs are becoming more accessible and worldwide presence is within hand's reach for practically anybody, making informed decisions through measurements can both save money and help to find optimal performance.
We used a number of RIPE NCC tools and data sets to take a quick look at the recent DDoS attack on Dyn’s infrastructure. We wanted to see if this could be found in the data produced by the RIPE Atlas community.
Maybe surprisingly, there is quite an overlap between the RIPE community and the hackers community. Visiting a local hackerspace has been a tradition for more than five years: during RIPE Meetings, network operators groups, IXP meetings and other technical events. This is a nostalgic look back to the history of these encounters, and an invitation to join us for future explorations.
The exhortations about the Internet’s prolonged transition to version 6 of the Internet Protocol continue, although after some two decades the intensity of the rhetoric has faded and, possibly surprisingly, it has been replaced by action in some notable parts of the Internet. But how do we know there is action? How can we tell whether, and where, IPv6 is being deployed in today’s Internet?
On 17 October 2016, a website hosted by the French Ministry of the Interior went offline when a large number of customers of the Internet service provider, Orange, were redirected to the site. The problem occurred after Google, Wikipedia and cloud provider OVH were mistakenly placed on a terrorism block list.
Please read this guest post by Tony Scheid about fighting Distributed Denial of Service (DDoS) attacks during the Olympics in Rio de Janeiro.
"Non-public measurements" is a feature of RIPE Atlas that allows users to use the infrastructure to measure things while not sharing those results with the public. Is that still a useful feature? Should it exist in the future? Please take the polls.
Two years ago we released the RIPE NCC Academy - an online training service. Now we've launched the third training module: the Local Internet Registry (LIR) course.
RIPE Atlas lets you make customised measurements from thousands of probes around the world. These measurements cost credits, which users usually earn by hosting or sponsoring RIPE Atlas probes - or you may have just been given a million RIPE Atlas credits as a member of one of the Regional Internet Registries. Find out how you can best spend your credits to check your services' connectivity and troubleshoot potential issues.
It was about one year ago that the RIPE community reached consensus on a policy proposal that introduced additional criteria for initial IPv6 allocations. We thought it was time to look back at the origins of this proposal and see how the change has worked out since.
Sure, for some the Internet of Things is just an opportunity to make money. But what if it's also an opportunity to share our expertise - and in the process, make the world a better place?
Is the elliptical curve cryptographic algorithm (ECDSA) a viable crypto algorithm for use in DNSSEC today? And what has changed over the last two years?
In 2016, IPv4 exhaustion is on everyone’s lips: four out of five Regional Internet Registries have run out of freely available address space.
Comparisons rarely work. They never fit properly; they almost always lead away from the topic. And the audience‘s attention is lost in unimportant details. Therefore, writers do themselves few favours when they use comparisons as stylistic tools. I once read that in a book about speech writing (Franz, 2015). But there is one exception: the remote comparison. The further away the object of comparison, the better. The remote comparison is intended to show how absurd a situation is. The market at the core of the Internet is like a movie without a title.
The Dutch Network Operators Group had its annual conference on 9 September 2016, in Amsterdam. Here are some impressions of the event.
We started using RIPE Atlas to monitor and improve the services to our customers. We liked it so much that we're now a sponsor!
We are updating the technology behind RIPE Labs and www.ripe.net. If you are a frequent RIPE Labs editor, you will discover some great new features! At the same time, we also documented our experiences with upgrading to the new version to provide feedback to the Plone community.
We announced earlier that the RIPE Atlas APIs will change around the end of the year. In this article we give some advice on how to make this transition.
How we compare connectivity of cloud services using RIPE Atlas latency and DNS measurements
In July, I was fortunate enough to attend the third Indonesia Network Operators Group conference, IDNOG 3, which was held in Jakarta.