bgpreport

Network · data from 2026-11-12

AS29697 Commercial Network Services (CNS)

Registry name: BEEKS-AS - BeeksFX VPS USA Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29697, 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.168.49.0/24 No ROA RIR databaseARIN 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS29697: RADB::AS-CNS. 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 (AS29697 isn't in the set, or no route object for AS29697 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 objectsAS29697 in itNot covered
RADB::AS-CNS In no IRR database read today.

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

  • ROA: none1
  • AS-SET: not found1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none69.168.49.0/24No ROA covers it. Add a ROA for AS29697, maxLength 24.673 of 673
AS-SET: not foundRADB::AS-CNSPeeringDB names RADB::AS-CNS; no IRR database read has it.

Route objects not announced

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

5.133.186.0/24RIPEInvalid: origin
5.133.187.0/24RIPEInvalid: origin
5.133.188.0/24RIPENo ROA
37.58.25.0/24RIPENo ROA
84.45.32.0/24RIPEInvalid: origin
2a04:f640::/29RIPENo 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.