bgpreport

Network · data from 2026-11-12

AS23420 Davenpro Enterprises

Registry name: AS-DAVENPRO - Davenpro Enterprises LLC, US · PeeringDB

6IPv4 routes 0.0% RPKI valid · 83.3% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS23420, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23420, 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.
69.22.133.0/24 No ROA Other origin onlycovered by 69.22.132.0/22 673 100% 67
69.22.132.0/22 No ROA RIR databaseARIN 673 100% 67
69.31.16.0/21 No ROA RIR databaseARIN 673 100% 67
198.47.119.0/24 No ROA RIR databaseARIN 673 100% 67
198.47.123.0/24 No ROA RIR databaseARIN 673 100% 67
204.93.36.0/24 No ROA RIR databaseARIN 673 100% 67
2605:9c40::/32 Valid RIR databaseARIN, RADB 636 100% 68

AS-SET

PeeringDB's irr_as_set for AS23420: AS-DAVENPRO. 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 (AS23420 isn't in the set, or no route object for AS23420 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 objectsAS23420 in itNot covered
AS-DAVENPRO ARIN 116 Yes 0

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.

  • ROA: none6
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none69.22.133.0/24No ROA covers it. Add a ROA for AS23420, maxLength 24.673 of 673
Route object: none69.22.133.0/24Route objects for it name AS32959. A route object for 69.22.132.0/22 with origin AS23420 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23420 in the RIR database for the space.673 of 673
ROA: none69.22.132.0/22No ROA covers it. Add a ROA for AS23420, maxLength 22.673 of 673
ROA: none69.31.16.0/21No ROA covers it. Add a ROA for AS23420, maxLength 21.673 of 673
ROA: none198.47.119.0/24No ROA covers it. Add a ROA for AS23420, maxLength 24.673 of 673
ROA: none198.47.123.0/24No ROA covers it. Add a ROA for AS23420, maxLength 24.673 of 673
ROA: none204.93.36.0/24No ROA covers it. Add a ROA for AS23420, maxLength 24.673 of 673

Route objects not announced

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