{"id":1182,"date":"2026-09-12T09:06:11","date_gmt":"2026-09-12T09:06:11","guid":{"rendered":"https:\/\/ip4.market\/blog\/self-service-ripe-management-leased-ipv4\/"},"modified":"2026-09-12T09:11:07","modified_gmt":"2026-09-12T09:11:07","slug":"self-service-ripe-management-leased-ipv4","status":"publish","type":"post","link":"https:\/\/ip4.market\/blog\/self-service-ripe-management-leased-ipv4\/","title":{"rendered":"Self-Service RIPE Management for Leased IPv4: Set Up Your Details"},"content":{"rendered":"<p class=\"post-intro\"><em>When you lease IPv4 space, who controls its RIPE records \u2014 you, or a support queue? On IP4 Market you manage it yourself. This guide shows how to set up your RIPE details once so every action that follows runs in your own name.<\/em><\/p>\n<div class=\"tools-toc\"><strong>In this guide<\/strong><\/p>\n<ol>\n<li>Why self-service RIPE management matters<\/li>\n<li>What &#8220;your RIPE details&#8221; are<\/li>\n<li>Before you start<\/li>\n<li>Step by step<\/li>\n<li>What we keep, what you control<\/li>\n<li>Next steps<\/li>\n<\/ol>\n<\/div>\n<h2>Why self-service RIPE management matters<\/h2>\n<p>Most IPv4 leasing providers keep the keys to themselves: every route object, every description change, every abuse contact update means opening a ticket and waiting. That is slow, and it puts your operational reality in someone else&#8217;s hands.<\/p>\n<p>We took the opposite approach. When you lease a range from IP4 Market, we delegate the relevant RIPE maintainers (<code>mnt-routes<\/code> and <code>mnt-lower<\/code>) to <em>your<\/em> maintainer. From that moment you announce, describe and register your space yourself, straight from your dashboard \u2014 a level of autonomy very few providers hand over.<\/p>\n<div class=\"result-box\">\n<p><strong>The short version:<\/strong> set your RIPE identity once in Company Settings, and creating route objects or publishing your description and abuse contact becomes a two-minute, self-service job.<\/p>\n<\/div>\n<h2>What &#8220;your RIPE details&#8221; are<\/h2>\n<p>Your RIPE details are the identity we use on your behalf when you register usage:<\/p>\n<ul>\n<li><strong>Organisation<\/strong> \u2014 your RIPE org handle, e.g. <code>ORG-EXAMPLE-RIPE<\/code>. It carries your abuse contact.<\/li>\n<li><strong>Admin and tech contacts<\/strong> \u2014 your <code>nic-hdl<\/code>s, e.g. <code>AA1234-RIPE<\/code>.<\/li>\n<li><strong>Maintainer<\/strong> \u2014 your <code>mntner<\/code>, the object that authorises what you do in RIPE.<\/li>\n<\/ul>\n<p>Set them once and they become the defaults for every route object and sub-assignment you create.<\/p>\n<h2>Before you start<\/h2>\n<ul>\n<li>You are a RIPE member, or you already have a RIPE organisation object and at least one contact (<code>nic-hdl<\/code>).<\/li>\n<li>You have your own maintainer. When you lease a range from us, we delegate routing and sub-allocation rights on it to that maintainer.<\/li>\n<\/ul>\n<h2>Step by step<\/h2>\n<div class=\"tool-card-block\">\n<div class=\"tool-card-icon\">1<\/div>\n<div class=\"tool-card-content\">\n<p>In your dashboard, open <strong>Company Settings<\/strong>.<\/p>\n<\/div>\n<\/div>\n<div class=\"tool-card-block\">\n<div class=\"tool-card-icon\">2<\/div>\n<div class=\"tool-card-content\">\n<p>Scroll to the <strong>RIPE settings<\/strong> section.<\/p>\n<\/div>\n<\/div>\n<div class=\"tool-card-block\">\n<div class=\"tool-card-icon\">3<\/div>\n<div class=\"tool-card-content\">\n<p>Fill in your <strong>Organisation ID<\/strong>, <strong>Default maintainer<\/strong>, and your <strong>Admin<\/strong> and <strong>Tech<\/strong> contacts.<\/p>\n<\/div>\n<\/div>\n<div class=\"tool-card-block\">\n<div class=\"tool-card-icon\">4<\/div>\n<div class=\"tool-card-content\">\n<p>Click <strong>Save Changes<\/strong>. That&#8217;s it.<\/p>\n<\/div>\n<\/div>\n<div class=\"result-box warning\">\n<p><strong>Why the organisation matters for abuse.<\/strong> Your abuse contact is published through your RIPE organisation. Once your Organisation ID is set here, the sub-assignments you create for your leased ranges carry your abuse contact automatically \u2014 so reports reach you, not us.<\/p>\n<\/div>\n<h2>What we keep, what you control<\/h2>\n<p>The parent allocation object stays under our maintainer, so it can never be altered or transferred by mistake. Everything about <em>how you use the space<\/em> \u2014 routing and registration \u2014 is delegated to you. It is the standard, transparent leasing model, with the controls actually in your hands.<\/p>\n<h2>Next steps<\/h2>\n<p>With your RIPE details in place, you can:<\/p>\n<ul>\n<li>Announce your range by <strong>creating your RIPE route object<\/strong>.<\/li>\n<li>Publish your <strong>description and abuse contact<\/strong> with a sub-assignment.<\/li>\n<\/ul>\n<div class=\"result-box\">\n<p><strong>Need IPv4 addresses?<\/strong> Lease RIPE-verified \/24&ndash;\/22 subnets from $0.50\/IP per month &mdash; LOA + RPKI\/ROA in minutes, instant company verification, and full self-service RIPE management from your dashboard. <a href=\"https:\/\/panel.ip4.market\/marketplace?utm_source=blog&amp;utm_medium=cta&amp;utm_campaign=ripe-self-service\" rel=\"nofollow\">See available subnets &rarr;<\/a><\/p>\n<\/div>\n<div class=\"te-puede-interesar\"><strong>You may also like<\/strong><\/p>\n<ul>\n<li><a href=\"https:\/\/ip4.market\/blog\/create-ripe-route-object-leased-ipv4\/\">How to Create a RIPE Route Object for Your Leased IPv4 Range<\/a><\/li>\n<li><a href=\"https:\/\/ip4.market\/blog\/register-ipv4-usage-description-abuse-ripe\/\">Register Your Usage: Description &amp; Abuse Contact for Leased IPv4<\/a><\/li>\n<\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>When you lease IPv4 space, who controls its RIPE records \u2014 you, or a support queue? On IP4 Market you manage it yourself. This guide shows how to set up&#8230;<\/p>\n","protected":false},"author":3,"featured_media":1183,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-1182","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ipv4-market"],"_links":{"self":[{"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/posts\/1182","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/comments?post=1182"}],"version-history":[{"count":1,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/posts\/1182\/revisions"}],"predecessor-version":[{"id":1190,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/posts\/1182\/revisions\/1190"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/media\/1183"}],"wp:attachment":[{"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/media?parent=1182"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/categories?post=1182"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/tags?post=1182"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}