bgpreport

Network · data from 2026-11-12

AS397879 LUMINATE-01 - Luminate Fiber LLC

Registry name: LUMINATE-01 - Luminate Fiber LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS397879, 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.
148.170.0.0/20 No ROA Nonecovered by 148.170.0.0/18 670 100% 68
148.170.32.0/20 No ROA Nonecovered by 148.170.0.0/18 670 100% 68
148.170.48.0/20 No ROA Nonecovered by 148.170.0.0/18 670 100% 68
148.170.0.0/18 No ROA Other IRR onlyRADB 670 100% 68
148.170.16.0/20 No ROA Other IRR onlyRADB 670 100% 68

AS-SET

AS397879 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: none5
  • Route object: none3
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none148.170.0.0/20No ROA covers it. Add a ROA for AS397879, maxLength 20.670 of 673
Route object: none148.170.0.0/20No route object for it. A route object for 148.170.0.0/18 with origin AS397879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397879 in the RIR database for the space.670 of 673
ROA: none148.170.32.0/20No ROA covers it. Add a ROA for AS397879, maxLength 20.670 of 673
Route object: none148.170.32.0/20No route object for it. A route object for 148.170.0.0/18 with origin AS397879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397879 in the RIR database for the space.670 of 673
ROA: none148.170.48.0/20No ROA covers it. Add a ROA for AS397879, maxLength 20.670 of 673
Route object: none148.170.48.0/20No route object for it. A route object for 148.170.0.0/18 with origin AS397879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397879 in the RIR database for the space.670 of 673
ROA: none148.170.0.0/18No ROA covers it. Add a ROA for AS397879, maxLength 18.670 of 673
Route object: RIR148.170.0.0/18Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none148.170.16.0/20No ROA covers it. Add a ROA for AS397879, maxLength 20.670 of 673
Route object: RIR148.170.16.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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