Network · data from 2026-11-12
AS215568 Manding_Data_Venture MB Manding Data Venture
Registry name: Manding_Data_Venture MB Manding Data Venture, LT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215568, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2607:cf40::/32 | Valid | None | 635 100% |
| 2a13:d340::/29 | Valid | None | 632 99% |
| 2a01:f1c0::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:cd44::/30 | Valid | RIR databaseRIPE | 633 100% |
| 2a01:f540::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a10:3580::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a10:6e44::/30 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:bf40::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:cd40::/30 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:e140::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:d840::/29 | Valid | RIR databaseRIPE | 631 99% |
AS-SET
AS215568 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2607:cf40::/32 | No route object for it. Add a route object with origin AS215568 in the RIR database for the space. |
| Route object: none | 2a13:d340::/29 | No route object for it. Add a route object with origin AS215568 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS215568 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.