bgpreport

Network · data from 2026-11-12

AS53855 RIPPLE-01 - Ripple

Registry name: RIPPLE-01 - Ripple, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53855, 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.
204.57.208.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.34.110.0/24 No ROA RIR databaseARIN 673 100% 67
199.34.111.0/24 No ROA RIR databaseARIN 673 100% 67
199.34.112.0/24 No ROA RIR databaseARIN 673 100% 67
185.224.64.0/24 Valid Nonecovered by 185.224.64.0/22 673 100% 67
185.224.65.0/24 Valid Nonecovered by 185.224.64.0/22 673 100% 67

AS-SET

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

  • ROA: none4
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none204.57.208.0/24No ROA covers it. Add a ROA for AS53855, maxLength 24.673 of 673
Route object: RIR204.57.208.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.34.110.0/24No ROA covers it. Add a ROA for AS53855, maxLength 24.673 of 673
ROA: none199.34.111.0/24No ROA covers it. Add a ROA for AS53855, maxLength 24.673 of 673
ROA: none199.34.112.0/24No ROA covers it. Add a ROA for AS53855, maxLength 24.673 of 673
Route object: none185.224.64.0/24No route object for it. A route object for 185.224.64.0/22 with origin AS53855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53855 in the RIR database for the space.673 of 673
Route object: none185.224.65.0/24No route object for it. A route object for 185.224.64.0/22 with origin AS53855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53855 in the RIR database for the space.673 of 673

Route objects not announced

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

185.224.64.0/22ARINNo ROA
199.34.113.0/24ARINNo ROA
2602:814:a000::/44ARINValid

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.