ixreport

Quest Consultancy

AS58659 · QuesT

Quest Consultancy Pvt Ltd

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
2To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Quest Consultancy? · Where should Quest Consultancy peer next? · Compare Quest Consultancy with another network

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

PeeringDB fix list Printable page · CSV

2 things to fix in Quest Consultancy's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Quest Consultancy'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 (2)

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 AMS-IX Mumbai Mumbai, India · PeeringDB 1623
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:e48:44:100b:0:a505:8659:1
    • In the entry with IPv4 223.31.200.75: set IPv6 to 2001:e48:44:100b:0:a505:8659:1 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs10G5G
    • In the entry with IPv4 103.27.170.164: set Speed to 5000 (5G) (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 Quest Consultancy'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 33G across 4 exchanges.

India AMS-IX Mumbai Mumbai, India 223.31.200.75 10G Down Both IPv6 not in PeeringDB
India DE-CIX Mumbai Mumbai, India 103.27.170.164 2401:7500:fff6::164 10G Yes Both Speed differs
India Extreme IX Mumbai Mumbai, India 103.77.108.151 2001:df2:1900:2::151 10G Yes PeeringDB
India NIXI Mumbai Mumbai, India 103.156.182.35 2001:de8:1:1::38 3G Yes PeeringDB

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

These exchanges have a switch in a facility where Quest Consultancy lists itself in PeeringDB, but don't have Quest Consultancy 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 (1)

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

India Equinix MB1 - Mumbai (GPX Mumbai 1)Mumbai 4 of 7