Observed topology
AS55653 SKYLINE-AS-ID Skyline Semesta, PT
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS55653: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS58389 | PT Sumber Data Indonesia | Unclassified | IPv4 IPv6 | 1,025 |
| AS10217 | PT. NTT Indonesia | Unclassified | IPv4 IPv6 | 330 |
| AS4800 | PT Aplikanusa Lintasarta | Hosting | IPv4 | 249 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 29 |
| AS17451 | BIZNET NETWORKS | Residential | IPv4 | 16 |
| AS7717 | OpenIXP ASN | Unclassified | IPv4 | 4 |
| AS7597 | Indonesia Internet Exchange | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS55653 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS55653 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS58389 | PT Sumber Data Indonesia | Unclassified | IPv4 IPv6 | 1,364 |
| AS10217 | PT. NTT Indonesia | Unclassified | IPv4 IPv6 | 386 |
| AS4800 | PT Aplikanusa Lintasarta | Hosting | IPv4 | 249 |
| AS149893 | PT Sima Bahtera Utama | Unclassified | IPv4 | 192 |
| AS133803 | PT Semesta Teknologi Informatika | Hosting | IPv4 IPv6 | 162 |
| AS137325 | PT Sanbe Farma | Unclassified | IPv4 | 43 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 31 |
| AS17451 | BIZNET NETWORKS | Residential | IPv4 | 16 |
| AS7717 | OpenIXP ASN | Unclassified | IPv4 | 4 |
| AS7597 | Indonesia Internet Exchange | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.