Network · data from 2026-11-12
AS39444 Owentis
Registry name: OWENTIS-AS OWENTIS SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39444, 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.
| 176.111.56.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.178.191.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.204.106.0/24 | Valid | Nonecovered by 185.204.104.0/22 | 673 100% |
| 46.30.206.0/24 | Valid | Nonecovered by 46.30.200.0/21 | 672 100% |
| 46.30.200.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 85.31.211.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.31.212.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.204.104.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 2a03:2680::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS39444: AS-OWENTIS:AS-SET RS-OWENTIS:RS-SET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS39444 isn't in the set, or no route object for AS39444 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS39444 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-OWENTIS:AS-SET | In no IRR database read today. | |||||
| RS-OWENTIS:RS-SET | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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 7 are in fix.csv.
- ROA: none2
- Route object: none2
- AS-SET: not found1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 176.111.56.0/24 | No ROA covers it. Add a ROA for AS39444, maxLength 24. |
| ROA: none | 193.178.191.0/24 | No ROA covers it. Add a ROA for AS39444, maxLength 24. |
| Route object: none | 185.204.106.0/24 | No route object for it. A route object for 185.204.104.0/22 with origin AS39444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39444 in the RIR database for the space. |
| Route object: none | 46.30.206.0/24 | No route object for it. A route object for 46.30.200.0/21 with origin AS39444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39444 in the RIR database for the space. |
| AS-SET: not found | AS-OWENTIS:AS-SET | PeeringDB names AS-OWENTIS:AS-SET; no IRR database read has it. |
Route objects not announced
Route objects with origin AS39444 whose prefix no peer sees AS39444 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.50.14.0/23 | RIPE | Valid |
| 2001:470:14f::/48 | ARIN | 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.