asn.dev

Observed topology

AS7356 SIKLA-AS - Sikla Tech Limited

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7356: 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
AS20473The Constant Company, LLCHostingIPv4 IPv6148

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS1405Caelus Technology LLCUnclassifiedIPv4 IPv6795
AS139358Kansuiun Co., LtdUnclassifiedIPv4 IPv6355
AS26879Aurelia Telecom Systems LLCUnclassifiedIPv4 IPv6273
AS141001Flinty NetworkUnclassifiedIPv4236
AS16968Aurelia Telecom Systems LLCUnclassifiedIPv4177

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS1405Caelus Technology LLCUnclassifiedIPv4 IPv6795
AS3356Level 3 Parent, LLCTransitIPv4 IPv6558
AS137409GSL Networks Pty LTDUnclassifiedIPv4503
AS9886CTCSCI TECH LIMITEDHostingIPv4 IPv6404
AS139358Kansuiun Co., LtdUnclassifiedIPv4 IPv6355
AS26879Aurelia Telecom Systems LLCUnclassifiedIPv4 IPv6273
AS141001Flinty NetworkUnclassifiedIPv4236
AS134823Sky Digital Co., Ltd.ResidentialIPv4 IPv6210
AS16968Aurelia Telecom Systems LLCUnclassifiedIPv4177
AS20473The Constant Company, LLCHostingIPv4 IPv6148

All 13 adjacent →

Provenance

Where this comes from

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