bgpreport

Network · data from 2026-11-12

AS53299 BetaForward, Inc

Registry name: BETAFORWARD - BetaForward, Inc, US · PeeringDB

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

Announced routes

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

2602:f701::/40 No ROA None 635 100% 67
208.65.254.0/24 No ROA Other origin only 593 88% 67

AS-SET

AS53299's PeeringDB record names no 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 4 are in fix.csv.

  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none2602:f701::/40No ROA covers it. Add a ROA for AS53299, maxLength 40.635 of 636
Route object: none2602:f701::/40No route object for it. Add a route object with origin AS53299 in the RIR database for the space.635 of 636
ROA: none208.65.254.0/24No ROA covers it. Add a ROA for AS53299, maxLength 24.593 of 673
Route object: none208.65.254.0/24Route objects for it name AS262. Add a route object with origin AS53299 in the RIR database for the space.593 of 673

Route objects not announced

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