Observed topology

AS149373 IDNIC-RBA-SOLUTION-AS-ID - PT Rintis Berkah Akamila

Unclassified APNIC

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS149373: 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
AS174	Cogent Communications, LLC	Transit	IPv4	177

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS399546	ZRIXI	Unclassified	IPv4	236
AS149689	PT Akm Link Net	Residential	IPv4	118
AS10847	Podernet, S.A. de C.V.	Unclassified	IPv4	59
AS29160	Arabcircle Internet Services for Saudi Arabia	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	649
AS399546	ZRIXI	Unclassified	IPv4	236
AS149689	PT Akm Link Net	Residential	IPv4	118
AS10847	Podernet, S.A. de C.V.	Unclassified	IPv4	59
AS29160	Arabcircle Internet Services for Saudi Arabia	Unclassified	IPv4	59

Provenance

Where this comes from

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