Veesp SIA: PeeringDB fix list

AS42532 · peeringdb.com/net/30861

PeeringDB

3 things to fix in Veesp SIA's PeeringDB record, from what its exchanges publish: 1 to add, 2 to check. As of 2026-10-08 20:58 UTC.

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.237.109
    IPv62a03:5f80:4:2::237:109
    Speed100000 Mbps (100G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Veesp SIA has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.210
    IPv62001:7f8:d:fe::210
    Speed100000 Mbps (100G)
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.210
    IPv62001:7f8:d:ff::210
    Speed100000 Mbps (100G)

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