bgpreport

Network · data from 2026-11-12

AS13866 Computer Country

Registry name: CCOUNTRY - Computer Country, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13866, 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.
65.167.68.0/22 No ROA None 673 100% 67
206.81.208.0/23 No ROA Other origin only 673 100% 67
208.3.100.0/23 No ROA None 673 100% 67
208.19.12.0/22 No ROA None 673 100% 67
65.112.28.0/23 No ROA Other IRR onlyRADB 671 100% 67
65.170.86.0/23 No ROA Other IRR onlyRADB 671 100% 67
198.251.112.0/20 Valid RIR databaseARIN, RADB 673 100% 67
2602:fff8::/36 Valid RIR databaseARIN, RADB 635 100% 69

AS-SET

AS13866's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none65.167.68.0/22No ROA covers it. Add a ROA for AS13866, maxLength 22.673 of 673
Route object: none65.167.68.0/22No route object for it. Add a route object with origin AS13866 in the RIR database for the space.673 of 673
ROA: none206.81.208.0/23No ROA covers it. Add a ROA for AS13866, maxLength 23.673 of 673
Route object: none206.81.208.0/23Route objects for it name AS18812. Add a route object with origin AS13866 in the RIR database for the space.673 of 673
ROA: none208.3.100.0/23No ROA covers it. Add a ROA for AS13866, maxLength 23.673 of 673
Route object: none208.3.100.0/23No route object for it. Add a route object with origin AS13866 in the RIR database for the space.673 of 673
ROA: none208.19.12.0/22No ROA covers it. Add a ROA for AS13866, maxLength 22.673 of 673
Route object: none208.19.12.0/22No route object for it. Add a route object with origin AS13866 in the RIR database for the space.673 of 673
ROA: none65.112.28.0/23No ROA covers it. Add a ROA for AS13866, maxLength 23.671 of 673
Route object: RIR65.112.28.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none65.170.86.0/23No ROA covers it. Add a ROA for AS13866, maxLength 23.671 of 673
Route object: RIR65.170.86.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

198.25.112.0/20RADBNo 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.