Tripleplay Broadband: PeeringDB fix list
AS132453 · peeringdb.com/net/6330
3 things to fix in Tripleplay Broadband's PeeringDB record, from what its exchanges publish: 2 to add, 1 to check. As of 2026-10-08 22:13 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 (2)
On the exchange's own member list, but not in Tripleplay Broadband's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.27.170.226 IPv6 2401:7500:fff6::1eb Speed 3000 Mbps (3G) RS peer Yes -
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Tripleplay Broadband has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 45.120.248.96 IPv6 2001:df2:1900:1::96 Speed 100000 Mbps (100G)
From ixreport.com/net/132453/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.