Peering policy

Last updated: October 2026

Akamind Inc. operates AS396144, an IPv6-native network carrying transactional email (Oveyon) and link routing (Rivva), with two IPv4 /24s held for reaching the parts of the internet that are still v4-only. Our policy is open: we will peer with any network that keeps its routing data in order, at any location where we are both present, with no contract, no traffic ratio and no minimum volume. Requests go to [email protected].

Details

• AS number: AS396144
• Address space: 2604:6340::/32 (IPv6) and two IPv4 /24s — 23.165.44.0/24 and 198.151.136.0/24 — all held directly from ARIN
• IRR as-set: ARIN::AS-AKAMIND
• PeeringDB: peeringdb.com/net/43612
• Geofeed: akamind.net/geofeed.csv
• Traffic: mostly outbound
• Max-prefix to configure: 25 for IPv6, 10 for IPv4

What we do on our side

• A block we are not announcing carries an AS0 ROA, so nobody can announce it while it sits idle. Every prefix we do announce has its own ROA with maxLength equal to the prefix length. A more specific route out of our space does not validate, so a forged-origin hijack of it is rejected by anyone doing origin validation (RFC 9319).
• Every announced prefix has a matching route6 object in ARIN's IRR, reachable by expanding ARIN::AS-AKAMIND.
• We publish a geofeed under RFC 8805 and keep it current, so you can place our addresses without guessing. Anycast prefixes are deliberately absent from it, because they have no single location.
• Addresses that send mail carry reverse DNS that resolves back to the sending name.
• We announce our own space only. We do not originate or carry anyone else's prefixes without their authorization in RPKI and IRR.
• [email protected] is read by the people who run the network, not by a ticket queue.

What we ask of you

• Keep a current PeeringDB record, with a NOC contact and your prefix counts.
• Filter what you send us by prefix and by AS path, and keep your IRR and RPKI data current.
• Set a max-prefix limit on the session. Our 25 covers today's announcements with room for new sites.
• Send your own and your customers' routes only — no default route, no static routes pointed at us, no transit across the session.
• Tell us ahead of maintenance that will drop the session, and expect the same from us.

Technical

• IPv6 is where our traffic lives; our IPv4 footprint is two /24s, so expect a short v4 prefix list. Dual-stack or IPv6-only sessions are both fine.
• Multiprotocol BGP over IPv6. MD5 is not required; we will enable it if your side wants it. BFD on request.
• We peer over exchange route servers where they exist, and over PNI.
• Both public exchange and private interconnect are fine. We do not treat one as a favor to the other.

Where

The first two sites to carry our own address space are US East (Northern Virginia) and US Central (Dallas); US West (Portland) follows. That space is being brought into service, so ask us what is live at the location you have in mind and we will tell you plainly rather than list intentions here.

Abuse

Traffic out of our space is traceable to a named account on our side. Reports go to [email protected], are acknowledged within 24 hours, and confirmed abuse ends with the account, sending domain or link suspended. See how to report abuse and our acceptable use policy.