RU-CENTER AS48287

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks9
IPv6 4 prefixes (largest 2001:7f8:20:101::208:157/128)
Also registered under this name 48 netblocks across 13 separate records
Record ID242141443
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.28.18.76/32 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high
185.1.152.93/32 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high
195.208.208.157/32 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high
195.208.208.222/32 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high
195.208.209.45/32 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high
2001:7f8:20:101::208:157/128 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high
2001:7f8:20:101::208:222/128 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high
2001:7f8:e6::bc9f:1/128 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high
2a00:13c0:3:2::1f1c:124c/128 RU-CENTER AS48287 PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Footprint over time

13 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-09-20

Network trust

what's this?
RPKI hygiene: C how networks compare →
55.6% of checked blocks have valid RPKI ROA coverage (5 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS48287