Modern and redundant network.
Every IBEE region is connected to the public internet through tier-1 carriers and to the rest of our footprint through a dedicated private backbone, so you can plan routing before a single VM boots.
Three separate networks.
Every server connects to the public internet, our global private backbone, and an out-of-band management plane, each on its own physical fabric.
Public internet
Multi-homed across at least two tier-1 carriers per region with direct peering at local exchanges. BGP-ready the day you provision.
Private backbone
A dedicated L3 fabric connects every IBEE region. Physical and logical isolation, move data between sites with no public-internet hop.
Out-of-band management
A separate management network for console, IPMI, and break-glass access. Survives a full data-plane outage in the primary fabric.
Magic TransitDDoS protection by Cloudflare.
IBEE prefixes are announced via BGP into Cloudflare's edge, so Layer 3 DDoS attacks are scrubbed at the nearest of 330+ cities, not at a distant scrubbing center. Clean traffic reaches our regions over a private interconnect, always-on.
Cloudflare Magic TransitAvailable IP carriers
Every region is multi-homed across at least two tier-1 carriers. We publish the list so you can plan BGP, anycast, and failover strategy ahead of provisioning.
Test files
Validate real-world throughput into every IBEE region. Copy a host and pull a 100 MB or 1000 MB sample from your side of the internet.
| Location | Host | 100 MB | 1000 MB |
|---|---|---|---|
AMR Amaravati, India | test.amr.ibee.ai | ||
HYD1 Hyderabad, India | test.hyd1.ibee.ai | ||
IAD Ashburn, USA | test.iad.ibee.ai |
Public network
Average round-trip times on the public internet between every IBEE site.
| From · To → | Amaravati · AMR | Hyderabad · HYD | Ashburn · IAD |
|---|---|---|---|
| Amaravati · AMR | < 1ms | 12ms | 232ms |
| Hyderabad · HYD | 12ms | < 1ms | 228ms |
| Ashburn · IAD | 232ms | 228ms | < 1ms |
Private backbone
The same matrix over our private backbone, lower jitter, shorter paths, and no public-internet hop between IBEE regions.
| From · To → | Amaravati · AMR | Hyderabad · HYD | Ashburn · IAD |
|---|---|---|---|
| Amaravati · AMR | < 1ms | 8.0ms | 215ms |
| Hyderabad · HYD | 8.0ms | < 1ms | 210ms |
| Ashburn · IAD | 215ms | 210ms | < 1ms |
Bring your ASN. We'll do the peering.
Custom BGP sessions, cross-connects, and private interconnects are supported in every region. Share your routing diagram and we'll plan the rest.