asn.dev

Observed topology

AS203971 AZFIBERNET-ASN AzFiberNet LLC

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203971: 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
AS196925Azertelecom LLCUnclassifiedIPv4 IPv6554
AS29049Delta Telecom LtdResidentialIPv4118

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205367NetPoint LLCUnclassifiedIPv4354
AS57675Seabak LLCUnclassifiedIPv4305
AS205317MAXINET LLCUnclassifiedIPv459
AS219253UNI COMMUNICATION SERVICES LLCUnclassifiedIPv459
AS216232NEOTELECOM SERVICES LLCUnclassifiedIPv436
AS39397Metronet LLCUnclassifiedIPv48
AS219485ELFIBER LLCUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS196925Azertelecom LLCUnclassifiedIPv4 IPv61,104
AS29049Delta Telecom LtdResidentialIPv4565
AS57675Seabak LLCUnclassifiedIPv4480
AS205367NetPoint LLCUnclassifiedIPv4354
AS205317MAXINET LLCUnclassifiedIPv459
AS219253UNI COMMUNICATION SERVICES LLCUnclassifiedIPv459
AS216232NEOTELECOM SERVICES LLCUnclassifiedIPv436
AS39397Metronet LLCUnclassifiedIPv48
AS219485ELFIBER LLCUnclassifiedIPv41

Provenance

Where this comes from

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