Network · data from 2026-11-12
AS212642 RUNNANE Runnane Jon Tungland
Registry name: RUNNANE Runnane Jon Tungland, NO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS212642, 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.
| 2a00:1e18:800::/48 | Invalid: origin | None | 100 16% |
| 89.221.111.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a00:1e1f:ff00::/40 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS212642 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: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a00:1e18:800::/48 | ROAs covering it name AS8896, not AS212642. If AS212642 should announce it, add a ROA for AS212642. |
| Route object: none | 2a00:1e18:800::/48 | No route object for it. Add a route object with origin AS212642 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS212642 whose prefix no peer sees AS212642 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a00:1e1f:ff00::/48 | RIPE | Invalid: maxLength |
| 2a00:1e1f:ff01::/48 | RIPE | Invalid: maxLength |
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.