ixreport

Voiceflex: PeeringDB fix list

AS24594 · peeringdb.com/net/1853

PeeringDB

One thing to fix in Voiceflex's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Voiceflex'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.

  1. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB5.57.81.2525.57.81.251 5.57.81.252
    Port speed differs5G2 × 5G
    • Add an entry: IPv4 5.57.81.251, IPv6 –, speed 5000 (5G), RS peer yes.

    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.

From ixreport.com/net/24594/: 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.