What is a cloud BGP route server?
A cloud BGP route server is an external BGP neighbour that hands your router ready-made, curated sets of routes, so you never deploy, tune and maintain a BGP service of your own.
You bring up a single eBGP session, subscribe to the categories you need, and the routes arrive and keep updating on their own — no manual exports, no config reloads. No daemon to run, no policies to write and no prefix lists to keep.
A category can hold both prefixes and domains: you enter networks directly in your account, and BGPCast resolves domains into their current prefixes over DNS on a schedule. Addresses behind a domain change; the category is described once, by name, and stays current.
This is not a VPN or a proxy: no traffic passes through BGPCast, the session carries routes and a BGP community tagging the category, nothing more. What your router does with them — a separate routing table, a tunnel, or a drop — stays your decision.
Features
Peers
Bring up BGP sessions with your routers — MikroTik, FRR, BIRD. eBGP multihop out of the box.
Connector agent
Router behind NAT or CGNAT — the agent re-advertises the routes over BGP locally. Keenetic, OpenWrt, MikroTik in a container.
Categories
Ready-made sets of prefixes and domains. Subscribe and the routes are advertised to your router.
Domain → prefix
Route by domain name: BGPCast resolves domains to current prefixes over DNS.
Own prefixes
Announce and filter your own prefixes. Per-peer isolation — each peer sees only its own routes.
Audit log
A full change log: who changed what and when in your configuration.
How it works
Peer your router
Establish a BGP session with the BGPCast route server — parameters are in the app.
Choose your categories
Select ready-made categories of prefixes and domains, or build your own.
Routes on your router
Prefixes are advertised to your router over BGP and update automatically.
How this differs from running your own BGP daemon
| BGPCast | Your own BGP daemon | |
|---|---|---|
| What you run | One eBGP session from your router | A VM, a daemon, monitoring, backups |
| Who curates the route sets | The service — categories update themselves | You: collect, verify, publish |
| Domains in routing | Resolved into prefixes over DNS | Your own resolver and generator |
| Router behind NAT or CGNAT | The connector agent | Your problem to solve |
| What it takes to start | Sign-up and a private ASN | Running a BGP daemon yourself |
FAQ
What is BGPCast?
A cloud BGP route server: connect your router over BGP and receive curated route sets organised into categories of prefixes and domains.
Which routers are supported?
Any router with BGP support. You'll find ready-to-use commands for MikroTik (RouterOS 7.23+), FRR, and BIRD 2 in the Knowledge Base.
What is a category?
A named set of prefixes and domains. Once you subscribe to a category, your router receives its routes; you can also build your own category.
How do I connect?
Sign up, create a peer in the app, and bring up a BGP session following the Knowledge Base instructions.
Why resolve domains to prefixes?
To route by domain name: BGPCast periodically resolves the domain via DNS and announces the current prefixes to your router.