Times Internet: PeeringDB fix list
AS55705 · peeringdb.com/net/13708
One thing to fix in Times Internet's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Times Internet'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.
-
Problem PeeringDB has The export has IPv6 address differs 2401:7500:fff6::101 2401:7500:fff6::1ab 2401:7500:fff6::101 2401:7500:fff6::146 2401:7500:fff6::20c IPv4 address in PeeringDB, not in the export 103.27.170.45 103.27.170.63 103.27.170.81 103.27.171.60 103.27.170.45 103.27.170.63 103.27.170.81 Port speed differs 4 × 10G 5 × 10G - In the entry with IPv4 103.27.170.45: set IPv6 to 2401:7500:fff6::20c (now empty).
- In the entry with IPv4 103.27.170.63: set IPv6 to 2401:7500:fff6::146 (now empty).
- The entry with IPv4 103.27.171.60, IPv6 2401:7500:fff6::1ab isn't in the export: delete it if that connection is gone.
From ixreport.com/net/55705/: 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.