<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>RIPE Labs</title><link href="https://labs.ripe.net" rel="alternate"/><link href="https://labs.ripe.net/atom.xml" rel="self"/><id>https://labs.ripe.net</id><updated>2026-04-08T08:57:51.315892+00:00</updated><entry><title>Operating a Data Center with a Small Team: Engineering Lessons from Central Asia</title><link href="https://labs.ripe.net/author/furug-rasuli/operating-a-data-center-with-a-small-team-engineering-lessons-from-central-asia/" rel="alternate"/><published>2026-04-08T08:57:18.143000+00:00</published><updated>2026-04-08T08:57:51.315892+00:00</updated><author><name>Furug Rasuli</name><uri>https://labs.ripe.net/author/furug-rasuli/</uri></author><id>https://labs.ripe.net/author/furug-rasuli/operating-a-data-center-with-a-small-team-engineering-lessons-from-central-asia/</id><summary type="html">Managing ~600 infrastructure devices with a three-person team demands careful design choices. Based on experience in Central Asia, this article examines how standardisation, observability, and operational discipline support reliability at scale.</summary><category term="security"/><category term="competition"/><category term="internet infrastructure"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Beyond the Network View: DNS-Driven Application Visibility</title><link href="https://labs.ripe.net/author/danny-lachos/beyond-the-network-view-dns-driven-application-visibility/" rel="alternate"/><published>2026-04-02T09:20:28.216188+00:00</published><updated>2026-04-02T12:12:14.349043+00:00</updated><author><name>Danny Lachos</name><uri>https://labs.ripe.net/author/danny-lachos/</uri></author><id>https://labs.ripe.net/author/danny-lachos/beyond-the-network-view-dns-driven-application-visibility/</id><summary type="html">Network operators often lack visibility into which applications drive their traffic. We present an open-source DNS-based correlation method that enriches NetFlow and BGP data with application and CDN information. This enables a shift from a network-centric to an application-oriented view of traffic.</summary><category term="dns"/><category term="tools"/><category term="competition"/><category term="open source"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Extending API Keys Beyond the RIPE Database</title><link href="https://labs.ripe.net/author/fallon-albrecht/extending-api-keys-beyond-the-ripe-database/" rel="alternate"/><published>2026-03-31T13:06:08.325968+00:00</published><updated>2026-03-31T13:06:08.325968+00:00</updated><author><name>Fallon Albrecht</name><uri>https://labs.ripe.net/author/fallon-albrecht/</uri></author><id>https://labs.ripe.net/author/fallon-albrecht/extending-api-keys-beyond-the-ripe-database/</id><summary type="html">We are extending the API key model introduced for the RIPE Database to create a more consistent, secure, and flexible approach across RIPE NCC services.</summary><category term="ripe"/><category term="members"/><category term="operational"/><category term="internet number resources"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>When iBGP Full Mesh Is Actually Unnecessary</title><link href="https://labs.ripe.net/author/rivadeneyra/when-ibgp-full-mesh-is-actually-unnecessary/" rel="alternate"/><published>2026-03-31T09:03:57.434650+00:00</published><updated>2026-03-31T09:03:57.434650+00:00</updated><author><name>José Mª Rivadeneyra</name><uri>https://labs.ripe.net/author/rivadeneyra/</uri></author><id>https://labs.ripe.net/author/rivadeneyra/when-ibgp-full-mesh-is-actually-unnecessary/</id><summary type="html">A common misconception is that iBGP requires a full mesh or alternatives such as route reflectors. In reality, full mesh is not a protocol requirement, but a design choice that may be unnecessary and even undesirable in stub ASes and small ISPs.</summary><category term="bgp"/><category term="routing"/><category term="competition"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Make This One Change to Prevent Routing Loops in Your Network</title><link href="https://labs.ripe.net/author/mkoch/make-this-one-change-to-prevent-routing-loops-in-your-network/" rel="alternate"/><published>2026-03-25T15:58:55.953000+00:00</published><updated>2026-03-30T14:48:20.302827+00:00</updated><author><name>Maynard Koch</name><uri>https://labs.ripe.net/author/mkoch/</uri></author><id>https://labs.ripe.net/author/mkoch/make-this-one-change-to-prevent-routing-loops-in-your-network/</id><summary type="html">Routing loops can trap packets between routers, preventing them from reaching their destination. In some cases, routers even duplicate looping packets, amplifying traffic and threatening Internet stability. We look at how this happens and how operators can prevent it.</summary><category term="routing"/><category term="research"/><category term="competition"/><category term="measurements"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Announcing the Results of the 2025 RIPE Code of Conduct Survey</title><link href="https://labs.ripe.net/author/amcconachie/announcing-the-results-of-the-2025-ripe-code-of-conduct-survey/" rel="alternate"/><published>2026-03-24T12:11:00.037000+00:00</published><updated>2026-03-31T09:53:11.240920+00:00</updated><author><name>Andrew McConachie</name><uri>https://labs.ripe.net/author/amcconachie/</uri></author><id>https://labs.ripe.net/author/amcconachie/announcing-the-results-of-the-2025-ripe-code-of-conduct-survey/</id><summary type="html">The RIPE community has spoken and the results are in. The RIPE Code of Conduct Team presents an analysis of the feedback received, discusses next actions, and shares a detailed breakdown of the results.</summary><category term="ripe"/><category term="events"/><category term="community"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Working with Local Hosts to Deliver Training</title><link href="https://labs.ripe.net/author/olivia-ruimwijk/working-with-local-hosts-to-deliver-training/" rel="alternate"/><published>2026-03-17T15:12:50.586000+00:00</published><updated>2026-03-31T09:53:23.114827+00:00</updated><author><name>Olivia Ruimwijk</name><uri>https://labs.ripe.net/author/olivia-ruimwijk/</uri></author><id>https://labs.ripe.net/author/olivia-ruimwijk/working-with-local-hosts-to-deliver-training/</id><summary type="html">In-person training remains a cornerstone of RIPE NCC engagement and many of our courses are made possible by local hosts who help us bring learning closer to the community. Here’s where we’ve been, and a look at where we’re heading next.</summary><category term="ripe"/><category term="training"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>RootViz: New Root DNS Reachability Dashboard</title><link href="https://labs.ripe.net/author/giovane_moura/rootviz-new-root-dns-reachability-dashboard/" rel="alternate"/><published>2026-03-10T14:32:13.936658+00:00</published><updated>2026-03-31T09:53:39.566120+00:00</updated><author><name>Giovane Moura</name><uri>https://labs.ripe.net/author/giovane_moura/</uri></author><id>https://labs.ripe.net/author/giovane_moura/rootviz-new-root-dns-reachability-dashboard/</id><summary type="html">In this guest post, the team at SIDN Labs introduce a new dashboard built on RIPE Atlas data that lets the community visualise real-time measurement results and explore how probes reach the Internet’s root DNS servers.</summary><category term="dns"/><category term="tools"/><category term="atlas"/><category term="competition"/><category term="measurements"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>The RIPE Chair Team Reports - March 2026</title><link href="https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-march-2026/" rel="alternate"/><published>2026-03-10T10:34:56.760006+00:00</published><updated>2026-03-31T09:53:52.768969+00:00</updated><author><name>Mirjam Kühne</name><uri>https://labs.ripe.net/author/mirjam_kuhne/</uri></author><id>https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-march-2026/</id><summary type="html">The RIPE Chair Team reports on preparations for RIPE 92, including programme planning and opportunities for community participation, as well as highlights from recent industry events and engagement with the wider Internet community.</summary><category term="ripe"/><category term="events"/><category term="community"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Rethinking RIPE NCC Navigation</title><link href="https://labs.ripe.net/author/antonella-de-bellis/rethinking-ripe-ncc-navigation/" rel="alternate"/><published>2026-03-05T15:01:42.979658+00:00</published><updated>2026-03-31T09:54:04.013052+00:00</updated><author><name>Antonella De Bellis</name><uri>https://labs.ripe.net/author/antonella-de-bellis/</uri></author><id>https://labs.ripe.net/author/antonella-de-bellis/rethinking-ripe-ncc-navigation/</id><summary type="html">We’ve been looking at how members navigate between RIPE NCC services and where friction appears. This article shares the research and reasoning behind a new unified navigation model launching in March 2026.</summary><category term="ripe"/><category term="events"/><category term="operational"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>A Day in the Life of RIPE Atlas</title><link href="https://labs.ripe.net/author/yevheniya-nosyk/a-day-in-the-life-of-ripe-atlas/" rel="alternate"/><published>2026-03-03T10:28:57.025000+00:00</published><updated>2026-03-31T09:54:18.173254+00:00</updated><author><name>Yevheniya Nosyk</name><uri>https://labs.ripe.net/author/yevheniya-nosyk/</uri></author><id>https://labs.ripe.net/author/yevheniya-nosyk/a-day-in-the-life-of-ripe-atlas/</id><summary type="html">On any given day, RIPE Atlas generates billions of measurement results, offering a comprehensive view of connectivity and reachability worldwide. This data, collected for over a decade, forms a unique historical record of the Internet. Here, we focus on a single day to show how RIPE Atlas operates in practice.</summary><category term="atlas"/><category term="research"/><category term="measurements"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Ukraine as a Laboratory of Internet Resilience</title><link href="https://labs.ripe.net/author/eliza-rohotska/ukraine-as-a-laboratory-of-internet-resilience/" rel="alternate"/><published>2026-02-24T15:38:50.445000+00:00</published><updated>2026-03-02T11:33:12.897672+00:00</updated><author><name>Eliza Rohotska</name><uri>https://labs.ripe.net/author/eliza-rohotska/</uri></author><id>https://labs.ripe.net/author/eliza-rohotska/ukraine-as-a-laboratory-of-internet-resilience/</id><summary type="html">Ukraine’s Internet has not collapsed under invasion - it has adapted. This article examines what that reveals about the concept of resilience in the context of Internet infrastructure and the people who keep the networks running.</summary><category term="nogs"/><category term="outages"/><category term="country"/><category term="community"/><category term="competition"/><category term="internet infrastructure"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>When ToR Instability Collapses Cross-Rack Redundancy Without Breaching SLA</title><link href="https://labs.ripe.net/author/ruslan-seyidov/when-tor-instability-collapses-cross-rack-redundancy-without-breaching-sla/" rel="alternate"/><published>2026-02-24T11:14:12.766454+00:00</published><updated>2026-02-24T11:14:12.766454+00:00</updated><author><name>Ruslan Seyidov</name><uri>https://labs.ripe.net/author/ruslan-seyidov/</uri></author><id>https://labs.ripe.net/author/ruslan-seyidov/when-tor-instability-collapses-cross-rack-redundancy-without-breaching-sla/</id><summary type="html">This article examines a two-rack deployment where ToR instability quietly collapsed redundancy while SLA metrics remained within bounds, revealing how service-level monitoring can mask structural risk.</summary><category term="use case"/><category term="competition"/><category term="internet infrastructure"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Testing IXP Configurations Without Breaking Production: A Digital Twin Approach</title><link href="https://labs.ripe.net/author/tcaiazzi/testing-ixp-configurations-without-breaking-production-a-digital-twin-approach/" rel="alternate"/><published>2026-02-23T14:23:16.495000+00:00</published><updated>2026-02-24T06:31:44.652088+00:00</updated><author><name>Tommaso Caiazzi</name><uri>https://labs.ripe.net/author/tcaiazzi/</uri></author><id>https://labs.ripe.net/author/tcaiazzi/testing-ixp-configurations-without-breaking-production-a-digital-twin-approach/</id><summary type="html">Configuration mistakes at an IXP can have immediate impact. Building on the earlier IXP Digital Twin project, this article presents a new dashboard that enables operators to recreate production environments, validate routing state, and test member onboarding off production.</summary><category term="tools"/><category term="peering"/><category term="competition"/><category term="internet infrastructure"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry><entry><title>Looking Back at 2025: What the Numbers Say About Engagement, Skills, and Coordination</title><link href="https://labs.ripe.net/author/alena-muravska/looking-back-at-2025-what-the-numbers-say-about-engagement-skills-and-coordination/" rel="alternate"/><published>2026-02-18T12:26:19.285000+00:00</published><updated>2026-02-20T12:24:23.144045+00:00</updated><author><name>Alena Muravska</name><uri>https://labs.ripe.net/author/alena-muravska/</uri></author><id>https://labs.ripe.net/author/alena-muravska/looking-back-at-2025-what-the-numbers-say-about-engagement-skills-and-coordination/</id><summary type="html">At the RIPE NCC, engagement happens in many different formats - RIPE Meetings, regional events, Open Houses, training courses, RIPE Labs, and more. But the questions behind all this activity are consistent: who are we reaching, how accessible is participation, and are people able to stay involved over time?</summary><category term="ripe"/><category term="events"/><category term="training"/><category term="governance"/><category term="operational"/><rights>Copyright (c) 2026, RIPE Labs</rights></entry></feed>