Skip to main content

AS48287

RU-CENTER

==== MSK ====

Registry

Authoritative registration data

AS number
48287
Name
RU-CENTER
Organisation
==== MSK ====
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

40

IPv6 prefixes

2

Total announced

42

Announced prefixes

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

Prefixes announced by AS48287
178.210.64.0/19 IPv4 /19 RPKI valid
178.210.64.0/20 IPv4 /20 RPKI valid
109.70.24.0/21 IPv4 /21 not checked
178.210.80.0/21 IPv4 /21 not checked
89.104.80.0/21 IPv4 /21 RPKI valid
91.189.112.0/21 IPv4 /21 not checked
178.210.88.0/22 IPv4 /22 RPKI valid
185.26.112.0/22 IPv4 /22 RPKI valid
185.76.144.0/22 IPv4 /22 not checked
195.24.64.0/22 IPv4 /22 not checked
31.177.64.0/22 IPv4 /22 RPKI valid
31.177.68.0/22 IPv4 /22 not checked
31.177.92.0/22 IPv4 /22 not checked
89.111.144.0/22 IPv4 /22 not checked
89.111.148.0/22 IPv4 /22 RPKI valid
89.111.156.0/22 IPv4 /22 RPKI valid
91.189.116.0/22 IPv4 /22 not checked
109.70.26.0/23 IPv4 /23 RPKI valid
109.70.30.0/23 IPv4 /23 RPKI valid
195.24.68.0/23 IPv4 /23 RPKI valid
31.177.78.0/23 IPv4 /23 RPKI valid
89.111.132.0/23 IPv4 /23 not checked
91.189.114.0/23 IPv4 /23 RPKI valid
109.70.24.0/24 IPv4 /24 not checked
109.70.25.0/24 IPv4 /24 not checked
178.210.92.0/24 IPv4 /24 not checked
193.232.130.0/24 IPv4 /24 not checked
193.232.146.0/24 IPv4 /24 RPKI not found
194.226.96.0/24 IPv4 /24 RPKI not found
194.85.61.0/24 IPv4 /24 not checked
195.208.0.0/24 IPv4 /24 not checked
195.208.1.0/24 IPv4 /24 RPKI not found
31.177.76.0/24 IPv4 /24 not checked
31.177.80.0/24 IPv4 /24 not checked
31.177.84.0/24 IPv4 /24 not checked
31.177.91.0/24 IPv4 /24 not checked
89.111.128.0/24 IPv4 /24 RPKI valid
89.111.130.0/24 IPv4 /24 RPKI valid
89.111.164.0/24 IPv4 /24 not checked
91.217.20.0/24 IPv4 /24 not checked
2a02:2090:1::/48 IPv6 /48 RPKI valid
2a02:2090::/48 IPv6 /48 RPKI valid

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 AS48287
Address families
CLOUD-IX SPB 10,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network — IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4 · IPv6

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 AS48287 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS48287 in AS paths

Observed upstreams
Families
AS201706 AS-SERVICEPIPE 1,510 15,848
v4
AS5537 RU-CENTER-AS 1,873 10,186
v4 v6
AS199599 CIREX 574 2,241
v4 v6
AS6939 HURRICANE 34 78
v4
AS25091 IP-Max 21 74
v4 v6
AS41327 FIBERTELECOM-AS 5 10
v4 v6
AS9198 KAZTELECOM-AS 3 6
v6
AS43727 KVANT-TELECOM 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

8 networks seen after AS48287 in AS paths

Observed downstreams
Families
AS39494 RU-CENTER-AS 1,368 9,536
v4 v6
AS199472 FAITID-AS 296 1,855
v4
AS43489 ANYCAST-AS 373 783
v4 v6
AS42399 HCRU-AS 349 503
v4
AS44112 SWEB-AS 283 367
v4
AS47595 ZAO-RU-NIC-AS 138 338
v4
AS60216 FAITID-AS 25 165
v4
AS5537 RU-CENTER-AS 55 136
v4

No rows match “”.

Showing – of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 4 22
v4 v6
AS36236 NETACTUATE 4 8
v4 v6
AS41722 MIRAN-AS 4 8
v4 v6
AS28910 INTAL-ASN 3 6
v4 v6
AS20764 RASCOM-AS 1 2
v4
AS28917 Fiord-AS 1 2
v4
AS35598 INETCOM 1 2
v4
AS49673 TRUENETWORK 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.