asn.dev

Observed topology

AS2515 JPNIC Japan Network Information Center

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2515: 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
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6152
AS2518BIGLOBE Inc.ResidentialIPv4 IPv655
AS6939Hurricane Electric LLCTransitIPv433
AS2500WIDE ProjectUnclassifiedIPv4 IPv625
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS20485Joint Stock Company TransTeleComUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS131971JPNIC-4Byte-ASBLOCK-APUnclassifiedIPv4 IPv6438

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2518BIGLOBE Inc.ResidentialIPv4 IPv6473
AS131971JPNIC-4Byte-ASBLOCK-APUnclassifiedIPv4 IPv6438
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6172
AS6939Hurricane Electric LLCTransitIPv433
AS2500WIDE ProjectUnclassifiedIPv4 IPv625
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS20485Joint Stock Company TransTeleComUnclassifiedIPv44

Provenance

Where this comes from

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