AS51375 VIVABH STC BAHRAIN B.S.C CLOSED
🇧🇭Org handle: ORG-VBBC1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
422total
409 IPv413 IPv6
IPv4 Addresses
Allocated (RIR)179,456
Announced (BGP)278,784
IPv6 Addresses
Allocated (RIR)7.1×10²⁹
Announced (BGP)7.1×10²⁹
Prefix Limit (IPv4)
1,000
Prefix Limit (IPv6)
50
Country
🇧🇭 BHRIR
RIPE NCCStatus
allocated
Allocated
2010-08-04
Routing hygiene
Score 3/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
98.3%
7 prefixes registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
6
diversity 69/100
- No significant routing hygiene issues found
Based on 421 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Listed on the threat map (2026-10-24)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)422|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | Other IRRRIPE | - | |
| Valid | Other IRRRIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | Other IRRRIPE | - | |
| Valid | Other IRRRIPE | - | |
| Valid | Other IRRRIPE | - |
1-10 of 422
1 / 43
Allocated Prefixes
(RIR)35Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.131.0.0/17 | 🇧🇭 BH | RIPENCC | allocated |
| 37.131.1.0/24 | 🇧🇭 BH | RIPE | assigned |
| 37.131.33.0/24 | 🇧🇭 BH | RIPE | assigned |
| 37.131.38.0/24 | 🇧🇭 BH | RIPE | assigned |
| 37.131.41.0/24 | 🇧🇭 BH | RIPE | assigned |
| 37.131.49.0/24 | 🇧🇭 BH | RIPE | assigned |
| 37.131.57.0/24 | 🇧🇭 BH | RIPE | assigned |
| 37.131.62.0/24 | 🇧🇭 BH | RIPE | assigned |
| 37.131.105.0/24 | 🇧🇭 BH | RIPE | assigned |
| 37.131.110.0/24 | 🇧🇭 BH | RIPE | assigned |
1-10 of 35
1 / 4
All 422 announced prefixes of AS51375 →
BGP Neighbours
(seen in AS paths)Upstreams (7)
Networks AS51375 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (7)
Networks whose own prefixes AS51375 passes on: usually its customers.
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 AS51375 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/51375Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/51375" | jq