Observed topology

AS58553 IDNIC-3DTECH-ID - PT 3D Tech

Unclassified APNIC Cable/DSL/ISP

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

Upstream graph Who carries AS58553, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS58553 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58553: 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
AS153068	Nusantara Global Exchange	Hosting	IPv4	184
AS7713	PT Telekomunikasi Indonesia	Residential	IPv4	60

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS141669	PT Citra Victoria Raya	Unclassified	IPv4	120
AS139382	PT Multi Teknologi Telematika	Residential	IPv4	62
AS141893	PT Kawanua Internet Indonesia	Unclassified	IPv4	61
AS133360	PT Awinet Global Mandiri	Residential	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS7713	PT Telekomunikasi Indonesia	Residential	IPv4	300
AS153068	Nusantara Global Exchange	Hosting	IPv4	247
AS141669	PT Citra Victoria Raya	Unclassified	IPv4	120
AS139382	PT Multi Teknologi Telematika	Residential	IPv4	63
AS141893	PT Kawanua Internet Indonesia	Unclassified	IPv4	61
AS133360	PT Awinet Global Mandiri	Residential	IPv4	59

Provenance

Where this comes from

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