bgpreport

Network · data from 2026-11-12

AS16876 ICANN AS16876

Registry name: ICANN-DC - ICANN, US · PeeringDB

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

Announced routes

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

208.77.189.0/24 No ROA None 673 100% 67
192.0.44.0/22 No ROA Other IRR onlyRADB 673 100% 67
192.0.47.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.4.29.0/24 No ROA Other IRR onlyRADB 673 100% 67
208.77.191.0/24 No ROA Other IRR onlyRADB 673 100% 67
2602:800:900f::/48 No ROA Other IRR onlyRADB 636 100% 67
2620:0:2830::/48 No ROA Other IRR onlyRADB 636 100% 67
192.0.43.0/24 No ROA Other IRR onlyRADB 544 81% 52
2001:500:88::/48 No ROA Other IRR onlyRADB 522 82% 54

AS-SET

PeeringDB's irr_as_set for AS16876: AS-ICANN. 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 (AS16876 isn't in the set, or no route object for AS16876 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 objectsAS16876 in itNot covered
AS-ICANN RADB 184161 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 18 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none208.77.189.0/24No ROA covers it. Add a ROA for AS16876, maxLength 24.673 of 673
Route object: none208.77.189.0/24No route object for it. Add a route object with origin AS16876 in the RIR database for the space.673 of 673
ROA: none192.0.44.0/22No ROA covers it. Add a ROA for AS16876, maxLength 22.673 of 673
Route object: RIR192.0.44.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.0.47.0/24No ROA covers it. Add a ROA for AS16876, maxLength 24.673 of 673
Route object: RIR192.0.47.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.4.29.0/24No ROA covers it. Add a ROA for AS16876, maxLength 24.673 of 673
Route object: RIR199.4.29.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.77.191.0/24No ROA covers it. Add a ROA for AS16876, maxLength 24.673 of 673
Route object: RIR208.77.191.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2602:800:900f::/48No ROA covers it. Add a ROA for AS16876, maxLength 48.636 of 636
Route object: RIR2602:800:900f::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2620:0:2830::/48No ROA covers it. Add a ROA for AS16876, maxLength 48.636 of 636
Route object: RIR2620:0:2830::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none192.0.43.0/24No ROA covers it. Add a ROA for AS16876, maxLength 24.544 of 673
Route object: RIR192.0.43.0/24Route object only in RADB. Add it in the RIR database for the space.544 of 673
ROA: none2001:500:88::/48No ROA covers it. Add a ROA for AS16876, maxLength 48.522 of 636
Route object: RIR2001:500:88::/48Route object only in RADB. Add it in the RIR database for the space.522 of 636

Route objects not announced

Every route object with origin AS16876 is announced.

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.