Dynamic routing with each cloud and your sites; private ASNs planned for you.
XcellNetwork|Cloud Router
One managed router between your offices, your racks and every cloud you use.
XcellHost runs a virtual router in our Mumbai Tier IV data centre that speaks BGP to AWS, Azure, Google Cloud and Oracle, keeps each environment in its own VRF and fails over on its own — monitored 24×7 by our NOC.
Every cloud has its own router. You need one that talks to all of them.
AWS, Azure, Google Cloud and Oracle each give you a routing service inside their own network — and each stops at the edge of that network. Once you run workloads in two clouds, an office or two and a rack in a data centre, someone has to decide which prefix goes where, what happens when a link drops and which environment may talk to which. Done with hand-edited static routes, that turns into outages after every change.
XcellHost Cloud Router is a managed virtual router hosted in our Mumbai Tier IV data centre. It peers over BGP with each cloud's own routing service and with your on-premises routers, carries static routes where BGP isn't available, separates environments in VRFs and filters every route it learns. Our engineers design the routing policy with you, deploy it and watch it 24×7 from the NOC.
What the router does — and what each cloud calls its half.
The cloud providers use different names for similar jobs. Pick one to see what it does and how XcellHost Cloud Router connects to it.
For devices and links that can't run BGP, with tracking so dead routes are pulled.
Separate routing tables for prod, dev, partners or subsidiaries on one router.
Prefix lists, communities, local-preference and AS-path prepend to steer traffic.
Fast failure detection where the peer supports it; backup paths pre-installed.
Dual-stack sessions where the cloud side supports IPv6 peering.
NAT or VRF separation when two networks use the same address range.
Two router instances with separate paths so one failure doesn't stop routing.
AWS Transit Gateway is AWS's transit hub for VPCs and on-premises networks. Per AWS, it takes VPC, VPN, Direct Connect gateway, Connect (SD-WAN appliance) and peering attachments, each associated with a transit gateway route table; VPN and Direct Connect gateway attachments exchange routes with your router over BGP.
How we connect: BGP from Cloud Router to a Direct Connect gateway over a Private Connect circuit, or to a Site-to-Site VPN as backup. TGW route tables stay in your AWS account.
Azure connects private circuits through an ExpressRoute virtual network gateway. Azure Route Server, per Microsoft, is a managed service that exchanges routes over BGP between network virtual appliances and the virtual network, acting as a route reflector. Virtual WAN is Microsoft's hub-and-spoke option for larger estates.
How we connect: BGP over an ExpressRoute circuit (private peering), or IPsec + BGP to a VPN gateway. Where you run an NVA in Azure, Route Server learns its routes.
Google Cloud Router, per Google, is a fully managed service that runs BGP sessions and turns learned routes into dynamic routes in your VPC — it doesn't forward packets itself. Dedicated and Partner Interconnect VLAN attachments and HA VPN require it; it supports custom route advertisements, BFD and MD5 authentication.
How we connect: our router peers with your Google Cloud Router over a Partner or Dedicated Interconnect VLAN attachment, or over HA VPN tunnels.
On Oracle Cloud Infrastructure, private circuits and VPNs attach to a Dynamic Routing Gateway (DRG), which routes between your VCNs and on-premises networks. FastConnect private peering uses BGP between your edge and Oracle.
How we connect: BGP over a FastConnect virtual circuit in Mumbai or Hyderabad through a partner, or IPsec VPN to the DRG. See Oracle Cloud.
A hub in Mumbai, a spoke for every network you own.
Pick a VRF to see which spokes it reaches. Each VRF keeps its own routing table, so the dev network never learns a route to production.
Diagram and route tables are sample data. Circuit types per spoke depend on what each site and provider offers — confirmed in design.
Same router, different routing problems.
Core banking on-prem, analytics in the cloud
Keep the core system and its data in India, send only approved datasets to a cloud analytics VRF, and log every route change for the auditor.
- Separate VRFs for core, analytics and vendor access
- Prefix lists so vendors see only their subnets
- Route-change records kept for 180 days
Plants, ERP and a cloud MES
Plants on SD-WAN, ERP in a colocation rack and a cloud-hosted MES — with plant networks that often reuse the same 192.168.x.x range.
- NAT or VRFs for overlapping plant subnets
- Backup paths so a plant link cut doesn't stop dispatch
- See Managed SD-WAN for the plant edge
Hospital systems and cloud PACS
Imaging archives move to the cloud while the HIS stays local; clinical and guest traffic must never mix.
- Clinical, admin and guest VRFs
- Imaging routes preferred over the private line
- Routing that supports DPDP safeguards for patient data
Multi-cloud SaaS with a customer-dedicated tier
Run in two clouds, peer with large customers privately and keep staging away from production.
- BGP to AWS and Google Cloud from one hub
- A VRF per enterprise customer link
- Route changes reviewed like code, applied in a window
Stores, warehouses and a cloud storefront
Hundreds of small sites, a payment network that must stay separate and a cloud storefront that peaks on sale days.
- Card-payment traffic in its own VRF
- Store routes summarised to keep tables small
- Backup path pre-installed before sale events
Campuses, labs and government cloud
Several campuses, research labs that need cloud burst, and departments that must stay apart.
- One VRF per department or campus
- Cloud burst routes for labs only
- XcellHost is MeitY empanelled
Designed with you, deployed in a window, watched every minute after.
The same network team surveys, designs, deploys and then runs your routing from the XcellHost NOC.
Inventory of sites, clouds, address plans and existing routing. Output: an IP plan, ASN plan, VRF map and route policy you sign off.
Router built, sessions brought up one at a time, failover pulled on purpose and timed — inside a change window you approve.
Session state, prefix counts and flaps alerted around the clock; changes through ticket and approval.
Routing records your auditor can actually read.
A router alone doesn't make you compliant. Logged changes, kept in India and separated networks help you meet these obligations.
CERT-In directions, April 2022
CERT-In asks organisations to report specified cyber incidents within 6 hours of noticing them and to keep ICT system logs for 180 days within India. Cloud Router session, change and flow logs are kept in Mumbai for at least that period, ready to hand to your incident team.
Asks for reasonable security safeguards for personal data. VRF separation and filtered routes limit who can reach systems that hold it.
Regulated entities face IT governance, network segmentation and outsourcing expectations. Route policies and change records support those reviews.
Cloud Router routes your own networks. Internet transit and last-mile circuits come from licensed providers through partner exchanges* — confirmed per site.
The router and its logs run in our Mumbai Tier IV data centre; cloud regions in India are reachable from it.
Pick by peers and VRFs. Monitoring is always included.
Indicative — confirm with XcellHost. All prices exclude 18% GST. Cloud provider gateway, port and data-transfer fees are billed by the cloud provider, per their pricing.
- Up to 4 BGP sessions
- 1 VRF
- Static routes with tracking
- 24×7 NOC monitoring
- Up to 16 BGP sessions
- 4 VRFs included
- Route policies, communities, BFD
- IPv6 dual-stack
- Sessions and VRFs to your design
- Routers in partner PoPs*
- Named network engineer*
- Quarterly routing review
* Indicative placeholder — confirm with XcellHost. Router plans and extra VRF are placeholders. IPsec site link ₹4,999 (Hybrid Cloud), cross-connect ₹2,999 (Co-Location), public IPv4 ₹299 (Virtual Networks) and onboarding ₹24,999 (Network Operations) are reused from those XcellHost pages. Private circuits are priced on Private Connect.
Build your router — see the monthly bill with GST.
Fixed-price items go to the cart at price × quantity. Cloud-side charges stay with the cloud provider.
Two networks, one address range? Find it before you peer.
Overlapping CIDRs are the most common reason a new cloud link "works" but traffic goes nowhere. List your networks — the checker runs in your browser and nothing is sent.
Ready to run BGP with the cloud? Ten questions tell you.
Tick what is already true for your network. The score shows what to fix first and which plan fits.
—
Static routes, cloud-native only, or one managed hub.
Six steps from address plan to first route.
Scroll — the packet moves along as each step completes.
- 01Discovery call
Sites, clouds, circuits and what must talk to what.
- 02IP & ASN plan
Overlaps found, private ASNs assigned, VRFs named.
- 03Route policy
Prefix lists, preferences and failover order agreed.
- 04Build
Router deployed in Mumbai; circuits and tunnels ordered.
- 05Bring-up & test
Sessions up one by one; failover pulled and timed.
- 06Hand-over to NOC
Alerts live, runbook shared, monthly report starts.