asn.dev

Internet exchange

Bosnia and Herzegovina Neutral Internet Exchange

active Sarajevo, Bosnia and Herzegovina SJJ

Recorded members 24 addresses on file
Connected ports 10 across all participants
Peak traffic 14.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
Sarajevo, Bosnia and Herzegovina
Region
Europe
Airport code
SJJ
Status
Active
PCH record updated
2026-08-08

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.133.0/24IPv4Active10
2001:7f8:d7::/64IPv6Active10

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

24 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.2001:7f8:d7::64Open
AS42WoodyNet, Inc.185.1.133.64Open
AS9119SOFTNET d.o.o.185.1.133.15Open
AS9119SOFTNET d.o.o.2001:7f8:d7::9119Open
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)2001:7f8:d7::62Open
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)185.1.133.62Open
AS3856Packet Clearing House, Inc.185.1.133.65Open
AS3856Packet Clearing House, Inc.2001:7f8:d7::65Open
AS197000Reseaux IP Europeens Network Coordination Centre (RIPE NCC)185.1.133.63Open
AS197000Reseaux IP Europeens Network Coordination Centre (RIPE NCC)2001:7f8:d7::63Open
AS9146BH Telecom d.d. Sarajevo2001:7f8:d7::9146Selective
AS9146BH Telecom d.d. Sarajevo185.1.133.12Selective
AS42560Telemach BH d.o.o. Sarajevo2001:7f8:d7::4:2560Open
AS42560Telemach BH d.o.o. Sarajevo185.1.133.14Open
AS16178Logosoft , information engineering and Internet providing185.1.133.13Open
AS16178Logosoft , information engineering and Internet providing2001:7f8:d7::1:6178Open
AS8670University of Sarajevo185.1.133.11Open
AS8670University of Sarajevo2001:7f8:d7::8670Open
AS209098University of Sarajevo185.1.133.10Open
AS209098University of Sarajevo2001:7f8:d7::20:9098Open
AS48443UNIV OF SARAJEVO2001:7f8:d7::1Open
AS48443UNIV OF SARAJEVO185.1.133.129Open
AS48443UNIV OF SARAJEVO185.1.133.1Open
AS48443UNIV OF SARAJEVO2001:7f8:d7::129Open

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.