bgpreport

Network · data from 2026-11-12

AS29843 FIVEA-AS1 - Five Area Systems, LLC

Registry name: FIVEA-AS1 - Five Area Systems, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29843, 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.
66.252.211.0/24 Valid Nonecovered by 66.252.208.0/20 673 100% 67
66.252.212.0/22 Valid Nonecovered by 66.252.208.0/20 673 100% 67
66.252.217.0/24 Valid Nonecovered by 66.252.208.0/20 673 100% 67
66.252.221.0/24 Valid Nonecovered by 66.252.208.0/20 673 100% 67
216.229.115.0/24 Valid Nonecovered by 216.229.112.0/21 673 100% 67
216.229.116.0/22 Valid Nonecovered by 216.229.112.0/21 673 100% 67
66.252.223.0/24 Valid Nonecovered by 66.252.208.0/20 669 99% 67
66.252.208.0/20 Valid RIR databaseALTDB, ARIN 669 99% 67
216.229.112.0/21 Valid RIR databaseALTDB, ARIN 669 99% 67
2604:2040::/32 Valid RIR databaseARIN 634 100% 67

AS-SET

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

  • Route object: none7
ChangePrefix or setDetailFull-table peers
Route object: none66.252.211.0/24No route object for it. A route object for 66.252.208.0/20 with origin AS29843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29843 in the RIR database for the space.673 of 673
Route object: none66.252.212.0/22No route object for it. A route object for 66.252.208.0/20 with origin AS29843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29843 in the RIR database for the space.673 of 673
Route object: none66.252.217.0/24No route object for it. A route object for 66.252.208.0/20 with origin AS29843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29843 in the RIR database for the space.673 of 673
Route object: none66.252.221.0/24No route object for it. A route object for 66.252.208.0/20 with origin AS29843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29843 in the RIR database for the space.673 of 673
Route object: none216.229.115.0/24No route object for it. A route object for 216.229.112.0/21 with origin AS29843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29843 in the RIR database for the space.673 of 673
Route object: none216.229.116.0/22No route object for it. A route object for 216.229.112.0/21 with origin AS29843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29843 in the RIR database for the space.673 of 673
Route object: none66.252.223.0/24No route object for it. A route object for 66.252.208.0/20 with origin AS29843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29843 in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS29843 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.