ixreport

iForce Networks

AS134858 · Oyenet Broadband Pvt Ltd

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

Tools: Where can I peer with iForce Networks? · Where should iForce Networks peer next? · Compare iForce Networks with another network

This network elsewhere: the registry history of AS134848-AS134947, the block AS134858 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in iForce Networks's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on iForce Networks'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 Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs2G1G
    • In the entry with IPv4 103.27.171.134: set Speed to 1000 (1G) (now 2000).

Exchanges over time

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

Map

Where iForce Networks'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 156G across 6 exchanges.

India AMS-IX Mumbai Mumbai, India 223.31.200.161 2001:e48:44:100b:a500:13:4858:1 1G Down Both
India DE-CIX Delhi Delhi, India 103.27.168.93 2400:d180:67::93 3G Yes PeeringDB only
India DE-CIX Mumbai Mumbai, India 103.27.171.134 2401:7500:fff6::c3 2G Yes Both Speed differs
India Extreme IX Delhi Delhi, India 45.120.248.52 2001:df2:1900:1::52 100G Yes PeeringDB
India Extreme IX Mumbai Mumbai, India 103.77.109.56 2001:df2:1900:2::62 10G Yes PeeringDB
India NIXI Delhi Delhi, India 103.218.244.52 2001:de8:1::17 40G Yes PeeringDB

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

These exchanges have a switch in a facility where iForce Networks lists itself in PeeringDB, but don't have iForce Networks 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.

Facilities (9)

The buildings iForce Networks lists in PeeringDB, and how many of the exchanges in each it's on.

India Equinix MB1 - Mumbai (GPX Mumbai 1)Mumbai 3 of 7
India Sify Greenfort - NoidaNoida 3 of 7
India Equinix MB2 - Mumbai (GPX Mumbai 2)Mumbai 3 of 6
India TATA Communications GK1New Delhi 3 of 6
India STTGDC DEL2Delhi 3 of 5
India CtrlS Noida DC1Noida 3 of 3
India STTGDC DEL1Delhi 0 of 2
India Web Werks NCR 2Noida 2 of 2
India Netmagic NoidaNoida 1 of 1

Recent changes Search them

  • Oct 27, 2026 [IXF] AS134858 iForce Networks dropped from DE-CIX Delhi's IX-F list (still in PeeringDB and on its website's members list)