Skip to content
KynexBGP
OkrugTeleCom logo

AS56874

OkrugTeleCom

Russia (RU)

AS56874 peers and adjacencies

Public data cannot confirm who AS56874 has a BGP session with. This page shows three different kinds of evidence, kept separate on purpose.

Upstreams (inferred)

ASNameRelationshipEvidenceLast observed
AS3216SOVAM-AS PJSC "Vimpelcom"Upstream (inferred)Observed paths, Path inference · 202 paths
AS8732COMCOR-AS JSC ComcorUpstream (inferred)Observed paths, Path inference · 148 paths
AS137409GSLNETWORKS-AS-AP - GSL Networks Pty LTDUpstream (inferred)Observed paths, Path inference · 14 paths
AS24482SGGS-AS-AP - SG.GSUpstream (inferred)Observed paths, Path inference · 4 paths
AS37721Virtual Technologies & Solutions - Virtual Technologies & SolutionsUpstream (inferred)Observed paths, Path inference · 2 paths
AS61049EXASCALE Exascale LtdUpstream (inferred)Observed paths, Path inference · 2 paths
AS9198KAZTELECOM-AS JSC KazakhtelecomUpstream (inferred)Path inference—
AS21030CDNNOW-AS Cluster LLCUpstream (inferred)Path inference—
AS25091IP-Max IP-Max SAUpstream (inferred)Path inference—
AS49434FBWNETWORKS FBW NETWORKS SASUpstream (inferred)Path inference—

Downstreams (inferred)

No downstream ASNs found for AS56874 in current data sources.

Combined from the evidence below: an ASN seen between AS56874 and the collectors (or inferred to be on the collector side) is listed as upstream; one seen behind it (“right”) as downstream.

1. Observed path adjacencies

ASNs that appear immediately next to AS56874 in AS paths seen by route collectors (prepends collapsed). These are path adjacencies, not confirmed BGP sessions, and the position says nothing certain about the commercial relationship.

ASNPosition in pathPathsCollectorsExample pathLast observed
AS3216
SOVAM-AS PJSC "Vimpelcom"
Before (towards collector)2027
listAmsterdam, Eugene, OR, Johannesburg, London, Singapore, Sydney, São Paulo
2119 3216 56874
AS8732
COMCOR-AS JSC Comcor
Before (towards collector)1486
listAmsterdam, Eugene, OR, Johannesburg, London, Singapore, São Paulo
398465 8732 56874
AS137409
GSLNETWORKS-AS-AP - GSL Networks Pty LTD
Before (towards collector)143
listEugene, OR, London, Sydney
8529 137409 56874
AS24482
SGGS-AS-AP - SG.GS
Before (towards collector)42
listEugene, OR, Singapore
24482 56874
AS37721
Virtual Technologies & Solutions - Virtual Technologies & Solutions
Before (towards collector)21
listEugene, OR
37721 56874
AS61049
EXASCALE Exascale Ltd
Before (towards collector)21
listAmsterdam
61049 56874

2. Direct sessions with route collectors

BGP sessions between AS56874 itself and a route collector (the AS feeds its routes to the collector).

AS56874 has no direct session with a route collector in the data.

3. Inferred neighbours

Neighbours inferred from AS paths seen by route collectors. “Left” neighbours appear between AS56874 and the collector, “right” neighbours on the origin side. These are inferences, not confirmed relationships.

ASNSideInferencePowerIPv4 peersIPv6 peers
AS3216
SOVAM-AS PJSC "Vimpelcom"
leftinferred upstream1513690
AS8732
COMCOR-AS JSC Comcor
leftinferred upstream1092630
AS25091
IP-Max IP-Max SA
leftinferred upstream5180
AS49434
FBWNETWORKS FBW NETWORKS SAS
leftinferred upstream240
AS61049
EXASCALE Exascale Ltd
leftinferred upstream240
AS9198
KAZTELECOM-AS JSC Kazakhtelecom
leftinferred upstream120
AS21030
CDNNOW-AS Cluster LLC
leftinferred upstream120
AS24482
SGGS-AS-AP - SG.GS
uncertainuncertain1180
AS28910
INTAL-ASN "Uzbektelekom" Joint Stock Company
uncertainuncertain120
AS34927
iFog-GmbH iFog GmbH
uncertainuncertain120
AS37721
Virtual Technologies & Solutions - Virtual Technologies & Solutions
uncertainuncertain120
AS137409
GSLNETWORKS-AS-AP - GSL Networks Pty LTD
leftinferred upstream120
  • Path adjacencies are derived from route collector AS paths for 2 of 2 prefixes originated by AS56874. Appearing next to AS56874 in a path does not by itself confirm a direct BGP session or its commercial relationship.
  • Inferred neighbours come from AS paths seen by route collectors: 'left' neighbours appear between AS56874 and the collectors (likely upstreams), 'right' neighbours appear behind it.

Data updated . See limitations.