asn.dev

Observed topology

AS39396 NBIS-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS39396: 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
AS61071NETBOX LTDUnclassifiedIPv4352
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv6199
AS6939Hurricane Electric LLCTransitIPv472
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv625
AS41313"NOVATEL" EOODUnclassifiedIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv613
AS34019Hivane AssociationUnclassifiedIPv4 IPv613
AS401753BIXCE IncUnclassifiedIPv4 IPv613
AS20764CJSC RASCOMUnclassifiedIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197168ASPhostBG LtdUnclassifiedIPv461

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS61071NETBOX LTDUnclassifiedIPv4365
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv6213
AS6939Hurricane Electric LLCTransitIPv478
AS197168ASPhostBG LtdUnclassifiedIPv461
AS41313"NOVATEL" EOODUnclassifiedIPv4 IPv641
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv614
AS34019Hivane AssociationUnclassifiedIPv4 IPv614
AS401753BIXCE IncUnclassifiedIPv4 IPv614
AS20764CJSC RASCOMUnclassifiedIPv413

All 13 adjacent →

Provenance

Where this comes from

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