asn.dev

Observed topology

AS38719 DREAMSCAPE-AS-AP Dreamscape Networks Limited

Hosting APNIC

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS38719: 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
AS55803Hostopia Australia Web Pty LtdUnclassifiedIPv4 IPv62,378
AS4657StarHub LtdResidentialIPv4 IPv61,004
AS6939Hurricane Electric LLCTransitIPv4 IPv6448
AS36351IBM CloudHostingIPv4118
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv687
AS24482SG.GSHostingIPv4 IPv656
AS64073Vetta GroupUnclassifiedIPv4 IPv653
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv611
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65

All 23 upstreams →

Transit

Downstream networks

inferred

Networks for which AS38719 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 AS38719 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS55803Hostopia Australia Web Pty LtdUnclassifiedIPv4 IPv62,378
AS4657StarHub LtdResidentialIPv4 IPv61,004
AS6939Hurricane Electric LLCTransitIPv4 IPv6448
AS36351IBM CloudHostingIPv4118
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv687
AS24482SG.GSHostingIPv4 IPv656
AS64073Vetta GroupUnclassifiedIPv4 IPv653
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv611
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65

All 23 adjacent →

Provenance

Where this comes from

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