ixreport

Fusionnet Web Services

AS134375

Fusionnet Web Services Private Limited

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Fusionnet Web Services? · Where should Fusionnet Web Services peer next? · Compare Fusionnet Web Services with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Fusionnet Web Services's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Fusionnet Web Services's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. India DE-CIX Delhi Delhi, India · PeeringDB 2587
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G + 60G
    • In the entry with IPv4 103.27.168.70: set Speed to 60000 (60G) (now 10000).

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where Fusionnet Web Services's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 130G across 4 exchanges.

India DE-CIX Delhi Delhi, India 103.27.168.70 2400:d180:67::70 10G Yes Both Speed differs
India Extreme IX Delhi Delhi, India 45.120.248.48 2001:df2:1900:1::48 100G Yes PeeringDB
India Extreme IX Mumbai Mumbai, India 103.77.108.45 2001:df2:1900:2::45 10G Yes PeeringDB
India NIXI Delhi Delhi, India 218.100.48.43 10G Yes PeeringDB

Exchanges in its buildings that it isn't on (4)

These exchanges have a switch in a facility where Fusionnet Web Services lists itself in PeeringDB, but don't have Fusionnet Web Services as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

India ANI-IX DelhiDelhi, India 30 Sify Greenfort - Noida
India MX-IX DelhiDelhi, India 9 Sify Greenfort - Noida
India Insta-IX DelhiDelhi, India 8 Sify Greenfort - Noida
India Fiblib Digital NetworksNew Delhi, India 4 Sify Greenfort - Noida
Facilities (1)

The buildings Fusionnet Web Services lists in PeeringDB, and how many of the exchanges in each it's on.

India Sify Greenfort - NoidaNoida 3 of 7