// Network at a glance
Adelia Networks
Pending allocation
Open
London + Manchester, UK
peering@netbrands.eu
noc@netbrands.eu
// Peering requirements
Peers must maintain an up-to-date and accurate PeeringDB record. This is the primary source of truth for all technical peering data including prefixes, NOC contacts, and IXP presence.
MandatoryAll announced prefixes must be registered in a public Internet Routing Registry (IRR) â RIPE, ARIN, APNIC, RADB, etc. RPKI Route Origin Validation (ROV) is strongly encouraged. We filter based on IRR data and will not accept unregistered prefixes.
MandatoryPeers must agree to reasonable prefix limits. Adelia Networks will configure maximum prefix limits per session. Announcing more prefixes than declared in PeeringDB will result in the session being dropped after prior notification.
MandatoryNeither party shall announce a default route (0.0.0.0/0 or ::/0) to the other. Peering is strictly for the exchange of each network's own prefixes and customer routes.
MandatoryPeers must not announce prefixes that are not legitimately originating from their AS or their customers. Re-advertising transit routes or routes learned from other peers through the peering session is strictly prohibited.
MandatoryPeers must provide a 24/7 reachable NOC contact for routing incidents, abuse reports, and emergency communications. Response time for critical routing issues should not exceed 4 hours.
MandatoryDual-stack peering (IPv4 + IPv6) is strongly preferred. We encourage all peers to operate IPv6-enabled networks and will prioritize dual-stack sessions. IPv6-only peering is also possible.
PreferredAdelia Networks supports standard BGP communities for traffic engineering. Peers are encouraged to tag routes with appropriate communities for visibility and ease of troubleshooting. Details available on request.
PreferredWe do not enforce a minimum traffic threshold for peering. We welcome peering requests from networks of all sizes, including emerging ISPs, research networks, and content providers.
No minimum// Internet Exchange Points
// Technical details
We drop RPKI Invalid routes. ROV enforced on all sessions.
All prefixes filtered against IRR. Unregistered routes rejected.
All our prefixes are covered by ROA entries. We sign everything.
BFD available upon request for fast failure detection on IXP sessions.
Standard and extended communities supported. Details on request.
MD5 session authentication available on request for added security.
// Get in touch
Send your peering request to our dedicated peering team. Please include your ASN, PeeringDB URL, preferred IXP, and IP addresses you'd like to use for the BGP session. We typically respond within 24â48 hours on business days.
noc@netbrands.eu
abuse@netbrands.eu
Available on request