asn.dev

Observed topology

AS43022 UA-SEECH Seech-Infocom Ltd.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43022: 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
AS199995Omega Telecom LLCResidentialIPv4333
AS15895"Kyivstar" PJSCMobileIPv4189
AS35297Dataline LLCUnclassifiedIPv445
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv619
AS6939Hurricane Electric LLCTransitIPv617
AS24482SG.GSHostingIPv4 IPv610
AS29632Netassist International EOODUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56610TOV "Global-NET"UnclassifiedIPv4134
AS60754Dianet Ltd.UnclassifiedIPv4117
AS31468PRJSC "ZAZ"UnclassifiedIPv467
AS42671ZAPOROZHELECTRONSNAB PKF LTDUnclassifiedIPv467
AS42714Kichkas Network Ltd.UnclassifiedIPv428
AS9202GYUSS PKF LTDUnclassifiedIPv47
AS210572"NETPIPE" LLCUnclassifiedIPv46

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS199995Omega Telecom LLCResidentialIPv4539
AS15895"Kyivstar" PJSCMobileIPv4272
AS56610TOV "Global-NET"UnclassifiedIPv4134
AS35297Dataline LLCUnclassifiedIPv4125
AS60754Dianet Ltd.UnclassifiedIPv4117
AS31468PRJSC "ZAZ"UnclassifiedIPv467
AS42671ZAPOROZHELECTRONSNAB PKF LTDUnclassifiedIPv467
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv445
AS42714Kichkas Network Ltd.UnclassifiedIPv428
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv627

Provenance

Where this comes from

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