Skip to main content

AS56874

ELECTROSVYAZ-AS

Electrosvyazstroy OOO

Registry

Authoritative registration data

AS number
56874
Name
ELECTROSVYAZ-AS
Organisation
Electrosvyazstroy OOO
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS56874
185.62.229.0/24 IPv4 /24 not checked
91.228.118.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS56874
Address families
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS56874 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS56874 in AS paths

Observed upstreams
Families
AS3216 SOVAM-AS 149 368
v4
AS8732 COMCOR-AS 92 226
v4
AS6939 HURRICANE 18 38
v4
AS25091 IP-Max 4 14
v4
AS49434 2 4
v4
AS61049 2 4
v4
AS9198 1 2
v4
AS137409 GSLNETWORKS-AS-AP 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS56874 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 18
v4
AS28910 1 2
v4
AS29049 1 2
v4
AS34927 iFog-GmbH 1 2
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.