AS215568 Manding_Data_Venture MB Manding Data Venture
🇱🇹Org handle: ORG-MMDV2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
11total
0 IPv411 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)6.6×10³⁰
Announced (BGP)5.4×10³⁰
Routing hygiene
Score 13/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
81.8%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
- 18% of announced prefixes (2 of 11) have no IRR route object for this ASN
Based on 11 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)11|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | - | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | - | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 |
1-10 of 11
1 / 2
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 136.148.128.0/22 | 🇱🇹 LT | RIPENCC | assigned |
| 2a01:f1c0::/29 | 🇱🇹 LT | RIPENCC | allocated |
| 2a01:f540::/29 | 🇱🇹 LT | RIPENCC | allocated |
| 2a02:e9c0::/29 | 🇱🇹 LT | RIPENCC | allocated |
| 2a10:3580::/29 | 🇱🇹 LT | RIPENCC | allocated |
| 2a10:6e44::/30 | 🇳🇱 NL | RIPE | assigned |
| 2a13:6cc0::/29 | 🇱🇹 LT | RIPENCC | allocated |
| 2a13:bf40::/29 | 🇱🇹 LT | RIPENCC | allocated |
| 2a13:cd40::/30 | 🇫🇷 FR | RIPE | assigned |
| 2a13:cd44::/30 | 🇫🇷 FR | RIPE | assigned |
1-10 of 13
1 / 2
All 11 announced prefixes of AS215568 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS215568 hands its own prefixes to: transit providers, or peers at an exchange.
- AS216213Lexistar Alliance11
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 AS215568 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/215568Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/215568" | jq