asn.dev

Observed topology

AS136841 MTMBALI-AS-ID PT MITRA TELEMEDIA MANUNGGAL

Upstreams 10 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 12
Adjacent (IPv6) 10

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS136841: 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
AS4800PT Aplikanusa LintasartaHostingIPv4 IPv6850
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv6548
AS7713PT Telekomunikasi IndonesiaResidentialIPv4 IPv6120
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv4 IPv681
AS7632Linknet-Exchange ASNUnclassifiedIPv4 IPv649
AS24482SG.GSHostingIPv4 IPv628
AS137366PT iForte Solusi Infotek - NAPUnclassifiedIPv4 IPv627
AS17451BIZNET NETWORKSResidentialIPv4 IPv616
AS137367PT iForte Solusi InfotekResidentialIPv44
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv41

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.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS38526Badan Teknologi Informasi Dan Telematika Sekretariat Daerah Kota YogyakartaUnclassifiedIPv4 IPv61,181
AS59151Diskominfo DIYUnclassifiedIPv4 IPv6240

Adjacency

Adjacent networks

22 shown

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

ASNetworkTypeFamiliesPaths seen
AS4800PT Aplikanusa LintasartaHostingIPv4 IPv61,299
AS38526Badan Teknologi Informasi Dan Telematika Sekretariat Daerah Kota YogyakartaUnclassifiedIPv4 IPv61,181
AS137366PT iForte Solusi Infotek - NAPUnclassifiedIPv4 IPv6999
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv6548
AS59151Diskominfo DIYUnclassifiedIPv4 IPv6240
AS7713PT Telekomunikasi IndonesiaResidentialIPv4 IPv6120
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv4 IPv681
AS7632Linknet-Exchange ASNUnclassifiedIPv4 IPv649
AS24482SG.GSHostingIPv4 IPv628
AS17451BIZNET NETWORKSResidentialIPv4 IPv616
AS137367PT iForte Solusi InfotekResidentialIPv44
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv41

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS136841, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 6 exchanges across 2 countries and 1 region.

ExchangeLocationTheir addressMember ports
OpenIXP Internet exchange PointJakarta, Indonesia218.100.36.1552,071
Indonesian Internet Exchange (IIX-Jakarta)Jakarta, Indonesia123.108.9.181923
Equinix Internet Exchange SingaporeSingapore, Singapore27.111.231.21490
BroadBand Internet eXchange SingaporeSingapore, Singapore103.231.153.24151
DE-CIX ASEAN (Singapore, Malaysia, Brunei)Singapore, Singapore103.162.254.143138
Digital Edge EPIX JakartaJakarta, Indonesia202.159.50.6883

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.