ixreport

xTom San Jose: PeeringDB fix list

AS6233 · peeringdb.com/net/19053

PeeringDB

3 things to fix in xTom San Jose's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 21:56 UTC.

Make the changes on xTom San Jose'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 (3)

On the exchange's own member list, but not in xTom San Jose's PeeringDB record. Add one entry per connection with these values.

  1. Norway FIXO Oslo, Norway · PeeringDB 453From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. Netherlands Speed-IX Dronten, Netherlands · PeeringDB 1842From its IX-F export
    IPv4185.1.222.84
    IPv62001:7f8:b7::a500:6233:1
    Speed1000 Mbps (1G)
    RS peerYes

    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/6233/: 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.