bgpreport

Network · data from 2026-11-12

AS209861 Christoffer Aasum Unes

Registry name: AS_CHRISTOFFERUNES Christoffer Aasum Unes, NO · PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object
4IPv6 routes 75.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS209861, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS209861, 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.

143.20.75.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a0e:b107:f0::/44 No ROA RIR databaseRIPE 633 100% 69
2a01:ffc6:8000::/34 Valid RIR databaseRIPE 634 100% 69
2a10:a642:aa00::/40 Valid RIR databaseRIPE 634 100% 69
2a0a:3e45:be00::/40 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS209861: AS209861:AS-DOWNSTREAM. 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 (AS209861 isn't in the set, or no route object for AS209861 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.

NameDatabaseASNsSets Route objectsAS209861 in itNot covered
AS209861:AS-DOWNSTREAM RIPE 2121 Yes 1

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 12 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin143.20.75.0/24ROAs covering it name AS834, not AS209861. If AS209861 should announce it, add a ROA for AS209861.2 of 673
Route object: none143.20.75.0/24Route objects for it name AS834. Add a route object with origin AS209861 in the RIR database for the space.2 of 673
ROA: none2a0e:b107:f0::/44No ROA covers it. Add a ROA for AS209861, maxLength 44.633 of 636

Route objects not announced

Route objects with origin AS209861 whose prefix no peer sees AS209861 announce. Many are kept on purpose (backup routes, space announced only in some places).

2602:fafd:f03::/48ARINValid
2a01:ffc6:b00b::/48RIPEValid
2a07:54c2:b00b::/48RIPEValid
2a0a:3e45:beef::/48RIPEValid
2a0e:b107:f0::/48RIPEInvalid: origin
2a0e:b107:f1::/48RIPEInvalid: origin
2a10:a642:aa00::/48RIPEValid
2a10:a642:aa01::/48RIPEValid
2a13:9500:66::/48RIPEValid

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.