A BGP (Border Gateway Protocol) session allows you to announce your own Autonomous System Number (ASN) and IP subnets directly over our network. You need it if you want absolute routing control, IP portability (keeping your IPs if you move data centers), IP Anycast setup, or if you are multihoming across multiple upstream transit providers for maximum redundancy.
To establish an eBGP session, you must possess a legally registered Autonomous System Number (ASN), valid and routable IPv4 or IPv6 subnets associated with your ASN, and you must provide a signed Letter of Authorization (LOA) permitting ServerMO to announce your prefixes on our network infrastructure.
Once you submit your ASN, IP subnets, and the signed LOA, our network engineering team verifies the documents with the respective Internet Registry (e.g., RIPE, ARIN, APNIC). Upon successful verification and payment of the one-time $100 setup fee, the BGP session is typically configured and brought live within 24 to 48 business hours.
We offer flexibility based on your router's hardware capacity. By default, we provide a default route or a partial routing table to conserve your router's memory. However, if your hardware supports it, we can provide the full global BGP routing table upon request.
Yes, our network is fully dual-stack. We support the announcement of both IPv4 prefixes (minimum /24) and IPv6 prefixes (minimum /48) through your eBGP session.
To protect our infrastructure and the global internet from route leaks and hijacking, we enforce strict inbound and outbound route filtering. All announced prefixes must be strictly validated against Internet Routing Registries (IRR) and RPKI (Resource Public Key Infrastructure) databases.
Absolutely. If you have deployments across multiple ServerMO global data centers, you can announce the same IP prefix via BGP in multiple locations simultaneously. This allows you to build a highly resilient, low-latency IP Anycast network for DNS servers or CDN edge nodes.
No. The $85 recurring monthly fee solely covers the maintenance, monitoring, and administrative overhead of the BGP peering session itself. Bandwidth usage, dedicated ports (e.g., 10Gbps or 100Gbps), and standard server costs are billed separately according to your chosen dedicated server plan.
