Network · data from 2026-11-12
AS269893 AS269893 - NETWORK CONNEXIONS SAS
Registry name: AS269893 - NETWORK CONNEXIONS SAS, CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269893, 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:94e0:800::/38 | Valid | Nonecovered by 2803:94e0::/32 | 635 100% |
| 2803:94e0:400::/38 | Valid | Other IRR onlyRADB | 635 100% |
| 45.191.74.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 45.190.86.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
AS-SET
AS269893 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 5 are in fix.csv.
- Route object: none1
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:94e0:800::/38 | No route object for it. A route object for 2803:94e0::/32 with origin AS269893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269893 in the RIR database for the space. |
| Route object: RIR | 2803:94e0:400::/38 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269893 whose prefix no peer sees AS269893 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.191.74.0/23 | RADB | No ROA |
| 2803:94e0::/32 | LACNIC, RADB | Valid |
| 2803:94e0::/38 | 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.