asn.dev

Observed topology

AS43966 ITREGION-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43966: 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
AS57304JSC "RetnNet"UnclassifiedIPv4482
AS6939Hurricane Electric LLCTransitIPv4149
AS31133PJSC MegaFonMobileIPv4127
AS44843MSS LLC.UnclassifiedIPv4105
AS31500Global Network Management IncUnclassifiedIPv420
AS9002RETN LimitedUnclassifiedIPv418
AS24482SG.GSHostingIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv416
AS34927iFog GmbHHostingIPv412
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50741ARIS Kart SPB LtdUnclassifiedIPv460
AS29493Federal State Budget Institution Petersburg Institute of Nuclear Physics of B.P. KonstantinovUnclassifiedIPv48

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS57304JSC "RetnNet"UnclassifiedIPv4506
AS6939Hurricane Electric LLCTransitIPv4158
AS31133PJSC MegaFonMobileIPv4137
AS44843MSS LLC.UnclassifiedIPv4106
AS50741ARIS Kart SPB LtdUnclassifiedIPv460
AS31500Global Network Management IncUnclassifiedIPv439
AS9002RETN LimitedUnclassifiedIPv419
AS24482SG.GSHostingIPv417
AS37721Virtual Technologies & SolutionsResidentialIPv417
AS34927iFog GmbHHostingIPv412

All 12 adjacent →

Provenance

Where this comes from

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