As RIPE Atlas is expanding, it is approaching the magical milestone of 10,000 probes. However, as our public graphs also illustrate, the expansion has slowed down recently.
We had a look at various RIPE NCC data sets to see what we can learn from yet another country-wide Internet outage in 2016.
At the RIPE NCC, we are grateful for the contribution RIPE Atlas ambassadors make to the success of the RIPE Atlas measurements platform. In this article, we focus on a handy RIPEstat tool that can be used to visualise the results of their efforts. The tool provides a historical view of country-specific growth of RIPE Atlas probe numbers and allows for comparisons of up to four countries in the same graph.
IP address transfers have the potential to create more entries in the routing table for the same amount of address space. We analyse the net effect that four years of IPv4 transfers in the RIPE NCC service region have had on routing table growth and compare this to growth for allocations from which no transfers have been made.
Does RIPE have a diversity problem? Let's do some simple measurement, and try to find out.
We made some adjustments to the RIPE Labs front page so that you can find RIPE NCC operational statistics more easily. At the same time we also improved the look for mobile usage.
Cybersecurity is no longer a corporate or private affair. What once was simply good business practice is now a legal obligation for ISPs, large and small. What does this mean for you?
Over the past year, I have been conducting a public survey to better understand how ISPs deploy IPv6. In this post, I will summarise some of the key findings thus far.
We look into why dynamic addresses change and find ISPs that renumber periodically, most commonly every 24 hours or a multiple of 24 hours. We also find that outages influence address changes.
We’ve made some changes to RIPE Atlas API Keys with the aim of improving the experience of RIPE Atlas users. The changes are designed to boost transparency and efficiency in the way users are able to manage their API Keys.
Large BGP Communities are an addition to BGP that solves a communication problem between networks that want to use 32-bit AS Numbers. We measured how Large BGP Communities behave "in the wild" and if they create any problems.
An increasing number of countries are passing laws that facilitate the mass surveillance of their citizens. In response, governments and citizens are increasingly paying attention to the countries that their Internet traffic traverses. In some cases, countries are taking extreme steps, such as building new IXPs and encouraging local interconnection to keep local traffic local. We find that although many of these efforts are extensive, they are often futile, due to the inherent lack of hosting and route diversity for many popular sites. We investigate how the use of overlay network relays and the DNS open resolver infrastructure can prevent traffic from traversing certain jurisdictions.
One of the Internet’s key features is that it keeps networking functions separate from the applications and services that use these functions. However, network operators and especially Internet service providers appear to be becoming more content aware. Networking is becoming more intertwined with content. This might have implications for tomorrow’s Internet.
The RIPE NCC is building relationships with external organisations and documenting the relationships we already have in order to broaden the support for and understanding of RIPE, the RIPE NCC and the global registry system.
This article is intended to make RIPE Atlas users aware of ethical issues that could arise when using RIPE Atlas. We do not intend to propose any new formal processes or procedures to address the relevant ethical issues, but we do want to encourage members of the RIPE Atlas community to consider the ethical impact of their behaviour when using RIPE Atlas.
The fourth RIPE NCC Hackathon was as fun and productive as the previous three, with even more supporting organisations and participants. This short article aims to express our gratitude to everyone involved and to give a summary of our experiences, while several projects will be described in more detail in the follow-up articles.
Geoff Huston discusses the possible demise of transit services and the rise of content networking.
The recent attacks on the DNS infrastructure operated by Dyn have generated a lot of comment in recent days. Indeed, it’s not often that the DNS itself has been prominent in the mainstream of news commentary and, in some ways, this DNS DDoS prominence is for all the wrong reasons! I’d like to speculate a bit on what this attack means for the DNS and what we could do to mitigate the recurrence of such attacks.
This is the final post in a series on Network Address Translation (NAT), provided by Mark Smith. In this post, Mark discusses the fundamental constraints of NAT and addresses some FAQs about IPv6 without NAT.
This is the second post in a series on NATs contributed by Mark Smith, based on a presentation given at AusNOG 2016. In the first post, Mark discussed Network Critical Success Factors (NCSFs). In this post, he is going into details about the trouble with Network Address Translation (NAT).