asn.dev

Observed topology

AS55670 UNIVERSALNET-AS-ID - PT. Universal Broadband

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55670: 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
AS4787PT Cyberindo AditamaResidentialIPv4316
AS134654PT Datautama Dinamika - NAPUnclassifiedIPv4153
AS7713PT Telekomunikasi IndonesiaResidentialIPv427
AS58495PT Parsaoran Global DatatransUnclassifiedIPv416
AS24482SG.GSHostingIPv4 IPv615
AS35280F5 Networks SARLHostingIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS155058PT Perdana Global InternetUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4787PT Cyberindo AditamaResidentialIPv4316
AS134654PT Datautama Dinamika - NAPUnclassifiedIPv4213
AS155058PT Perdana Global InternetUnclassifiedIPv460
AS7713PT Telekomunikasi IndonesiaResidentialIPv427
AS58495PT Parsaoran Global DatatransUnclassifiedIPv416
AS24482SG.GSHostingIPv4 IPv615
AS35280F5 Networks SARLHostingIPv4 IPv67

Provenance

Where this comes from

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