asn.dev

Observed topology

AS152900 ONIDEL-AS-AP - Onidel Pty Ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152900: 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
AS136557Host Universal Pty LtdUnclassifiedIPv4 IPv6644
AS24482SG.GSHostingIPv4 IPv6500
AS63018Dedicated.comHostingIPv4 IPv6214
AS212477RoyaleHosting BVHostingIPv4 IPv6152

Transit

Downstream networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS140999JetEmail Pty LtdUnclassifiedIPv4 IPv6225
AS205563Marc GomezUnclassifiedIPv6142
AS135134Soon Keat NeoUnclassifiedIPv4 IPv6100
AS212085Alexander BruegmannUnclassifiedIPv670
AS40663IncogNet LLCVPNIPv464
AS398810MXroute LLCUnclassifiedIPv463
AS197569BASED ON WHAT LLCUnclassifiedIPv4 IPv650
AS214999Christian WolfseherUnclassifiedIPv638
AS199459Alexandro SetiawanUnclassifiedIPv637
AS206042Suhail HarisUnclassifiedIPv636

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS136557Host Universal Pty LtdUnclassifiedIPv4 IPv61,028
AS24482SG.GSHostingIPv4 IPv6694
AS63018Dedicated.comHostingIPv4 IPv6490
AS140999JetEmail Pty LtdUnclassifiedIPv4 IPv6225
AS212477RoyaleHosting BVHostingIPv4 IPv6169
AS205563Marc GomezUnclassifiedIPv6142
AS135134Soon Keat NeoUnclassifiedIPv4 IPv6100
AS212085Alexander BruegmannUnclassifiedIPv670
AS40663IncogNet LLCVPNIPv464
AS398810MXroute LLCUnclassifiedIPv463

Provenance

Where this comes from

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