Observed topology

AS25124 DATAK Datak Company LLC

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25124: 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
AS57218	"Rightel Communication Service Company PJS"	Unclassified	IPv4 IPv6	932

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS42907	Research Institute Of Petroleum Industry	Unclassified	IPv4	420
AS209596	Kish Cell Pars Co. (PJS)	Unclassified	IPv4	240
AS204203	Atrin Information & Communications Technology Company PJS	Unclassified	IPv4	116
AS49433	Bank Refah Kargaran	Unclassified	IPv4	60
AS57497	Faraso Samaneh Pasargad Ltd.	Unclassified	IPv4	59
AS205490	Railways of Islamic Republic of IRAN	Unclassified	IPv4	19

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS57218	"Rightel Communication Service Company PJS"	Unclassified	IPv4 IPv6	1,905
AS42907	Research Institute Of Petroleum Industry	Unclassified	IPv4	420
AS209596	Kish Cell Pars Co. (PJS)	Unclassified	IPv4	240
AS204203	Atrin Information & Communications Technology Company PJS	Unclassified	IPv4	175
AS49433	Bank Refah Kargaran	Unclassified	IPv4	60
AS57497	Faraso Samaneh Pasargad Ltd.	Unclassified	IPv4	59
AS205490	Railways of Islamic Republic of IRAN	Unclassified	IPv4	19

Provenance

Where this comes from

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