asn.dev

Observed topology

AS45040 EXTRAIP-AS

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45040: 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
AS50673Serverius Holding B.V.UnclassifiedIPv4231
AS6939Hurricane Electric LLCTransitIPv4 IPv673
AS24482SG.GSHostingIPv4 IPv66
AS58057Securebit AGUnclassifiedIPv4 IPv66
AS34019Hivane AssociationUnclassifiedIPv45
AS34927iFog GmbHHostingIPv45
AS61044ExtraIP B.V.HostingIPv45
AS202365Omer GOLGELIUnclassifiedIPv45
AS56662Marcin GondekUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61044ExtraIP B.V.HostingIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50673Serverius Holding B.V.UnclassifiedIPv4231
AS6939Hurricane Electric LLCTransitIPv4 IPv674
AS24482SG.GSHostingIPv4 IPv66
AS58057Securebit AGUnclassifiedIPv4 IPv66
AS61044ExtraIP B.V.HostingIPv46
AS34019Hivane AssociationUnclassifiedIPv45
AS34927iFog GmbHHostingIPv45
AS202365Omer GOLGELIUnclassifiedIPv45
AS56662Marcin GondekUnclassifiedIPv61

Provenance

Where this comes from

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