asn.dev

Observed topology

AS3226 MARK-ITT-AS OOO "NI"

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3226: 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
AS12389PJSC RostelecomResidentialIPv4 IPv6565
AS50384iHome LLCUnclassifiedIPv449
AS25478iHome LLCUnclassifiedIPv410
AS20764CJSC RASCOMUnclassifiedIPv69
AS1299Arelion Sweden ABTransitIPv65
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS38959LLC "RadioLink"UnclassifiedIPv4150
AS43781CORPORACIA HLEBNITSA LLCUnclassifiedIPv445
AS52217OOO ISKRAUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6695
AS38959LLC "RadioLink"UnclassifiedIPv4150
AS50384iHome LLCUnclassifiedIPv449
AS43781CORPORACIA HLEBNITSA LLCUnclassifiedIPv445
AS25478iHome LLCUnclassifiedIPv444
AS1299Arelion Sweden ABTransitIPv4 IPv637
AS20764CJSC RASCOMUnclassifiedIPv69
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv62
AS52217OOO ISKRAUnclassifiedIPv41

Provenance

Where this comes from

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