asn.dev

Observed topology

AS43576 KUMIR-AS

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43576: 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
AS57455Filanco Ukraine Ltd.UnclassifiedIPv4129
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv643
AS28917Fiord Networks, UABUnclassifiedIPv436
AS6939Hurricane Electric LLCTransitIPv614
AS3303Swisscom (Schweiz) AGResidentialIPv43
AS24482SG.GSHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50864IT TeleNet Ltd.UnclassifiedIPv4 IPv6424
AS21379LLC TC "Interzvyazok"UnclassifiedIPv4152
AS39049Kyivski Merezhi ltdUnclassifiedIPv4130
AS35365TOV Vica-TVUnclassifiedIPv478
AS41316FOP Pilipenko Olexandr OlexandrovichUnclassifiedIPv465
AS207085LLC "RACKPLACE"UnclassifiedIPv4 IPv65

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS57455Filanco Ukraine Ltd.UnclassifiedIPv4808
AS50864IT TeleNet Ltd.UnclassifiedIPv4 IPv6424
AS21379LLC TC "Interzvyazok"UnclassifiedIPv4190
AS28917Fiord Networks, UABUnclassifiedIPv4163
AS39049Kyivski Merezhi ltdUnclassifiedIPv4130
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv6116
AS35365TOV Vica-TVUnclassifiedIPv478
AS41316FOP Pilipenko Olexandr OlexandrovichUnclassifiedIPv465
AS6939Hurricane Electric LLCTransitIPv614
AS3303Swisscom (Schweiz) AGResidentialIPv413

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.