Observed topology

AS18268 JANIS - Naganoken Kyodou Densan Co.Ltd.

Unclassified APNIC Cable/DSL/ISP

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 5

Upstream graph Who carries AS18268, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS18268 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18268: 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.

AS	Network	Type	Families	Paths seen
AS2519	ARTERIA Networks Corporation	Unclassified	IPv4 IPv6	187
AS17676	SoftBank Corp.	Mobile	IPv4 IPv6	94
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	88
AS9002	RETN Limited	Unclassified	IPv4	12
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4 IPv6	8
AS24482	SG.GS	Hosting	IPv4 IPv6	8
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS17518	Shiojiri City	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS2519	ARTERIA Networks Corporation	Unclassified	IPv4 IPv6	217
AS17676	SoftBank Corp.	Mobile	IPv4 IPv6	112
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	97
AS17518	Shiojiri City	Unclassified	IPv4	59
AS9002	RETN Limited	Unclassified	IPv4	12
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4 IPv6	9
AS24482	SG.GS	Hosting	IPv4 IPv6	9
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	4

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.