Network · data from 2026-11-12
AS49230 ARUMTEC ARUM TECHNOLOGIES
Registry name: ARUMTEC ARUM TECHNOLOGIES, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49230, 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.
| 149.7.101.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 670 100% |
| 91.212.119.0/24 | No ROA | RIR databaseRIPE | 670 100% |
AS-SET
AS49230 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 4 are in fix.csv.
- ROA: none2
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.7.101.0/24 | No ROA covers it. Add a ROA for AS49230, maxLength 24. |
| Route object: RIR | 149.7.101.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 91.212.119.0/24 | No ROA covers it. Add a ROA for AS49230, maxLength 24. |
Route objects not announced
Route objects with origin AS49230 whose prefix no peer sees AS49230 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 149.13.116.0/24 | RIPE-NONAUTH | 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.