asn.dev

Observed topology

AS133371 IDNIC-SOKKALINK-AS-ID - PT SOKKA TAMA FIBER

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS133371: 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
AS3356Level 3 Parent, LLCTransitIPv430
AS174Cogent Communications, LLCTransitIPv421
AS3491PCCW Global (HK) Ltd.TransitIPv46
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS140454PT Pop Net IndonesiaResidentialIPv4236
AS131717PT Citra Jelajah InformatikaResidentialIPv4116
AS153858PT SOKKA TAMA FIBERUnclassifiedIPv458
AS138389PT Borneo Gerbang SolusindoUnclassifiedIPv457
AS38783PT. Simaya Jejaring MandiriResidentialIPv436
AS141903PT Natha Buana IndonesiaResidentialIPv420

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4283
AS140454PT Pop Net IndonesiaResidentialIPv4236
AS3356Level 3 Parent, LLCTransitIPv4199
AS131717PT Citra Jelajah InformatikaResidentialIPv4116
AS3491PCCW Global (HK) Ltd.TransitIPv497
AS153858PT SOKKA TAMA FIBERUnclassifiedIPv458
AS138389PT Borneo Gerbang SolusindoUnclassifiedIPv457
AS38783PT. Simaya Jejaring MandiriResidentialIPv436
AS141903PT Natha Buana IndonesiaResidentialIPv420
AS24482SG.GSHostingIPv42

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.