Network · data from 2026-11-12
AS207904 VEUIBITS VEU I BITS, SERVEIS EMPRESARIALS S.L.
Registry name: VEUIBITS VEU I BITS, SERVEIS EMPRESARIALS S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207904, 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.
| 5.154.175.0/24 | No ROA | None | 672 100% |
| 194.147.213.0/24 | No ROA | Other origin only | 672 100% |
| 213.0.76.0/24 | Valid | RIR databaseRIPE | 619 92% |
| 213.0.77.0/24 | Valid | RIR databaseRIPE | 619 92% |
AS-SET
AS207904 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 6 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.154.175.0/24 | No ROA covers it. Add a ROA for AS207904, maxLength 24. |
| Route object: none | 5.154.175.0/24 | No route object for it. Add a route object with origin AS207904 in the RIR database for the space. |
| ROA: none | 194.147.213.0/24 | No ROA covers it. Add a ROA for AS207904, maxLength 24. |
| Route object: none | 194.147.213.0/24 | Route objects for it name AS201748. Add a route object with origin AS207904 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS207904 whose prefix no peer sees AS207904 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.18.40.0/21 | RIPE | No ROA |
| 46.18.46.0/24 | RIPE | No ROA |
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.