Snuggle Systems https://snuggle.systems/ en Mon, 20 Jul 2026 17:20:08 +0100 Starting to set up AS208147 https://snuggle.systems/2026/07/20/starting-to-set-up-as/ Mon, 20 Jul 2026 17:20:08 +0100 http://snuggle-systems.micro.blog/2026/07/20/starting-to-set-up-as/ <p>Snuggle Systems now has its own slice of the internet&rsquo;s routing table: AS208147 is officially registered, and I&rsquo;m starting the process of actually putting it to work.</p> <h2 id="whats-actually-happening-here">What&rsquo;s actually happening here</h2> <p>An ASN doesn&rsquo;t do much, it only becomes useful once you start using it to announce via BGP towards upstreams willing to carry the announcements. So the plan, roughly:</p> <ul> <li><strong>Two independent sites</strong>: each with its own path to the internet, so a failure in one location doesn&rsquo;t take the network down.</li> <li><strong>Two transit providers</strong>: at least at the beginning, one per site with the two sites talking to each other directly.</li> <li><strong>Two IP address prefixes</strong>: one /24 for IPv4 and one /48 for IPv6</li> </ul> <h2 id="what-has-been-done">What has been done</h2> <p>The boring stuff: paperwork, applying for an ASN, getting PI (provider-independent) IP address space, talking to transit providers, getting RIPE database objects in order, setting up RPKI ROAs, setting up IRR objects, making a PeeringDB entry so that AS208147 is discoverable and contactable by anyone who needs to reach it, and finally, making this page.</p> <h2 id="whats-next">What&rsquo;s next</h2> <p>Next up: the actual BGP sessions - getting the two sites talking to their respective transit providers, then to each other. I&rsquo;ll hopefully do a follow-up once it is working.</p> <p>If you&rsquo;re building something similar and want to compare notes, feel free to reach out to shiny new AS208147!</p> Snuggle Systems now has its own slice of the internet's routing table: AS208147 is officially registered, and I'm starting the process of actually putting it to work. ## What's actually happening here An ASN doesn't do much, it only becomes useful once you start using it to announce via BGP towards upstreams willing to carry the announcements. So the plan, roughly: - **Two independent sites**: each with its own path to the internet, so a failure in one location doesn't take the network down. - **Two transit providers**: at least at the beginning, one per site with the two sites talking to each other directly. - **Two IP address prefixes**: one /24 for IPv4 and one /48 for IPv6 ## What has been done The boring stuff: paperwork, applying for an ASN, getting PI (provider-independent) IP address space, talking to transit providers, getting RIPE database objects in order, setting up RPKI ROAs, setting up IRR objects, making a PeeringDB entry so that AS208147 is discoverable and contactable by anyone who needs to reach it, and finally, making this page. ## What's next Next up: the actual BGP sessions - getting the two sites talking to their respective transit providers, then to each other. I'll hopefully do a follow-up once it is working. If you're building something similar and want to compare notes, feel free to reach out to shiny new AS208147!