asn.dev

Observed topology

AS12459 NETOPS-CEE NETOPS B.V.

Hosting RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12459: 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
AS9002RETN LimitedUnclassifiedIPv462
AS174Cogent Communications, LLCTransitIPv452
AS13004Serbian Open Exchange DOOUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207604United Internet Ltd.UnclassifiedIPv4 IPv6382
AS136787PacketHub S.A.VPNIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS201789NETOPS B.V.UnclassifiedIPv4 IPv61,005
AS9002RETN LimitedUnclassifiedIPv4 IPv6815
AS174Cogent Communications, LLCTransitIPv4 IPv6403
AS207604United Internet Ltd.UnclassifiedIPv4 IPv6382
AS13004Serbian Open Exchange DOOUnclassifiedIPv4 IPv6343
AS136787PacketHub S.A.VPNIPv458

Provenance

Where this comes from

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