bgpreport

Network · data from 2026-11-12

AS12161 dao Consulting

Registry name: DAO - dao Consulting, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12161, 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.
169.131.48.0/22 No ROA Other IRR onlyRADB 667 99% 67
169.131.52.0/24 No ROA Other IRR onlyRADB 667 99% 67
199.184.246.0/24 No ROA Other IRR onlyALTDB, RADB 667 99% 67
204.107.248.0/24 No ROA Other IRR onlyALTDB 667 99% 67
204.128.154.0/24 No ROA Other IRR onlyALTDB 667 99% 67
199.74.222.0/24 Valid RIR databaseALTDB, ARIN, RADB 667 99% 67
2620:124:1000::/44 Valid RIR databaseALTDB, ARIN, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS12161: ARIN::AS-DAO. 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 (AS12161 isn't in the set, or no route object for AS12161 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 objectsAS12161 in itNot covered
ARIN::AS-DAO ARIN 1210 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 13 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none169.131.48.0/22No ROA covers it. Add a ROA for AS12161, maxLength 22.667 of 673
Route object: RIR169.131.48.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none169.131.52.0/24No ROA covers it. Add a ROA for AS12161, maxLength 24.667 of 673
Route object: RIR169.131.52.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none199.184.246.0/24No ROA covers it. Add a ROA for AS12161, maxLength 24.667 of 673
Route object: RIR199.184.246.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none204.107.248.0/24No ROA covers it. Add a ROA for AS12161, maxLength 24.667 of 673
Route object: RIR204.107.248.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
ROA: none204.128.154.0/24No ROA covers it. Add a ROA for AS12161, maxLength 24.667 of 673
Route object: RIR204.128.154.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

169.131.0.0/16ALTDB, RADBNo ROA
169.131.52.0/22ALTDB, RADBNo ROA
199.74.249.0/24ARINValid

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.