asn.dev

Observed topology

AS15645 AS15645 DE Ukrainian Internet Exchange UA-IX

Unclassified RIPE Route Server

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15645: 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
AS25372IT Consulting L.L.C.UnclassifiedIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS13188CONTENT DELIVERY NETWORK LTDResidentialIPv628
AS28994Sitel LtdUnclassifiedIPv621
AS25526LAMBDA LLCUnclassifiedIPv618
AS48641Syntegra Telecom LLCResidentialIPv61

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv665
AS25372IT Consulting L.L.C.UnclassifiedIPv459
AS29632Netassist International EOODUnclassifiedIPv652
AS60812"1-IX" LLCUnclassifiedIPv639
AS13188CONTENT DELIVERY NETWORK LTDResidentialIPv628
AS28994Sitel LtdUnclassifiedIPv621
AS25526LAMBDA LLCUnclassifiedIPv618
AS35320Eurotranstelecom LtdUnclassifiedIPv68
AS28907Internet Invest, Ltd.HostingIPv61
AS48641Syntegra Telecom LLCResidentialIPv61

All 11 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.