Requesting a peering

RoutedBits is open for peering to any registered DN42 member in good standing. Pick a node, provide your side of the tunnel, and our automation provisions the RoutedBits side and brings up the BGP session for you.

What is DN42?

DN42 is a decentralized, peer-to-peer network for exploring and researching Internet routing technologies while enabling members to share services with one another. Rather than relying on physical links, members typically connect through tunnels and use protocols such as BGP to establish routing across the broader network. Members also host a variety of services that are accessible throughout DN42.

More information about the network can be found on the DN42 wiki.

Getting started

You will need:

A DN42 registry presence — a registered ASN and maintainer object (MNT).
A user account. Sign in with the Log in with Kioubit button. First-time users must authenticate through Kioubit.dn42; we read your basic registry information (ASN, IP allocations, MNT resource) so you can self-service tunnels and peerings on our platform.
A WireGuard endpoint of your own — a public IPv4/IPv6 address or hostname, a listening port, and a public key.

Once logged in, go to Peerings → Add peering (or any Request a session button) to open the form. You enter your side; the RoutedBits side is generated automatically when you submit. For details on every field, see Session options.

After you submit, we automatically provision the tunnel and BGP session on your chosen node. Your generated RoutedBits configuration — endpoint (hostname.routedbits.com:[port]), our public key, tunnel MTU (1420), and BGP peer addresses — appears on your peering list and on the live session status page.

Please allow 5–10 minutes for provisioning to complete. Live details appear on the peering page as metrics begin to arrive. If you have trouble establishing the session, contact us.

Route filtering

Every session is filtered with strict ROA — routes that fail origin validation are dropped. This is enforced on all peerings and is not configurable.

Traffic engineering

You can shape how your announcements are handled by attaching BGP large communities to your routes — for example AS prepending (4242420207:500:[1-4]), blackhole (65535:666), or "don't advertise to region X" (4242420207:600:[region]). See the BGP communities page for the full published list.

Keeping your session healthy

Sessions are monitored automatically. A peering may be removed automatically if its WireGuard endpoint stops resolving in DNS, or if the BGP session never establishes or stays inactive past our threshold. You will see warnings on the session status page before this happens.