asn.dev

Observed topology

AS198524 ILOL iLOL d.o.o.

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS198524: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv635
AS44306OMONIA d.o.o.UnclassifiedIPv4 IPv624
AS174Cogent Communications, LLCTransitIPv4 IPv620
AS21283A1 Slovenija telekomunikacijske storitve,d.d.ResidentialIPv49
AS56635XENYA inzeniring, proizvodnja in trgovina, d.o.o. LjubljanaUnclassifiedIPv44
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv62
AS3303Swisscom (Schweiz) AGResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197944Virtua IT d.o.o.UnclassifiedIPv437
AS44073Zdravstveni Dom LjubljanaUnclassifiedIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv644
AS6939Hurricane Electric LLCTransitIPv4 IPv644
AS197944Virtua IT d.o.o.UnclassifiedIPv437
AS44306OMONIA d.o.o.UnclassifiedIPv4 IPv628
AS56635XENYA inzeniring, proizvodnja in trgovina, d.o.o. LjubljanaUnclassifiedIPv413
AS44073Zdravstveni Dom LjubljanaUnclassifiedIPv412
AS21283A1 Slovenija telekomunikacijske storitve,d.d.ResidentialIPv49
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS3303Swisscom (Schweiz) AGResidentialIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.