Disclosure up front: I run IPYE, a company that leases IP space. Most of this article is practical how-to; IPYE appears where a free /48, LOA, or ROA helps you try the work, with a short call to action at the end.
PeeringDB is the shared database where networks publish how to peer with them: which exchanges and data centres they are in, what their peering policy is, and how many prefixes to expect. Many operators set max-prefix limits and decide whether to peer at all by reading it. If your network starts with a single free IPv6 /48 from IPYE, a small, accurate PeeringDB record makes the first peering requests much easier. Examples use AS64496.
Why bother with one prefix
A record helps even before you peer with anyone:
- Peers and route servers read your expected prefix count to set max-prefix limits. Without it, they guess.
- Your NOC contact is where other operators look when your network causes a problem.
- Some exchange points and route servers build filters from the IRR as-set listed in PeeringDB.
Get access
Create a user account on peeringdb.com, then request affiliation with your ASN. PeeringDB verifies the request against the contact information in the RIR's record for the ASN, usually by email to the registered contact. Make sure that address works before you start. If no organisation exists yet, the affiliation request creates one.
The minimum useful record
Fill in these fields carefully:
| Field | What to enter |
|---|---|
| Name | your network's public name |
| Website | your main site |
| IRR as-set | your as-set, for example AS64496:AS-CUSTOMERS, or AS64496 if you have no customers |
| IPv6 prefixes | the number you announce, here 1
|
| IPv4 prefixes |
0 until you have IPv4 space |
| Network type | the honest category, such as Content or NSP |
| Peering policy | Open, Selective or Restrictive |
| Policy URL | a page with your peering terms, if you have one |
Then add at least one role contact for NOC and one for policy, with addresses that a person reads.
Set the prefix counts slightly above what you announce today if you expect growth, but not far above. If you set 1000 with one prefix, peers lose the protection max-prefix is meant to give.
Facilities and exchanges
Add a facility only where you have equipment or a cross-connect. Add an exchange connection only once you have a port and IP addresses from that exchange. A record that claims presence you do not have wastes other operators' time and damages trust.
Traffic levels
The traffic field is a range, and it should reflect real measurements. A new network with a single /48 normally sits in the lowest band. That is fine; plenty of small networks peer actively.
Verify the record
The API is open for reading:
curl -s 'https://www.peeringdb.com/api/net?asn=64496' | jq '.data[0] | {name, info_prefixes6, irr_as_set, policy_general}'
Check the IRR as-set too:
bgpq4 -6 -l OUR-PREFIXES AS64496
The output should list your /48. If it is empty, the route6 object is missing or the as-set does not include your ASN. For a free /48 on IPYE's ARIN or APNIC accounts, route objects are created automatically; confirm they resolve from the as-set you published.
Keep it current
Review the record whenever something changes: a new prefix, a new exchange, a new NOC address. A quick check every few months is enough for a small network. Stale contact addresses are the most common problem, and they matter most during incidents.
Your first peering request
When you contact a network about peering, include your ASN, the exchange or facility, your IPv6 address on the exchange, your max-prefix value and a link to your PeeringDB record. Keep it short. If they ask for proof of the prefix, attach the LOA from the IPYE portal.
Do this next
Claim a free /48 from IPYE, check your as-set with bgpq4, and publish a PeeringDB record that lists exactly what you announce. Questions: ipye@turnel.com.
About IPYE
IPYE (https://ipye.com) leases IPv4, IPv6 and ASN space with instant setup. Your first IPv6 /48 is free for the first year, a real allocation you can announce on your own ASN, with a LOA from the portal and the ROA created automatically. ASN and region changes apply automatically. IPv4 /24 to /22 leases include LOA, ROA and per-/24 rDNS; WHOIS is editable on IPv6 /44 and larger. Locations: Los Angeles, New York, Ashburn, Salt Lake City, London, Amsterdam, Frankfurt. Claim your free /48: https://my.ipye.com/products/ipv6-rental. Questions: ipye@turnel.com.
Disclosure: I run IPYE
Top comments (0)