ixreport

Tripleplay Broadband

AS132453

Tripleplay Broadband Pvt Ltd

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

Tools: Where can I peer with Tripleplay Broadband? · Where should Tripleplay Broadband peer next? · Compare Tripleplay Broadband 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 Tripleplay Broadband's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 18:41 UTC.

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

Add these exchanges (1)

On the exchange's own member list, but not in Tripleplay Broadband's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Mumbai Mumbai, India · PeeringDB 832From its IX-F export
    IPv4103.27.170.226
    IPv62401:7500:fff6::1eb
    Speed3000 Mbps (3G)
    RS peerYes

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 differs10G20G
    • In the entry with IPv4 103.27.168.193: set Speed to 20000 (20G) (now 10000).

Exchanges over time

0246Oct 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, 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 Tripleplay Broadband'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 133G across 4 exchanges.

India DE-CIX Delhi Delhi, India 103.27.168.193 2400:d180:67::c8 10G Yes Both Speed differs
India DE-CIX Mumbai Mumbai, India 103.27.170.226 2401:7500:fff6::1eb 3G Yes Not in PeeringDB
India Extreme IX Delhi Delhi, India 45.120.248.96 2001:df2:1900:1::96 100G Yes PeeringDB
India NIXI Delhi Delhi, India 103.218.244.40
218.100.48.40
2001:de8:1::18 2 × 10G PeeringDB

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

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

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

India STTGDC DEL2Delhi 3 of 5
India TATA Communications DelhiNew Delhi 2 of 5
India TATA Communications ChennaiChennai 0 of 3
India NIXI Noida NetmagicNoida No exchange