39D is an official participant in MANRS — Mutually Agreed Norms for Routing Security. We implement practical controls that reduce route leaks, route hijacks, spoofed traffic and operational risk across BGP-based networks.
MANRS participants commit to recognised routing-security actions and ongoing conformance. For our clients and peers, this provides an independent trust signal that secure routing is part of the way we design and operate networks.
Our public participant profile provides the authoritative external reference for our MANRS status.
Customer and peer announcements are controlled with explicit prefix filters, prefix-length limits, maximum-prefix protection, bogon filtering, IRR checks and RPKI Route Origin Validation.
Read our BGP filtering guideNetwork designs use source-address validation and anti-spoofing controls aligned with BCP 38 and BCP 84, applied at appropriate customer, access and edge boundaries.
Accurate NOC, abuse and peering contacts, documented escalation paths and active monitoring help incidents reach the right engineers quickly.
Contact Matthew SouthgateIRR route objects, RPKI ROAs, public ASN information and documented routing policies make announcements easier for other networks to validate.
View AS34979 informationValidate route origins and identify invalid announcements before they can influence routing policy.
Compare advertised prefixes and origin ASNs against maintained routing registry data.
Accept only authorised networks and expected prefix lengths from customers and peers.
Contain accidental leaks or unexpected route growth before it impacts the wider network.
Block invalid, reserved and inappropriate source or destination ranges at network boundaries.
Monitor BGP sessions, route counts, origin changes and policy exceptions across the edge.
I help ISPs, hosting companies, MSPs and enterprise networks assess their current routing posture and implement the controls needed for a secure, supportable BGP environment.
Yes. Our official MANRS participant profile is linked directly from this page.
No. MANRS provides a clear set of expected actions, but they still need to be implemented through real routing policy, monitoring, operational procedures and accurate public data.
Yes. A review can cover filtering, anti-spoofing, RPKI, IRR records, PeeringDB, operational contacts, route monitoring and evidence required to demonstrate good routing practice.
Yes. Reviews can cover MikroTik RouterOS as well as mixed environments involving carrier, open-source and enterprise routing platforms.