asn.dev

Internet exchange

Norwegian Internet Exchange Oslo 2

active Oslo, Norway OSL

Recorded members 26 addresses on file
Connected ports 13 across all participants
Peak traffic 4.5 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Oslo, Norway
Region
Europe
Airport code
OSL
Status
Active
PCH record updated
2022-02-28

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
185.1.65.0/26IPv4Active13
2001:7f8:12:2::/64IPv6Active13

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

26 shown

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS42WoodyNet, Inc.185.1.65.26Open
AS42WoodyNet, Inc.2001:7f8:12:2::42Open
AS2119Telenor Norge AS185.1.65.2ti100001b051-ge4-0.ti.telenor.netSelective
AS2119Telenor Norge AS2001:7f8:12:2::2119Selective
AS2116GLOBALCONNECT AS2001:7f8:12:2::2116te2-0-2.br1.osls.as2116.netSelective
AS2116GLOBALCONNECT AS185.1.65.3Selective
AS3856Packet Clearing House, Inc.2001:7f8:12:2::3856Open
AS3856Packet Clearing House, Inc.185.1.65.27Open
AS25400Telia Norge AS185.1.65.9Restrictive
AS25400Telia Norge AS2001:7f8:12:2::2:5400Restrictive
AS29695Lyse Tele AS185.1.65.16
AS29695Lyse Tele AS2001:7f8:12:2::2:9695
AS12996Domeneshop AS2001:7f8:12:2::1:2996Open
AS12996Domeneshop AS185.1.65.11nix2-gw.domeneshop.noOpen
AS224Sikt - Kunnskapssektorens Tjenesteleverandor185.1.65.1tullin-gw1.uninett.noOpen
AS224Sikt - Kunnskapssektorens Tjenesteleverandor2001:7f8:12:2::224tullin-gw1.uninett.noOpen
AS15659NextGenTel AS185.1.65.12
AS15659NextGenTel AS2001:7f8:12:2::1:5659
AS25148Orange Business Digital Norway AS2001:7f8:12:2::2:5148Open
AS25148Orange Business Digital Norway AS185.1.65.17osl3-gw1-nix2.osl.basefarm.netOpen
AS56828Norsk Helsenett SF2001:7f8:12:2::5:6828Open
AS56828Norsk Helsenett SF185.1.65.22Open
AS39787TV 2 AS185.1.65.18nix2.tv2.noOpen
AS39787TV 2 AS2001:7f8:12:2::3:9787nix2-ipv6.tv2.noOpen
AS33079INET SYS CONSORTIUM, INC.2001:7f8:12:2::3:3079Open
AS33079INET SYS CONSORTIUM, INC.185.1.65.24nix2.r2.osl1.isc.orgOpen

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.