ixreport

Vertex: PeeringDB fix list

AS149513 · peeringdb.com/net/29247

2 things to fix in Vertex's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Vertex'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 Vertex's PeeringDB record. Add one entry per connection with these values.

  1. Singapore SGIX Singapore, Singapore · PeeringDB 429From its IX-F export and website members list
    IPv4103.16.102.31
    IPv62001:de8:12:100::31
    Speed10000 Mbps (10G)
    RS peerYes

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. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB103.16.102.31 is AS37468 Angola Cables103.16.102.31
    Address belongs to another network in PeeringDB2001:de8:12:100::31 is AS37468 Angola Cables2001:de8:12:100::31

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

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