asn.dev

Observed topology

AS21107 BLICNET-AS Blicnet d.o.o. Banja Luka

Unclassified RIPE

Upstreams 2 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 1
Upstream graph Who carries AS21107, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS21107 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21107: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS25144"Telekomunikacije Republike Srpske" akcionarsko drustvo Banja LukaUnclassifiedIPv43,173
AS5603Telekom Slovenije, d.d.MobileIPv4 IPv61,666

Transit

Downstream networks

inferred

Networks for which AS21107 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS39826Terc Trade Company d.o.o.UnclassifiedIPv4264
AS201719Teleklik d.o.o.UnclassifiedIPv424

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS21107 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS25144"Telekomunikacije Republike Srpske" akcionarsko drustvo Banja LukaUnclassifiedIPv43,325
AS5603Telekom Slovenije, d.d.MobileIPv4 IPv61,666
AS39826Terc Trade Company d.o.o.UnclassifiedIPv4264
AS8400TELEKOM SRBIJA a.d.ResidentialIPv4136
AS201719Teleklik d.o.o.UnclassifiedIPv424

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.