bgpreport

Network · data from 2026-11-12

AS402072 OZONTI-NETWORK-LLC - OZONTI NETWORK LLC

Registry name: OZONTI-NETWORK-LLC - OZONTI NETWORK LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402072, 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.83.70.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2602:f52a:1::/48 No ROA None 635 100% 67
2602:f52a::/40 No ROA None 633 100% 68
23.147.236.0/24 Valid RIR databaseARIN 673 100% 67
64.205.62.0/24 Valid RIR databaseARIN, RADB 671 100% 67
69.33.209.0/24 Valid RIR databaseARIN, RADB 671 100% 67
199.204.140.0/24 Valid RIR databaseARIN 671 100% 68
199.204.143.0/24 Valid RIR databaseARIN, RADB 671 100% 67
216.46.79.0/24 Valid RIR databaseARIN, RADB 671 100% 67
66.253.95.0/24 Valid RIR databaseARIN, RADB 670 100% 67
77.111.105.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
69.33.199.0/24 Valid RIR databaseARIN, RADB 669 99% 67
2602:f52a::/48 Valid RIR databaseARIN, RADB 635 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none2
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin64.83.70.0/24ROAs covering it name AS834, AS21769, not AS402072. If AS402072 should announce it, add a ROA for AS402072.2 of 673
Route object: none64.83.70.0/24Route objects for it name AS834. Add a route object with origin AS402072 in the RIR database for the space.2 of 673
ROA: none2602:f52a:1::/48No ROA covers it. Add a ROA for AS402072, maxLength 48.635 of 636
Route object: none2602:f52a:1::/48No route object for it. Add a route object with origin AS402072 in the RIR database for the space.635 of 636
ROA: none2602:f52a::/40No ROA covers it. Add a ROA for AS402072, maxLength 40.633 of 636
Route object: none2602:f52a::/40No route object for it. Add a route object with origin AS402072 in the RIR database for the space.633 of 636

Route objects not announced

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

199.204.141.0/24RADBNo 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.