asn.dev

Observed topology

AS24295 AS-PNAPOSK PacketFabric Japan Co., Ltd.

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24295: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6231
AS2516KDDI CORPORATIONMobileIPv4 IPv6229
AS17676SoftBank Corp.MobileIPv4 IPv657

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS134835Starry Network LimitedUnclassifiedIPv4 IPv6497
AS24291MITSUI & CO., LTD.UnclassifiedIPv465
AS59207SYD OfficeUnclassifiedIPv418

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS134835Starry Network LimitedUnclassifiedIPv4 IPv6528
AS3356Level 3 Parent, LLCTransitIPv4 IPv6509
AS2516KDDI CORPORATIONMobileIPv4 IPv6504
AS17676SoftBank Corp.MobileIPv4 IPv6115
AS24291MITSUI & CO., LTD.UnclassifiedIPv465
AS59207SYD OfficeUnclassifiedIPv418

Provenance

Where this comes from

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