asn.dev

Observed topology

AS45302 DESNET-AS-ID PT DES Teknologi Informasi

Upstreams 5 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 5

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45302: 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
AS45305Lintas Data Prima, PTResidentialIPv4 IPv6588
AS4800PT Aplikanusa LintasartaHostingIPv4532
AS7632Linknet-Exchange ASNUnclassifiedIPv4 IPv6287
AS24482SG.GSHostingIPv415
AS7717OpenIXP ASNUnclassifiedIPv61

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

ASNetworkTypeFamiliesPaths seen
AS58492Universitas Islam Sultan AgungUnclassifiedIPv4268
AS149699RSUD Dr MoewardiUnclassifiedIPv4 IPv6121
AS147119Politeknik Pariwisata MakassarUnclassifiedIPv462
AS140431Dinas Komunikasi dan Informatika Kabupaten WonogiriUnclassifiedIPv4 IPv661
AS46049Universitas DiponegoroEducationIPv459

Adjacency

Adjacent networks

16 shown

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

ASNetworkTypeFamiliesPaths seen
AS45305Lintas Data Prima, PTResidentialIPv4 IPv6846
AS4800PT Aplikanusa LintasartaHostingIPv4820
AS7632Linknet-Exchange ASNUnclassifiedIPv4 IPv6315
AS58492Universitas Islam Sultan AgungUnclassifiedIPv4268
AS149699RSUD Dr MoewardiUnclassifiedIPv4 IPv6121
AS147119Politeknik Pariwisata MakassarUnclassifiedIPv462
AS140431Dinas Komunikasi dan Informatika Kabupaten WonogiriUnclassifiedIPv4 IPv661
AS46049Universitas DiponegoroEducationIPv459
AS24482SG.GSHostingIPv415
AS137367PT iForte Solusi InfotekResidentialIPv44
AS7717OpenIXP ASNUnclassifiedIPv4 IPv62

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 AS45302, 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 2 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
OpenIXP Internet exchange PointJakarta, Indonesia218.100.27.422,071
Indonesian Internet Exchange (IIX-Jakarta)Jakarta, Indonesia123.108.8.242923

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-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 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.