Acceptable use policy · version 2026-09-12
The rules, in full.
1. Who may connect. Networks that hold a public ASN and can prove it through PeeringDB or through the contacts in their RIR objects. One connection per ASN per site unless we agree otherwise.
2. What may enter the peering LAN. IPv6 and ARP frames from the MAC address you registered, or from the second one if we granted you one. No spanning tree, LLDP, CDP, router advertisements, DHCPv6, IGP hellos or proxy ND. Multicast and broadcast are rate-limited per member. Frames outside this are dropped, and repeated violations lead to suspension.
3. What may be announced. Only prefixes you are authorised to originate or carry, covered by a route6 object reachable from your AS-SET, by a ROA, or by both. Announcing prefixes you do not control, more-specifics of another member's prefixes, or RPKI-invalid routes is grounds for immediate disconnection.
4. Route-server hygiene. Do not point a default route or a static route at the peering LAN. Do not use the LAN as transit towards a network you do not have a session with. Honour the communities other members set.
5. Abuse. Answer notices sent to your registered contact within 24 hours. We act on reports of hijacking and on evidence from public route collectors. A member found hijacking is disconnected within the hour, and we publish what happened. Bulletproof hosting, spam sources and networks under active abuse reports are not welcome here.
6. Suspension. DATAHUB, LLC may suspend any member at any time for a breach of this policy or to protect other members. A suspension removes the connection and both route-server sessions at once and you are told by email what triggered it. Ending your membership is a separate step, covered by the member agreement.
7. Data. We publish your ASN, network name, site, LAN address, the state of your route-server sessions and the date you joined, on the members page and in the IX-F export. Your MAC address, your contact address and your tunnel endpoint are not published. For traffic graphs we keep five-minute totals per MAC pair; we do not capture packets and we do not store raw flow records. We do not sell anything to anyone.
8. No service level. The community tier is free and provided as it is. We run it as production and we publish its real state, but we give no availability commitment on it.
9. Changes. Changes are announced by email to your registered NOC address 14 days before they take effect, and continued use is acceptance. The version you accepted is recorded with a timestamp.