asn.dev

Observed topology

AS203868 RAPDODGENET-ID Rifqi Arief Pamungkas

Unclassified RIPE

Upstreams 6 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 2
Adjacent (IPv6) 6
Upstream graph Who carries AS203868, and who carries them, drawn as a map up to the transit-free core. 5 exchanges Where AS203868 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203868: 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
AS205941Lungu Stefan GabrielUnclassifiedIPv679
AS41051Openfactory GmbHUnclassifiedIPv664
AS210152Jon Vanvik trading as Vanvik InternetUnclassifiedIPv636
AS34927iFog GmbHHostingIPv635
AS24482SG.GSHostingIPv63
AS152368PT Perwira Pedjoeang NusantaraUnclassifiedIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS151992PT Jet Cyber Network NusantaraResidentialIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS205941Lungu Stefan GabrielUnclassifiedIPv679
AS41051Openfactory GmbHUnclassifiedIPv664
AS210152Jon Vanvik trading as Vanvik InternetUnclassifiedIPv636
AS34927iFog GmbHHostingIPv635
AS152368PT Perwira Pedjoeang NusantaraUnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv63
AS151992PT Jet Cyber Network NusantaraResidentialIPv42

Provenance

Where this comes from

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