Issue 02 / 2026 Metro Peering opens in Mumbai — one session, three IXPs Read more →
Peering, Colocation & CDN

Buy peering once. Reach every IX in the metro.

One BGP session at an Esto POP gives a downstream network consolidated reach to all the IXPs in that metro — NIXI, Extreme-IX, and DE-CIX in Delhi or Mumbai — without joining each exchange, paying three sets of port fees, or running three sessions. Plus rack, half-rack and cage colocation at our POPs, and cache hosting for the content networks your eyeballs actually pull from.

Read the spec sheet →
1 session
Per metro · every IX in it
3 IXPs
NIXI · Extreme-IX · DE-CIX
2 metros
Delhi · Mumbai
GGC · FNA · OCA
Caches hosted at our POPs
§ 01What’s included

One interconnect. Three jobs done.

01Metro Peering

One session, every exchange in the metro.

We hold the memberships, the port costs, and the route mediation at NIXI, Extreme-IX and DE-CIX. You bring up a single BGP session at our Delhi or Mumbai POP and inherit the whole metro’s peering reach — route-server fan-out or selective direct sessions, your call.

  • ReachNIXI + Extreme-IX + DE-CIX
  • SessionsRoute-server or direct
  • MetrosDelhi · Mumbai
02Colocation

Rack, half-rack, or a caged footprint.

Space at our four POPs — single units up to a full cage — with metered or committed power, N+1 cooling, and cross-connects to the Esto fabric or any other tenant in-building. Remote hands are on the floor 24×7 so you don’t fly an engineer out for a reboot.

  • FootprintRack · half · cage
  • PowerMetered or committed kVA
  • Hands24×7 remote hands
03Cache hosting

The content caches, already inside.

Google GGC, Meta FNA, and Netflix OCA run in our POPs today — so the heavy eyeball traffic is served from inside the building at single-digit-millisecond RTT, off your transit bill. Open to additional cache nodes from other networks on request.

  • LiveGGC · FNA · OCA
  • BenefitOff-transit · low RTT
  • OpenMore nodes on request
04Cross-connects

Patch to anyone in the building.

Single-mode fibre cross-connects from your rack to the Esto edge, to a cache node, or to any carrier and content network present in the same facility. Provisioned to the meet-me-room, documented, and billed flat — no per-bit metering on a cross-connect.

  • MediaSingle-mode fibre
  • TargetsEsto edge · cache · in-building
  • BillingFlat per cross-connect
05Route security

Signed, filtered, and capped by default.

Every session runs MD5 authentication, a max-prefix limit, and RPKI route-origin validation — invalids dropped, not de-prefed. IRR-built prefix filters on direct sessions. The same hygiene we run on the backbone, applied to your peering edge.

  • AuthMD5 · max-prefix
  • ValidationRPKI ROV · invalids dropped
  • FiltersIRR-built on direct sessions
§ 02Metro Peering

Two metros. One session each.

Metro Peering — DelhiPOP · BLR-free · GK1 / Noida

1
BGP session
  • NIXI Delhi ~2,400 prefixes
  • Extreme-IX Delhi ~3,100 prefixes
  • DE-CIX Delhi ~4,900 prefixes
Aggregate reach
~9,400+ prefixes
Networks
~180+ ASNs
Port options
1G · 10G · 100G
Sessions
Route-server / direct

Metro Peering — MumbaiPOP · Web Werks

1
BGP session
  • NIXI Mumbai ~3,200 prefixes
  • Extreme-IX Mumbai ~4,600 prefixes
  • DE-CIX Mumbai ~7,800 prefixes
Aggregate reach
~14,200+ prefixes
Networks
~260+ ASNs
Port options
1G · 10G · 100G
Sessions
Route-server / direct

IPv4 + IPv6 on every session · MD5 + RPKI ROV throughout. Prefix and ASN counts are indicative of current exchange reach and move with the exchanges — confirmed live in your RFQ.

§ 03Content delivery

The caches are already racked.

Cache nodes hosted

Google, Meta, and Netflix caches inside our POPs — eyeball traffic served from in-building, single-digit-millisecond RTT, and off your transit bill.

GGC
FNA
OCA

Private network interconnects

Off-IX bilateral interconnects so the heaviest flows don’t ride a shared fabric — direct to the source, capacity dedicated.

PNI
PNI
PNI
§ 04Spec sheet

The parameters, in full.

Metro PeeringSessions
One BGP session per metro aggregates every exchange in it. Route-server fan-out or selective direct sessions.
ExchangesIXPs aggregated
NIXI · Extreme-IX · DE-CIX — in Delhi and Mumbai.3 IXPs · 2 metros
Port speedsPeering handoff
1 Gbps · 10 Gbps · 100 Gbps  —  single-mode fibre at the POP cross-connect.
Address familiesIP version
IPv4 + IPv6 on every session.v6 default
Route securityHygiene
MD5 + max-prefix on every session · RPKI ROV with invalids dropped · IRR-built prefix filters on direct sessions.
ColocationFootprints
Rack · half-rack · cage at our POPs · metered or committed kVA · N+1 cooling · 24×7 remote hands.
Cross-connectsIn-building
Single-mode fibre to the Esto edge, a cache node, or any carrier / content network in-building. Flat-billed, not metered.
Cache hostingCDN
Google GGC · Meta FNA · Netflix OCA live at our POPs. Open to additional cache nodes from other networks on request.
FacilitiesPOPs
Noida (Sify Greenfort) · Delhi (GK1) · Mumbai (Web Werks) · Patna (CtrlS). Peering & cache in Delhi + Mumbai.
SLAService level
99.95% availability · 4-hour MTTR target · 24×7 NOC escalation.

Prefix and ASN counts move with the exchanges — confirmed live per RFQ. Figures are standard offerings; non-standard builds are quoted per RFQ.

§ 05Use cases

Who buys this, and why.

Regional ISP

Skip three IX memberships, keep all three exchanges.

A Tier-3 ISP wants Delhi peering but can’t justify joining NIXI, Extreme-IX and DE-CIX separately — three sets of dues, three ports, three sessions to babysit. One session at our Delhi POP and it inherits the lot, with route security handled.

1 session · 3 IXPs · Delhi
Content / CDN

Put the cache where the eyeballs already are.

A content network wants its node close to regional subscribers without standing up its own facility. It racks a cache at our Mumbai POP, cross-connects to the Esto fabric, and serves the downstream ISPs at in-building RTT.

Cache node · cross-connect · Mumbai
DC / enterprise

A cage, the power, and a patch to everyone.

An operator needs a caged footprint with committed power and diverse cross-connects to carriers and content in the same building — plus remote hands so a 02:00 IST reboot doesn’t mean a flight. One contract covers space, power, and the patches.

Cage · committed kVA · cross-connects
§ 06FAQ

Questions operators ask.

01What exactly is Metro Peering?+
A single BGP session at an Esto POP that aggregates every internet exchange in that metro. Instead of joining NIXI, Extreme-IX and DE-CIX one by one — each with its own membership, port, and session — you bring up one session with us in Delhi or Mumbai and receive the combined routes of all three. We carry the memberships, the port costs, and the route mediation.
02Route-server fan-out, or direct sessions?+
Either. Most networks take the route-server fan-out — one session, all the metro's routes, simplest to run. If you want selective control over specific peers, we'll set up direct sessions with IRR-built prefix filters instead. You can also mix: route-server for the long tail, direct for the heavy hitters.
03Do you enforce RPKI?+
Yes. Every session runs RPKI route-origin validation and we drop invalids rather than de-preferencing them, alongside MD5 authentication, a max-prefix limit, and — on direct sessions — IRR-built prefix filters. It's the same hygiene we run on the backbone, applied to your peering edge.
04Can I place my own cache node in your POP?+
Yes. We already host Google GGC, Meta FNA, and Netflix OCA, and we're open to additional cache nodes from other content networks. You colo the node, we cross-connect it to the fabric, and downstream ISPs reach it at in-building RTT. Power, space, and the cross-connect are covered in one quote.
05What colocation footprints do you offer?+
From a single rack unit up to a full cage — rack, half-rack, or caged — with metered or committed kVA, N+1 cooling, and cross-connects to the Esto edge or any tenant in-building. Remote hands are staffed 24×7, so routine reboots, reseats, and media swaps don't need your engineer on a plane.
06Which POPs can I peer and colo at?+
Colocation is available at all four POPs — Noida (Sify Greenfort), Delhi (GK1), Mumbai (Web Werks), and Patna (CtrlS). Metro Peering and hosted caches sit where the exchanges are: Delhi and Mumbai. A cross-connect or leased line extends reach to a POP without a presence in-building.
§ 07Request a quote

Tell us what you need. We’ll come back in 24 hours.