bgpreport

Network · data from 2026-11-12

AS6493 BEACON-TECHNOLOGIES-AS - Beacon Technologies, Inc

Registry name: BEACON-TECHNOLOGIES-AS - Beacon Technologies, Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6493, 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.
209.195.192.0/20 No ROA Other origin only 673 100% 67
209.195.208.0/21 No ROA None 673 100% 67
209.195.232.0/22 No ROA None 673 100% 67
209.195.244.0/22 No ROA None 673 100% 67
209.120.196.0/22 No ROA Other IRR onlyRADB 673 100% 67
209.120.200.0/22 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none209.195.192.0/20No ROA covers it. Add a ROA for AS6493, maxLength 20.673 of 673
Route object: none209.195.192.0/20Route objects for it name AS7029. Add a route object with origin AS6493 in the RIR database for the space.673 of 673
ROA: none209.195.208.0/21No ROA covers it. Add a ROA for AS6493, maxLength 21.673 of 673
Route object: none209.195.208.0/21No route object for it. Add a route object with origin AS6493 in the RIR database for the space.673 of 673
ROA: none209.195.232.0/22No ROA covers it. Add a ROA for AS6493, maxLength 22.673 of 673
Route object: none209.195.232.0/22No route object for it. Add a route object with origin AS6493 in the RIR database for the space.673 of 673
ROA: none209.195.244.0/22No ROA covers it. Add a ROA for AS6493, maxLength 22.673 of 673
Route object: none209.195.244.0/22No route object for it. Add a route object with origin AS6493 in the RIR database for the space.673 of 673
ROA: none209.120.196.0/22No ROA covers it. Add a ROA for AS6493, maxLength 22.673 of 673
Route object: RIR209.120.196.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none209.120.200.0/22No ROA covers it. Add a ROA for AS6493, maxLength 22.673 of 673
Route object: RIR209.120.200.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

208.248.0.0/20RADBNo 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.