asn.dev

Observed topology

AS151006 IDNIC-NIMNET-AS-ID PT Nesta Indo Media

Upstreams 5 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 4

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS151006: 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
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6180
AS7713PT Telekomunikasi IndonesiaResidentialIPv459
AS136106PT. Mega Akses PersadaResidentialIPv4 IPv651
AS24482SG.GSHostingIPv4 IPv66
AS35280F5 Networks SARLHostingIPv41

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 AS151006 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS141664PT Jaringan Inti ExadataResidentialIPv4 IPv6278
AS135471PEMERINTAH KABUPATEN BOYOLALIUnclassifiedIPv4132
AS153769RSUD Pandan Arang BoyolaliUnclassifiedIPv466

Adjacency

Adjacent networks

14 shown

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

ASNetworkTypeFamiliesPaths seen
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6566
AS141664PT Jaringan Inti ExadataResidentialIPv4 IPv6278
AS135471PEMERINTAH KABUPATEN BOYOLALIUnclassifiedIPv4132
AS136106PT. Mega Akses PersadaResidentialIPv4 IPv6128
AS153769RSUD Pandan Arang BoyolaliUnclassifiedIPv466
AS7713PT Telekomunikasi IndonesiaResidentialIPv459
AS24482SG.GSHostingIPv4 IPv69
AS4787PT Cyberindo AditamaResidentialIPv46
AS131767PT. SOLO JALA BUANAUnclassifiedIPv44
AS35280F5 Networks SARLHostingIPv41

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 AS151006, 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 5 exchanges across 2 countries and 1 region.

ExchangeLocationTheir addressMember ports
OpenIXP Internet exchange PointJakarta, Indonesia43.252.146.2452,071
Indonesian Internet Exchange (IIX-Jakarta)Jakarta, Indonesia123.108.10.198923
Alien Internet ExchangeDepok, Indonesia43.254.82.199382
cloudXchange JakartaJakarta, Indonesia103.225.173.72207
DE-CIX ASEAN (Singapore, Malaysia, Brunei)Singapore, Singapore103.162.254.179138

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.