BGP for ISPs
Well-configured Border Gateway Protocol is what makes your ISP's internet work — and what separates a stable provider from one that goes down every week.
What BGP is
BGP exchanges routes between Autonomous Systems (AS) on the internet. Every ISP with its own ASN needs to run BGP to announce IPv4/IPv6 prefixes and receive routes from upstreams and peers.
Bad BGP can take you off the internet, leak third-party routes (Pakistan/YouTube 2008 style) or create traffic loops that take down the backbone.
What RASYS does with BGP
- IX.br peering — onboarding, session setup and curation of routes received via route servers.
- Private peering — technical negotiation and session setup with CDNs (Google, Netflix, Meta, Cloudflare), IP transit and other ISPs.
- Prefix filtering — prefix-list, RPKI, max-prefix per session. Protects against leaks and unexpected more-specific routes.
- Communities and local-preference — traffic engineering to exit through the right upstream, with automatic fallback.
- eBGP/iBGP redundancy — full-mesh or route reflectors, BFD for sub-second session failure detection.
- RTBH (Remotely Triggered Blackhole) — BGP community to null-route attack destinations within milliseconds.
- Monitoring — Zabbix/LibreNMS tracking sessions UP/DOWN, prefixes received/announced, BGPmon for leak alerts.
Equipment we work with
Huawei NE8000/NE40/NE20, Juniper MX, Cisco ASR/IOS XR, Mikrotik RouterOS, Datacom DM, FRR/BIRD on Linux.
When it makes sense to talk to us
You don't have an ASN yet; want to reduce IP transit cost via IX; live with BGP sessions flapping; need to add a new upstream; suspect a route leak; want to deploy RPKI; merging networks after acquisition.
Talk to us — initial assessment is free. See also: OSPF, MPLS, BGP in glossary.