AS56463 ASAVICENA OOO "BSCOM"
🇷🇺Org handle: ORG-BSCM1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
6 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)4,096
Announced (BGP)4,096
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Routing hygiene
Score 40/100 · Medium riskRPKI ROA coverage
0%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (6 of 6) have no valid ROA
- Only one upstream seen in the AS paths of its routes
Based on 6 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-24 | |
| No ROA | - | 2026-10-24 | |
| No ROA | - | 2026-10-24 | |
| No ROA | - | 2026-10-24 | |
| No ROA | - | 2026-10-24 | |
| No ROA | - | 2026-10-24 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 176.102.160.0/21 | 🇷🇺 RU | RIPENCC | assigned |
| 188.191.184.0/21 | 🇷🇺 RU | RIPENCC | assigned |
All 6 announced prefixes of AS56463 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS56463 hands its own prefixes to: transit providers, or peers at an exchange.
- AS20485TRANSTELECOM Joint Stock Company TransTeleCom6
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS56463 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/56463Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/56463" | jq