asn.dev

Observed topology

AS136880 SMSNET-AS-ID - PT. Sumatra Multimedia Solusi

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS136880: 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
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv4 IPv6271
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv416
AS24198PT. Datakom Padma Jaya (DatakomNAP)UnclassifiedIPv412
AS24482SG.GSHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS138142Institut Informatika & Bisnis DarmajayaUnclassifiedIPv468

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv4 IPv6334
AS138142Institut Informatika & Bisnis DarmajayaUnclassifiedIPv468
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv419
AS24198PT. Datakom Padma Jaya (DatakomNAP)UnclassifiedIPv412
AS24482SG.GSHostingIPv45
AS131111PT Mora Telematika IndonesiaUnclassifiedIPv41

Provenance

Where this comes from

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