asn.dev

Observed topology

AS63774 KAMOIKE-NET Kamoike.net LLP

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS63774: 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
AS9607BroadBand Tower, Inc.HostingIPv4 IPv6293
AS55900GLBB Japan KKUnclassifiedIPv4 IPv6191
AS6939Hurricane Electric LLCTransitIPv472
AS59103SoftEther CorporationUnclassifiedIPv428
AS24482SG.GSHostingIPv4 IPv612
AS59105Home NOC Operators GroupUnclassifiedIPv4 IPv611
AS9002RETN LimitedUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS151371PAINA Information DevelopmentUnclassifiedIPv4 IPv611

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9607BroadBand Tower, Inc.HostingIPv4 IPv6293
AS55900GLBB Japan KKUnclassifiedIPv4 IPv6191
AS6939Hurricane Electric LLCTransitIPv481
AS59103SoftEther CorporationUnclassifiedIPv428
AS24482SG.GSHostingIPv4 IPv614
AS59105Home NOC Operators GroupUnclassifiedIPv4 IPv611
AS151371PAINA Information DevelopmentUnclassifiedIPv4 IPv611
AS9002RETN LimitedUnclassifiedIPv41

Provenance

Where this comes from

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