bgpreport

Network · data from 2026-11-12

AS33288 DASH FT - Dash Financial Technologies LLC

Registry name: DASH FT - Dash Financial Technologies LLC, US · not in PeeringDB

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

Announced routes

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

107.161.149.0/24 No ROA Other IRR onlyRADB 673 100% 66
205.159.88.0/24 No ROA Other IRR onlyRADB 673 100% 66
209.120.216.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS33288 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none107.161.149.0/24No ROA covers it. Add a ROA for AS33288, maxLength 24.673 of 673
Route object: RIR107.161.149.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.159.88.0/24No ROA covers it. Add a ROA for AS33288, maxLength 24.673 of 673
Route object: RIR205.159.88.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none209.120.216.0/24No ROA covers it. Add a ROA for AS33288, maxLength 24.673 of 673
Route object: RIR209.120.216.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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