Observed topology

AS136838 BITEK-NAP-AS-ID PT BIT TEKNOLOGI NUSANTARA

Unclassified RIPE NSP

Upstreams 2 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS136838: 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
AS137367	PT iForte Solusi Infotek	Residential	IPv4	68
AS174	Cogent Communications, LLC	Transit	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS133797	PT Rekajasa Akses	Unclassified	IPv4	157
AS38769	PT. Bit Technology Nusantara	Unclassified	IPv4	73

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS137367	PT iForte Solusi Infotek	Residential	IPv4	189
AS133797	PT Rekajasa Akses	Unclassified	IPv4	157
AS6939	Hurricane Electric LLC	Transit	IPv4	78
AS38769	PT. Bit Technology Nusantara	Unclassified	IPv4	73
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	10
AS38001	NewMedia Express Pte Ltd	Hosting	IPv4	10
AS132132	MyRepublic Ltd.	Residential	IPv4	10
AS174	Cogent Communications, LLC	Transit	IPv4	3
AS24482	SG.GS	Hosting	IPv4	1

Provenance

Where this comes from

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