TVP Operations Company: PeeringDB fix list
AS4857 · peeringdb.com/net/22158
3 things to fix in TVP Operations Company's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on TVP Operations Company'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 (3)
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 missing from PeeringDB none 2001:7fa:11:1:0:12f9:0:1 - In the entry with IPv4 218.100.78.91: set IPv6 to 2001:7fa:11:1:0:12f9:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 500M - In the entry with IPv4 218.100.53.55: set Speed to 500 (500M) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 103.26.69.28 103.26.68.219 103.26.69.28 IPv6 address missing from PeeringDB 2001:dea:0:10::11c 2001:dea:0:10::db 2001:dea:0:10::11c - Add an entry: IPv4 103.26.68.219, IPv6 2001:dea:0:10::db, RS peer yes.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/4857/: 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.