asn.dev

Observed topology

AS16003 FORNEX-NL-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16003: 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
AS6204INTERKVM HOST SRLUnclassifiedIPv41,092
AS8455atom86 BVHostingIPv4 IPv6479
AS6939Hurricane Electric LLCTransitIPv4324
AS58329servinga GmbHHostingIPv4 IPv6234
AS24482SG.GSHostingIPv437
AS37721Virtual Technologies & SolutionsResidentialIPv437
AS49673Truenetwork LLCUnclassifiedIPv437
AS56655Gigahost ASUnclassifiedIPv437
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv437

Transit

Downstream networks

inferred

Networks for which AS16003 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS6204INTERKVM HOST SRLUnclassifiedIPv41,092
AS8455atom86 BVHostingIPv4 IPv6479
AS6939Hurricane Electric LLCTransitIPv4324
AS58329servinga GmbHHostingIPv4 IPv6234
AS24482SG.GSHostingIPv437
AS37721Virtual Technologies & SolutionsResidentialIPv437
AS49673Truenetwork LLCUnclassifiedIPv437
AS56655Gigahost ASUnclassifiedIPv437
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv437

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.