asn.dev

Observed topology

AS151552 IDNIC-THREEGOTECHNOLOGY-AS-ID - PT Threego Technology Indonesia

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS151552: 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
AS1514043GO TECHNOLOGY PTE. LTD.UnclassifiedIPv4 IPv660
AS151326DCConnect Communication Pte. Ltd.ResidentialIPv625
AS4229Zenlayer IncHostingIPv46
AS138077PT Abhinawa Sumberdaya AsiaHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS396986Bytedance Inc.HostingIPv4 IPv6296
AS45323PT INTERLINK TECHNOLOGYUnclassifiedIPv4118
AS199524G-Core Labs S.A.HostingIPv4 IPv690
AS54994Meteverse Limited.UnclassifiedIPv444

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1514043GO TECHNOLOGY PTE. LTD.UnclassifiedIPv4 IPv6444
AS396986Bytedance Inc.HostingIPv4 IPv6300
AS45323PT INTERLINK TECHNOLOGYUnclassifiedIPv4118
AS151326DCConnect Communication Pte. Ltd.ResidentialIPv4 IPv6118
AS199524G-Core Labs S.A.HostingIPv4 IPv690
AS17497Liasail Global Hongkong LimitedUnclassifiedIPv468
AS54994Meteverse Limited.UnclassifiedIPv444
AS4229Zenlayer IncHostingIPv4 IPv613
AS138077PT Abhinawa Sumberdaya AsiaHostingIPv42

Provenance

Where this comes from

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