Phibee Telecom: PeeringDB fix list
AS8487 · peeringdb.com/net/1250
2 things to fix in Phibee Telecom's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Phibee Telecom'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 Phibee Telecom's PeeringDB record. Add one entry per connection with these values.
-
nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France · PeeringDB 4705From its IX-F exportIPv4 185.1.14.65 IPv6 2001:7f8:12e::8487:1 Speed 10000 Mbps (10G) 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.
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 Port speed differs 10G 2G - In the entry with IPv4 80.249.210.196: set Speed to 2000 (2G) (now 10000).
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/8487/: 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.