bgpreport

Network · data from 2026-11-12

AS29906 Westat

Registry name: WESTAT-AS1 - Westat, Inc., US · PeeringDB

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

Announced routes

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

198.232.249.0/24 No ROA Other IRR onlyALTDB 667 99% 68
198.232.250.0/24 No ROA Other IRR onlyALTDB 667 99% 68
198.232.251.0/24 No ROA Other IRR onlyALTDB 667 99% 68
198.232.252.0/24 No ROA Other IRR onlyALTDB 667 99% 68
74.119.60.0/24 No ROA RIR databaseALTDB, ARIN 667 99% 68
74.119.61.0/24 No ROA RIR databaseALTDB, ARIN 667 99% 68
74.119.62.0/24 No ROA RIR databaseALTDB, ARIN 667 99% 68
74.119.63.0/24 No ROA RIR databaseALTDB, ARIN 667 99% 68
2620:68::/48 No ROA RIR databaseALTDB, ARIN 630 99% 69

AS-SET

PeeringDB's irr_as_set for AS29906: AS29906. 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 (AS29906 isn't in the set, or no route object for AS29906 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 objectsAS29906 in itNot covered
AS29906 A single AS number, not a set: AS29906 (this network), 9 route objects.

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: none9
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none198.232.249.0/24No ROA covers it. Add a ROA for AS29906, maxLength 24.667 of 673
Route object: RIR198.232.249.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
ROA: none198.232.250.0/24No ROA covers it. Add a ROA for AS29906, maxLength 24.667 of 673
Route object: RIR198.232.250.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
ROA: none198.232.251.0/24No ROA covers it. Add a ROA for AS29906, maxLength 24.667 of 673
Route object: RIR198.232.251.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
ROA: none198.232.252.0/24No ROA covers it. Add a ROA for AS29906, maxLength 24.667 of 673
Route object: RIR198.232.252.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
ROA: none74.119.60.0/24No ROA covers it. Add a ROA for AS29906, maxLength 24.667 of 673
ROA: none74.119.61.0/24No ROA covers it. Add a ROA for AS29906, maxLength 24.667 of 673
ROA: none74.119.62.0/24No ROA covers it. Add a ROA for AS29906, maxLength 24.667 of 673
ROA: none74.119.63.0/24No ROA covers it. Add a ROA for AS29906, maxLength 24.667 of 673
ROA: none2620:68::/48No ROA covers it. Add a ROA for AS29906, maxLength 48.630 of 636

Route objects not announced

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