Network · data from 2026-11-12
AS209903 conscia-no Conscia Norge AS
Registry name: conscia-no Conscia Norge AS, NO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209903, 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.
| 2a02:d140:c017::/48 | Invalid: origin | None | 91 14% |
| 193.3.243.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a10:5a40::/30 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS209903 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.
- ROA: origin1
- ROA: none2
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a02:d140:c017::/48 | ROAs covering it name AS49788, not AS209903. If AS209903 should announce it, add a ROA for AS209903. |
| Route object: none | 2a02:d140:c017::/48 | No route object for it. Add a route object with origin AS209903 in the RIR database for the space. |
| ROA: none | 193.3.243.0/24 | No ROA covers it. Add a ROA for AS209903, maxLength 24. |
| ROA: none | 2a10:5a40::/30 | No ROA covers it. Add a ROA for AS209903, maxLength 30. |
Route objects not announced
Route objects with origin AS209903 whose prefix no peer sees AS209903 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:5a40::/29 | 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.