BGP and peering review
Typical length: 2 to 3 weeks from receiving your data.
How a BGP and peering review runs
You send configs and flow data
Router configurations (we read them; we don’t log in), two weeks of sFlow, NetFlow or IPFIX from the edge, and your current transit and IX invoices. We sign an NDA first.
We map what’s there
Every BGP session and what it carries, import and export policy, filtering and max-prefix limits, RPKI state, and how traffic splits across transit, IX and private peering.
We rank what to change
A short report: what each change saves or protects, how risky it is, and the order to do it in.
We walk your team through it
A working session with your engineers. If you want us to make the changes, that becomes a separate, scoped piece of work.
What you send
- Configuration exports from your edge and border routers
- Two weeks of sFlow, NetFlow or IPFIX from the edge, or exports from your flow collector
- Your transit and IX prices, or the invoices
- A list of your IXs and private interconnects, if it isn’t obvious from the configs
What you get
- A written report with a ranked list of changes: the saving or risk reduction, the effort and the risk of each
- Configuration snippets for the first changes, for your platform
- Peering candidates with the traffic each one would move
- A working session with your engineers to go through it
user@edge1> show bgp summaryGroups: 4 Peers: 6 Down peers: 2Peer AS Flaps Last Up/Dwn State192.0.2.1 64496 2 6w2d3h Establ inet.0: 412/415/415/0a198.51.100.9 64497 14 4w1d22h Active203.0.113.33 64499 0 12w0d4h Establb inet.0: 18211/18211/18211/0c2001:db8:0:7::33 64499 1 9w4d1h Connect- aDown for four weeks. Nobody was paged, because the alerts only fire when a session changes state.
- bA peer that should announce a few hundred prefixes is sending 18,211, and no max-prefix limit is set to stop a leak.
- cThe IPv6 session to the same peer never came up, so its IPv6 traffic leaves over transit.
What we look at
- Every BGP session: state, uptime, flaps and what it carries
- Import and export policy, communities and local preference
- Filtering: IRR prefix lists, bogons, max-prefix limits and RPKI origin validation
- How traffic splits between transit, IX and private peering, and what each path costs
- Networks you could peer with at IXs you’re already on
- How each session is protected: authentication, limits and filters
Questions about the review
Do you sign an NDA?
Yes, before you send anything.
Do you need access to our routers?
No. The review works from configuration exports and flow data. Nobody logs in to your network.
Which platforms do you cover?
Juniper Junos, Arista EOS, IP Infusion OcNOS, MikroTik RouterOS and Cisco IOS and IOS XR. If you run something else, ask.
Request a review
Tell us a little about the network. We’ll reply within one business day with what we need from you and when we can start.