asn.dev

Observed topology

AS39310 NITRONET

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39310: 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
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4114
AS1299Arelion Sweden ABTransitIPv455
AS12741Netia SAResidentialIPv422
AS24482SG.GSHostingIPv43
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15902maciej grzeszczukUnclassifiedIPv465
AS48208Narodowe Archiwum CyfroweUnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4196
AS1299Arelion Sweden ABTransitIPv497
AS15902maciej grzeszczukUnclassifiedIPv465
AS48208Narodowe Archiwum CyfroweUnclassifiedIPv463
AS12741Netia SAResidentialIPv422
AS24482SG.GSHostingIPv45
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv44

Provenance

Where this comes from

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