Website & Hosting
VPS & Dedicated
Infrastructure
Marketplace
Gati Cloud
Resources
India
Global
Login
BGP Connectivity · ASN · Multihoming

Enterprise BGP Connectivity to Control Every Route.

Build resilient internet connectivity with Border Gateway Protocol. Custom routing, IP announcements, ASN integration and multi-provider network design for eligible enterprise, colocation and infrastructure environments.

ASN Integration Use your own ASN, or plan BGP with our network team.
IP Announcements Announce eligible IPv4 and IPv6 prefixes.
Multi-Homing Multi-provider design for resilient connectivity.
Route Engineering Routing policy designed around your traffic.
IPv4 & IPv6 Prefixes Single & Dual Upstream Colocation BGP DDoS Integration
BGP Connectivity Proposal FREE ROUTING REVIEW

Request a BGP Connectivity Proposal

Share your ASN, prefixes and routing requirements. Our network team will review them and recommend a BGP architecture.

Optional — details help our team design the right routing. 0 / 1500
Secure submission Network team review Custom route design
What is BGP connectivity

Routing Control Between Networks

Border Gateway Protocol (BGP) is used to exchange routing information between autonomous networks on the internet. It allows a network to advertise its IP prefixes and select routing paths across multiple providers.

For enterprises, BGP provides greater control over redundancy, routing policy, IP portability and upstream connectivity. HostGraber supports BGP for eligible enterprise, colocation and infrastructure environments.

  • Announce

    Advertise eligible IP prefixes to upstream networks

  • Learn

    Receive routing information from connected peers

  • Select

    Choose preferred paths using routing policy

  • Fail over

    Use alternate paths when conditions change

Multi-homed BGP architectureTwo upstream providers connect to your BGP edge router. Routing policy prefers the primary path through upstream A and fails over to upstream B. Your ASN announces your IP prefixes to both upstreams.PRIMARYFAILOVERROUTESUpstream AISP / transitUpstream BAlternate pathYour ASNBGP edge routerRouting policyeBGP sessionsYour networkYour IP prefixes
Illustrative. Final routing design depends on ASN, prefix ownership, upstream providers, BGP policy, redundancy requirements and network topology.
BGP connectivity solutions

Routing Built Around Your Network

From announcing a single prefix to a fully multi-homed architecture, BGP connectivity is designed around your ASN, address space and redundancy goals.

ASN integration

Incorporate your Autonomous System Number into supported network architectures.

IP prefix announcement

Advertise eligible IPv4 or IPv6 address space through supported BGP sessions.

Multi-provider connectivity

Redundant network paths across multiple upstream sources, where available.

Routing policy design

Route preferences based on business and network requirements.

Colocation BGP

Integrate customer networks and routers within eligible colocation deployments.

Custom BGP architecture

Routing designed around ASN, IP blocks, upstreams, redundancy and traffic.

Request BGP Connectivity Proposal
Multi-homing and routing policy

Resilient Paths, Precise Control

BGP multi-homing connects your network to multiple upstream providers. If one path becomes unavailable, routing can shift to another available path according to your configured policy.

  • Local preference

    Influence outbound path selection within the supported routing architecture.

  • AS path prepending

    Influence inbound route preference where appropriate.

  • Prefix filtering

    Control which eligible routes are accepted or advertised.

  • Route policies

    Apply routing controls around operational requirements.

  • Primary and backup paths

    Preferred and alternate connectivity paths, where supported.

  • Custom routing design

    Policies designed around upstreams, destinations and redundancy objectives.

Routing comparison

Static Routing vs BGP

Static routing suits simple networks with a single path. BGP is designed for networks that need multiple upstreams, their own ASN and control over how traffic flows.

AspectStatic routingBGP
Route managementManualDynamic
Multiple upstreamsLimitedDesigned for it
Own ASNNot requiredCommon use
Traffic engineeringLimitedAdvanced
Best forSimple networksEnterprise and multi-homed networks

Need address space to announce? Explore IP services →

Technical capabilities

BGP Connectivity, Engineered for Resilience

BGP at HostGraber is part of a broader network architecture, planned together with IP services, security and colocation.

BGP sessions

eBGP for eligible deployments

ASN

Customer ASN integration

IPv4

Eligible prefix announcements

IPv6

Eligible IPv6 routing

Multi-homing

Multi-upstream architecture where available

Route policies

Filtering, preference and path engineering

Security

Firewall and DDoS integration

Architecture

Custom routing design

Plan Your BGP ArchitectureDiscuss on WhatsApp
Why HostGraber

BGP as Part of a Complete Network

BGP is one layer of a broader network architecture. HostGraber combines routing with IP services, DDoS protection, firewall, private networking, cross connects, colocation and infrastructure monitoring.

Talk to Our Network Team
  • ASN integration
  • IPv4 and IPv6 routing
  • Multi-upstream architecture
  • Routing policy design
  • Firewall and DDoS integration
  • Network consulting
  • Control routes
  • Improve resilience
  • Build better networks
Use cases

Advanced Routing for Network-Driven Businesses

  1. 01

    Hosting providers

    Announce address space and control upstream paths.

  2. 02

    ISPs and network operators

    Exchange routes with upstream networks.

  3. 03

    Colocation customers

    Connect customer routers within the facility.

  4. 04

    SaaS platforms

    Resilient connectivity for customer-facing services.

  5. 05

    Enterprise data centres

    Redundant internet paths for critical infrastructure.

  6. 06

    Multi-site networks

    Consistent routing across locations.

  7. 07

    Private cloud

    Routed public connectivity for cloud platforms.

  8. 08

    Own ASN and IP holders

    Use your own ASN and address space.

Deployment process

From Requirement Review to Route Validation

  1. 01REVIEW

    Requirement review

    We review your ASN, prefixes, upstreams and routing requirements.

  2. 02VALIDATE

    Prefix validation

    Eligible IPv4 or IPv6 resources and routing requirements are reviewed.

  3. 03DESIGN

    Routing design

    Peerings, preferences, filters and redundancy are planned.

  4. 04DEPLOY

    Session deployment

    Approved BGP sessions and network policies are configured.

  5. 05VERIFY

    Route validation

    Announcements, route selection and failover behaviour are validated.

Start Your Routing Review
BGP insights

Enterprise BGP Connectivity: ASN, Prefixes and Multi-Homing

An overview for network teams planning BGP: how routes are exchanged, what is needed to announce address space and how routing policy shapes resilience.

How BGP connectivity works

The internet is made up of autonomous systems, independent networks each identified by an Autonomous System Number. BGP is the protocol these networks use to tell one another which IP prefixes they can reach.

In a typical deployment, your edge router establishes external BGP (eBGP) sessions with one or more upstream providers. Your router announces your prefixes, receives routes in return and selects the best path for each destination according to routing policy.

ASN and prefix requirements

Announcing address space through BGP requires a few resources to be in place. Each is reviewed during the prefix validation stage.

RequirementWhat it meansNotes
ASNYour network's routing identityCommonly used for public eBGP; requirement depends on architecture
IP prefixesThe IPv4 / IPv6 blocks you announceEligibility and authorisation are reviewed
Prefix sizeThe length of each announced blockIPv4 /24 and IPv6 /48 are widely accepted minimums
Routing registryPublic records of your routesRoute objects and RPKI ROAs support route acceptance
Edge routerEquipment that runs your BGP sessionsCustomer or managed, depending on deployment

Multi-homing and failover

A single-homed network depends on one upstream path. A multi-homed network maintains BGP sessions with two or more upstreams, so an outage on one path does not remove the network from the internet.

In a correctly designed multi-homed environment, routing converges toward another available path according to the configured policy. Designs typically define a primary path for normal operation and an alternate path for failover, or share traffic across upstreams.

Traffic engineering with routing policy

Routing policy determines how traffic enters and leaves your network:

  • Local preference influences which upstream your outbound traffic uses
  • AS path prepending makes a path less attractive to influence inbound traffic
  • Prefix filtering controls which routes are accepted and advertised
  • Primary and backup paths define preferred and alternate connectivity

For public-facing networks, BGP routing is commonly combined with DDoS protection and a firewall as part of a layered architecture.

Preparing for a BGP deployment

The following information allows our network team to review your requirements efficiently:

  • Your ASN, or the status of your ASN application
  • IPv4 and IPv6 prefixes to be announced
  • Single upstream, dual upstream or multi-homing requirement
  • Estimated bandwidth and preferred routing behaviour
  • Colocation, DDoS protection or firewall requirements

Share these details through the BGP connectivity proposal form and our team will recommend a routing architecture.

BGP glossary

Key BGP Terminology

BGP
Border Gateway Protocol: the routing protocol used to exchange routes between autonomous networks on the internet.
eBGP
External BGP: a BGP session between two different autonomous systems, such as your network and an upstream provider.
ASN
Autonomous System Number: the unique identifier of a network that participates in BGP routing.
Prefix
A block of IP addresses, such as an IPv4 /24, announced through BGP.
Upstream / transit
A provider that carries your traffic to and from the rest of the internet.
Multi-homing
Connecting a network to two or more upstream providers for redundancy.
Local preference
A BGP attribute used to prefer one outbound path over another.
AS path prepending
Repeating an ASN in announcements to make a path less preferred for inbound traffic.
Prefix filtering
Rules that control which routes are accepted from or advertised to peers.
RPKI / ROA
A security framework in which Route Origin Authorisations confirm which ASN may announce a prefix.
Frequently asked questions

BGP Connectivity Questions Answered

Have a question about your ASN, prefixes or upstreams? Share your requirements and our network team will advise.

Ask Our Network Team
What is BGP connectivity?

BGP connectivity allows autonomous networks to exchange routing information and advertise eligible IP prefixes to other networks.

Do I need an ASN for BGP?

Public eBGP deployments commonly use an Autonomous System Number. The exact requirement depends on the routing architecture.

Can I announce my own IPv4 block?

Eligible IPv4 resources can be reviewed for announcement through supported BGP connectivity.

Can IPv6 prefixes be announced?

Yes. Eligible IPv6 resources can be incorporated into supported BGP architectures.

Can I connect to multiple ISPs using BGP?

Yes. Multi-homed BGP architectures can use multiple upstream paths where the required connectivity is available.

What happens if one upstream goes down?

In a correctly designed multi-homed environment, routing can converge toward another available path according to the configured policies.

Can BGP work with DDoS protection?

Yes. BGP routing and DDoS mitigation can be integrated within supported network protection architectures.

Does HostGraber provide BGP network consulting?

Yes. ASN integration, prefix announcements, route policies, multi-homing and network architecture can be reviewed according to your requirements.

Can I use BGP in colocation?

Yes. Customer networks and routers can be integrated with BGP within eligible colocation deployments.

How do I get started with BGP connectivity?

Complete the BGP connectivity proposal form with your ASN status, prefix and connectivity requirements. Our network team will review them and recommend a routing architecture.

Enterprise BGP connectivity

Control Routes. Improve Resilience.

Tell us about your ASN, prefixes and upstream requirements. Our network team will recommend a BGP architecture.

Request BGP Connectivity Quote Discuss on WhatsApp
A better foundation for what’s next

Build what’s next. We’ll power it.

From business websites to demanding workloads, find the hosting and cloud infrastructure that fits your next move.

Web Hosting Fast & managed
Cloud Built to scale
Dedicated Bare metal power
Infrastructure Built for growth
Hosting · Cloud · Compute · Infrastructure Built by HostGraber