Telecall AS62663: PeeringDB fix list
AS62663 · peeringdb.com/net/19905
5 things to fix in Telecall AS62663's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Telecall AS62663'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 Telecall AS62663's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 195.66.231.91 IPv6 2001:7f8:4::f4c7:1 Speed 200 Mbps (200M) RS peer Yes
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 Port speed differs 2 × 100G 500M + 250M - In the entry with IPv4 80.249.211.109: set Speed to 250 (250M) (now 100000).
- In the entry with IPv4 80.249.212.130: set Speed to 500 (500M) (now 100000).
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 200G - In the entry with IPv4 80.81.196.104: set Speed to 200000 (200G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 200M 10G - In the entry with IPv4 178.18.236.22: set Speed to 10000 (10G) (now 200).
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/62663/: 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.