asn.dev

Observed topology

AS38230 NAVICENET-AS-AP - Navice Consulting

Hosting ARIN Network Services

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS38230: 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
AS34927iFog GmbHHostingIPv4 IPv6189
AS1299Arelion Sweden ABTransitIPv4 IPv610
AS6939Hurricane Electric LLCTransitIPv47
AS29632Netassist International EOODUnclassifiedIPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS204092Association GRIFONUnclassifiedIPv4 IPv64
AS205794JINZE YANGUnclassifiedIPv63

All 16 upstreams →

Transit

Downstream networks

inferred

Networks for which AS38230 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 16

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4 IPv6189
AS1299Arelion Sweden ABTransitIPv4 IPv610
AS6939Hurricane Electric LLCTransitIPv47
AS29632Netassist International EOODUnclassifiedIPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS204092Association GRIFONUnclassifiedIPv4 IPv64
AS205794JINZE YANGUnclassifiedIPv63

All 16 adjacent →

Provenance

Where this comes from

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