Network topology

Relationships come from RIS AS_PATH observations; direction represents path position, not a commercial contract or traffic direction.

AS48102

Currently announcedSnapshot awaiting refresh

PETERSERVICE JSC Neksain · PETERSERVICE

Last observed10/4/2026, 07:37:52Open ASN profile →

AS48102 relationship topology

Showing 5 / 5

AS48102PETERSERVICE JSC Neksain

UpstreamDownstreamUncertain relationshipNodes are ordered by observed weight

SELECTED NODEAS57304RETNRU-AS JSC "RetnNet"

Relationship: Upstream
Observed weight: 106
ASN registration country: Russia
Latest RIS data: 10/11/2026, 00:00:00

Open AS57304 profile →

All adjacent autonomous systems

The table preserves every relationship in the selected filter; graph limits and pagination never remove data.

5 relationships

ASN	Organization	Relationship	ASN registration country	RIS observation start	Latest RIS data	IPv4
AS57304Observed weight 106	RETNRU-AS JSC "RetnNet"	Upstream	Russia	8/23/2019, 00:00:00	10/11/2026, 00:00:00	136
AS9002Observed weight 86	RETN-AS RETN Limited	Upstream	United Kingdom	8/23/2019, 00:00:00	10/11/2026, 00:00:00	115
AS51178Observed weight 60	AVANTEL-SPB-AS JSC "ER-Telecom Holding"	Upstream	Russia	8/23/2019, 00:00:00	10/11/2026, 00:00:00	72
AS35000Observed weight 19	SEVEREN-TELECOM_TRANSIT JSC "Severen-Telecom"	Upstream	Russia	8/23/2019, 00:00:00	10/11/2026, 00:00:00	21
AS20632Observed weight 5	PETERSTAR-AS PJSC MegaFon	Upstream	Russia	8/23/2019, 00:00:00	10/11/2026, 00:00:00	7

CHA.LA ASN relationship snapshotRelationships are normalized by CHA.LA from collected routing observations and registration context.CHA.LA routing observations · registration context