asn.dev

Observed topology

AS201986 Arpinet Arpinet LLC

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201986: 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
AS9002RETN LimitedUnclassifiedIPv4347
AS8932Ucom CJSCUnclassifiedIPv4 IPv6199
AS12297Telecom Armenia OJSCUnclassifiedIPv4147

Transit

Downstream networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS200896Arpinet LLCUnclassifiedIPv4244
AS207980TINS LLCUnclassifiedIPv4 IPv6211
AS210315Arpinet LLCUnclassifiedIPv4183
AS8226Arpinet LLCUnclassifiedIPv4181
AS205277Interlink LLCUnclassifiedIPv4180
AS207991ACHON LLCUnclassifiedIPv4118
AS34083Arpinet LLCUnclassifiedIPv461
AS197805Dzoraghbyur Complex LLCUnclassifiedIPv461
AS198265I-NET LLCUnclassifiedIPv460
AS209778Armcom LLCUnclassifiedIPv453

All 12 downstreams →

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv41,066
AS8932Ucom CJSCUnclassifiedIPv4 IPv6619
AS12297Telecom Armenia OJSCUnclassifiedIPv4425
AS200896Arpinet LLCUnclassifiedIPv4244
AS207980TINS LLCUnclassifiedIPv4 IPv6211
AS8226Arpinet LLCUnclassifiedIPv4188
AS210315Arpinet LLCUnclassifiedIPv4183
AS205277Interlink LLCUnclassifiedIPv4180
AS207991ACHON LLCUnclassifiedIPv4118
AS34083Arpinet LLCUnclassifiedIPv461

All 15 adjacent →

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.