asn.dev

Observed topology

AS15624 OKITECH-AS OKITECH Krzysztof Kusnierczyk

Residential RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS15624: 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
AS219062Nera sp z.o.oUnclassifiedIPv4117
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv482
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv439
AS47329WDM Sp. z o.o.UnclassifiedIPv414
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv43
AS212261Stowarzyszenie e-PoludnieUnclassifiedIPv43
AS24482SG.GSHostingIPv42
AS8551Bezeq International Ltd.UnclassifiedIPv41
AS12859BIT BVHostingIPv41

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS219062Nera sp z.o.oUnclassifiedIPv4117
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv482
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv439
AS47329WDM Sp. z o.o.UnclassifiedIPv414
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv43
AS212261Stowarzyszenie e-PoludnieUnclassifiedIPv43
AS24482SG.GSHostingIPv42
AS8551Bezeq International Ltd.UnclassifiedIPv41
AS12859BIT BVHostingIPv41

Provenance

Where this comes from

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