Hi3G Access AB: PeeringDB fix list

AS44034 · peeringdb.com/net/1876

PeeringDB

3 things to fix in Hi3G Access AB'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 Hi3G Access AB'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 Hi3G Access AB's PeeringDB record. Add one entry per connection with these values.

  1. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.166
    IPv62001:7f8:d:fb::166
    SpeedNot published
    RS peerYes

Check these entries (2)

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

  1. Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868Not on its IX-F export
    IPv4212.237.192.166
    IPv62001:7f8:d:202::166
    Speed100000 Mbps (100G)
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.166
    IPv62001:7f8:d:ff::166
    Speed100000 Mbps (100G)

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