asn.dev

Observed topology

AS42303 FIBERDIREKT

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42303: 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
AS1299Arelion Sweden ABTransitIPv4 IPv61,430
AS174Cogent Communications, LLCTransitIPv4495
AS6939Hurricane Electric LLCTransitIPv4415
AS24482SG.GSHostingIPv441
AS31500Global Network Management IncUnclassifiedIPv428

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57238Sheimo Scorpion Data ABUnclassifiedIPv457
AS199780Binero ABUnclassifiedIPv457
AS51701Adminor AktiebolagUnclassifiedIPv450
AS29468Infracom Managed Services ABResidentialIPv46
AS49303Niscayah Group ABUnclassifiedIPv45

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,505
AS174Cogent Communications, LLCTransitIPv4584
AS6939Hurricane Electric LLCTransitIPv4436
AS57238Sheimo Scorpion Data ABUnclassifiedIPv457
AS199780Binero ABUnclassifiedIPv457
AS51701Adminor AktiebolagUnclassifiedIPv450
AS24482SG.GSHostingIPv444
AS31500Global Network Management IncUnclassifiedIPv428
AS39889Fredrik HolmqvistHostingIPv413
AS29468Infracom Managed Services ABResidentialIPv46

Provenance

Where this comes from

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