bgpreport

Network · data from 2026-11-12

AS53497 WEBPERCEPTION - WebPerception, LLC

Registry name: WEBPERCEPTION - WebPerception, LLC, US · not in PeeringDB

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

Announced routes

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

64.7.64.0/24 Invalid: maxLength Nonecovered by 64.7.64.0/20 69 10% 41
209.112.96.0/24 No ROA Other IRR onlyRADB 673 100% 67
64.7.64.0/20 Valid RIR databaseARIN, RADB 673 100% 70
64.7.80.0/21 Valid RIR databaseARIN, RADB 673 100% 70

AS-SET

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

  • ROA: maxLength1
  • ROA: none1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: maxLength64.7.64.0/24ROA 64.7.64.0/20 AS53497 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 64.7.64.0/24.69 of 673
Route object: none64.7.64.0/24No route object for it. A route object for 64.7.64.0/20 with origin AS53497 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53497 in the RIR database for the space.69 of 673
ROA: none209.112.96.0/24No ROA covers it. Add a ROA for AS53497, maxLength 24.673 of 673
Route object: RIR209.112.96.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 AS53497 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.