Network · data from 2026-11-12
AS272978 ORINOCO VENTURES GROUP SAS
Registry name: AS272978 - ORINOCO VENTURES GROUP SAS, CO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272978, 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.
| 2803:b0e0:7005::/48 | Valid | None | 631 99% |
| 38.199.68.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 38.199.76.0/24 | Valid | RIR databaseARIN, RADB | 666 99% |
| 2803:b0e0:7000::/48 | Valid | RIR databaseLACNIC, RADB | 632 99% |
AS-SET
AS272978's PeeringDB record names no 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 15 are in fix.csv.
- Route object: none1
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:b0e0:7005::/48 | No route object for it. Add a route object with origin AS272978 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS272978 whose prefix no peer sees AS272978 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.56.114.0/24 | RADB | No ROA |
| 38.56.119.0/24 | RADB | No ROA |
| 38.137.198.0/24 | RADB | No ROA |
| 38.137.200.0/23 | RADB | No ROA |
| 38.137.208.0/24 | RADB | No ROA |
| 38.137.210.0/24 | RADB | No ROA |
| 38.199.74.0/24 | ARIN, RADB | Valid |
| 131.161.200.0/24 | LACNIC, RADB | Valid |
| 2803:b0e0:8008::/46 | LACNIC, RADB | Valid |
| 2803:b0e0:8008::/48 | RADB | Valid |
| 2803:b0e0:800a::/48 | RADB | Valid |
| 2803:b0e0:800c::/48 | LACNIC, RADB | Valid |
| 2803:b0e0:801a::/48 | LACNIC, RADB | Valid |
| 2803:b0e0:99c8::/48 | LACNIC, RADB | Valid |
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.