Netnod Oslo BLUE -- MTU9K: operator report

Oslo, Norway · PeeringDB 4855 · ixreport.com/ix/4855/report/

Download CSV

Members of Netnod Oslo BLUE -- MTU9K that PeeringDB has wrong, from its IX-F export (6 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 5 networks to follow up; 2 with a public PeeringDB contact.

Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.

On your lists, missing from PeeringDB (3)

These networks could add Netnod Oslo BLUE -- MTU9K to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS12552 GlobalConnect AS12552 PeeringDBIX-F 194.153.157.10
2001:7f8:d:500::10
Policy: email address (needs JavaScript)
AS20940 Akamai Technologies PeeringDBIX-F 194.153.157.8
2001:7f8:d:500::8
No public contact
AS200781 Tampnet PeeringDBIX-F 194.153.157.9
2001:7f8:d:500::9
Policy: email address (needs JavaScript)

Addresses or port speeds that differ (0)

PeeringDB against your IX-F export, for the 3 networks in both. Either the network's PeeringDB record or the export is out of date.

None: every network's addresses and port speed match.

In PeeringDB, not on your lists (2)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

NetworkIn PeeringDBContact
AS9201 Swedish Armed Forces PeeringDB 194.153.157.7
2001:7f8:d:500::7
10G
No public contact
AS212232 BGP.Tools Route Collector PeeringDB 194.153.157.5
2001:7f8:d:500::5
1G
No public contact