ixreport

HOSTOWEB: PeeringDB fix list

AS37738 · peeringdb.com/net/34470

PeeringDB

3 things to fix in HOSTOWEB's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.

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

  1. Romania DSIX Bucharest, Romania · PeeringDB 3477From its IX-F export and website members list
    IPv4185.0.0.5
    IPv62001:7f8:133::20:5897: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.

Correct these entries (2)

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. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs100G1G
    • In the entry with IPv4 185.1.170.198: set Speed to 1000 (1G) (now 100000).
  2. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs100G1G
    • In the entry with IPv4 185.1.192.231: set Speed to 1000 (1G) (now 100000).

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