asn.dev

Observed topology

AS64098 FIELD-AS-AP Field Solutions Group Pty Ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS64098: 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
AS134090LeaptelResidentialIPv4 IPv6672
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv6506
AS6939Hurricane Electric LLCTransitIPv4141
AS24482SG.GSHostingIPv4 IPv623
AS64073Vetta GroupUnclassifiedIPv4 IPv623
AS4608Asia Pacific Network Information CentreUnclassifiedIPv419

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133736TASMANETUnclassifiedIPv41,054
AS45158TASMANETUnclassifiedIPv4 IPv6694
AS55581NEXT TELECOMResidentialIPv4628
AS136799onPlatinum AUUnclassifiedIPv4124

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS134090LeaptelResidentialIPv4 IPv62,568
AS45158TASMANETUnclassifiedIPv4 IPv61,705
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv61,601
AS133736TASMANETUnclassifiedIPv41,054
AS55581NEXT TELECOMResidentialIPv4660
AS6939Hurricane Electric LLCTransitIPv4516
AS136799onPlatinum AUUnclassifiedIPv4124
AS24482SG.GSHostingIPv4 IPv683
AS64073Vetta GroupUnclassifiedIPv4 IPv683
AS4608Asia Pacific Network Information CentreUnclassifiedIPv476

Provenance

Where this comes from

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