asn.dev

Observed topology

AS139993 IDNIC-SEKOLAHAN-AS-ID PT. FORIT ASTA SOLUSINDO

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS139993: 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
AS58389PT Sumber Data IndonesiaUnclassifiedIPv4187
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv463
AS24482SG.GSHostingIPv44
AS150506PT Pusat Fiber IndonesiaUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS4855Pacific Link IndonesiaUnclassifiedIPv4195
AS154440Dinas Komunikasi & Informatika Kota CimahiUnclassifiedIPv465
AS138102PT Baraya Telematika NusantaraUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS58389PT Sumber Data IndonesiaUnclassifiedIPv4260
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv4242
AS4855Pacific Link IndonesiaUnclassifiedIPv4195
AS154440Dinas Komunikasi & Informatika Kota CimahiUnclassifiedIPv465
AS150506PT Pusat Fiber IndonesiaUnclassifiedIPv417
AS138102PT Baraya Telematika NusantaraUnclassifiedIPv414
AS24482SG.GSHostingIPv48

Provenance

Where this comes from

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