asn.dev

Observed topology

AS29263 HAAGNET-AS Gemeente Den Haag

Unclassified RIPE

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS29263: 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
AS32787Akamai Technologies, Inc.HostingIPv4 IPv6380
AS33915Vodafone Libertel B.V.ResidentialIPv4 IPv661
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv63
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS34019Hivane AssociationUnclassifiedIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62
AS48185team.blue NVUnclassifiedIPv4 IPv62
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv62
AS293ESnetUnclassifiedIPv41

Transit

Downstream networks

inferred

Networks for which AS29263 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 23

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

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv4 IPv6380
AS33915Vodafone Libertel B.V.ResidentialIPv4 IPv661
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv63
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS34019Hivane AssociationUnclassifiedIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62
AS48185team.blue NVUnclassifiedIPv4 IPv62
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv62
AS293ESnetUnclassifiedIPv41

Provenance

Where this comes from

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