ixreport

Gigantic Infotel Pvt Ltd

AS133275 · Gigantic

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

Tools: Where can I peer with Gigantic Infotel Pvt Ltd? · Where should Gigantic Infotel Pvt Ltd peer next? · Compare Gigantic Infotel Pvt Ltd with another network

This network elsewhere: the registry history of AS133221-AS133320, the block AS133275 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Gigantic Infotel Pvt Ltd'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
    IPv4 address in PeeringDB, not in the export103.27.170.213 103.27.171.2103.27.170.213
    IPv6 address in PeeringDB, not in the export2401:7500:fff6::2c 2401:7500:fff6::2132401:7500:fff6::213
    Port speed differs2 × 10G3G
    • In the entry with IPv4 103.27.170.213: set Speed to 3000 (3G) (now 10000).
    • The entry with IPv4 103.27.171.2, IPv6 2401:7500:fff6::2c isn't in the export: delete it if that connection is gone.

Exchanges over time

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

Map

Where Gigantic Infotel Pvt Ltd'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 70G across 5 exchanges.

India DE-CIX Delhi Delhi, India 103.27.168.52 2400:d180:67::52 10G Yes Both
India DE-CIX Mumbai Mumbai, India 103.27.170.213
103.27.171.2
2401:7500:fff6::2c
2401:7500:fff6::213
2 × 10G Yes Both IPv4 not in exportIPv6 not in exportSpeed differs
India Extreme IX Delhi Delhi, India 45.120.248.22 2001:df2:1900:1::22 10G Yes PeeringDB
India NIXI Delhi Delhi, India 103.218.244.19
103.218.244.163
2001:de8:1::19
2001:de8:1::55
2 × 10G Yes PeeringDB
India NIXI Mumbai Mumbai, India 103.156.182.211 2001:de8:1:1::226 10G Yes PeeringDB

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

These exchanges have a switch in a facility where Gigantic Infotel Pvt Ltd lists itself in PeeringDB, but don't have Gigantic Infotel Pvt Ltd 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 Gigantic Infotel Pvt Ltd lists in PeeringDB, and how many of the exchanges in each it's on.

India Equinix MB1 - Mumbai (GPX Mumbai 1)Mumbai 2 of 7
India Sify Greenfort - NoidaNoida 3 of 7
India TATA Communications GK1New Delhi 3 of 6
India TATA Communications DelhiNew Delhi 2 of 5
India CtrlS Noida DC1Noida 3 of 3
India NTT Noida DC2AGreater Noida 2 of 2
India YOTTA D1Greater Noida 2 of 2
India NIXI GuwahatiGuwahati No exchange
India NIXI Noida NetmagicNoida No exchange