ixreport

Texes Connect

AS136306 · TEXES

Texes Connect Private Limited

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

Tools: Where can I peer with Texes Connect? · Where should Texes Connect peer next? · Compare Texes Connect with another network

This network elsewhere: the registry history of AS136278-AS136377, the block AS136306 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Texes Connect'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 differs10G1G
    • In the entry with IPv4 103.27.170.6: set Speed to 1000 (1G) (now 10000).

Exchanges over time

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

Map

Where Texes Connect'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 21G across 3 exchanges.

India DE-CIX Mumbai Mumbai, India 103.27.170.6 2401:7500:fff6::78 10G Yes Both Speed differs
India Extreme IX Delhi Delhi, India 45.120.248.219 2001:df2:1900:1::219 10G Yes PeeringDB
India NIXI Delhi Delhi, India 103.218.244.72 2001:de8:1::107 1G Yes PeeringDB

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

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

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

India Sify Greenfort - NoidaNoida 2 of 7
India TATA Communications GK1New Delhi 2 of 6
India Sify Rabale - MumbaiNavi Mumbai 1 of 3
India Sify Tidel-DC- ChennaiChennai 0 of 3
India Sify Airoli-DC- MumbaiMumbai 0 of 2
India Sify ITPL - BangaloreBangalore 0 of 2
India Sify Vashi - MumbaiNavi Mumbai 0 of 2

Recent changes Search them

  • Oct 5, 2026 [PDB] AS136306 Texes Connect now in PeeringDB at Extreme IX Delhi
  • Oct 4, 2026 AS136306 Texes Connect added to Extreme IX Delhi