bgpreport

Network · data from 2026-11-12

AS398371 ORANGE-COUNTY-BROADBAND-AUTHORITY - OCBA

Registry name: ORANGE-COUNTY-BROADBAND-AUTHORITY - OCBA, US · not in PeeringDB

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

Announced routes

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

2605:c9c0::/32 No ROA Other IRR onlyRADB 632 99% 69
38.45.176.0/24 Valid Nonecovered by 38.45.176.0/22 672 100% 67
38.45.177.0/24 Valid Nonecovered by 38.45.176.0/22 672 100% 67
38.45.178.0/24 Valid Nonecovered by 38.45.176.0/22 672 100% 67
38.45.179.0/24 Valid Nonecovered by 38.45.176.0/22 672 100% 67
38.45.189.0/24 Valid Nonecovered by 38.45.188.0/22 672 100% 67
38.45.191.0/24 Valid Nonecovered by 38.45.188.0/22 672 100% 67
38.113.176.0/24 Valid Nonecovered by 38.113.176.0/22 672 100% 67
38.113.177.0/24 Valid Nonecovered by 38.113.176.0/22 672 100% 67
38.113.178.0/24 Valid Nonecovered by 38.113.176.0/22 672 100% 67
38.113.179.0/24 Valid Nonecovered by 38.113.176.0/22 672 100% 67
38.45.188.0/24 Valid Nonecovered by 38.45.188.0/22 669 99% 67
38.45.190.0/24 Valid Nonecovered by 38.45.188.0/22 669 99% 67
198.160.27.0/24 Valid Other IRR onlyRADB 673 100% 67
38.45.173.0/24 Valid Other IRR onlyRADB 672 100% 67
38.45.175.0/24 Valid Other IRR onlyRADB 672 100% 67
38.64.240.0/24 Valid Other IRR onlyRADB 672 100% 67
38.64.241.0/24 Valid Other IRR onlyRADB 672 100% 67
38.64.242.0/24 Valid Other IRR onlyRADB 672 100% 67
38.91.49.0/24 Valid Other IRR onlyRADB 672 100% 67
38.91.51.0/24 Valid Other IRR onlyRADB 672 100% 67
38.91.61.0/24 Valid Other IRR onlyRADB 672 100% 67
38.92.33.0/24 Valid Other IRR onlyRADB 672 100% 67
38.92.35.0/24 Valid Other IRR onlyRADB 672 100% 67
38.92.57.0/24 Valid Other IRR onlyRADB 672 100% 67
38.92.59.0/24 Valid Other IRR onlyRADB 672 100% 67
198.160.26.0/23 Valid Other IRR onlyRADB 670 100% 67
198.160.26.0/24 Valid Other IRR onlyRADB 670 100% 67
38.45.172.0/24 Valid Other IRR onlyRADB 669 99% 67
38.45.174.0/24 Valid Other IRR onlyRADB 669 99% 67
38.91.48.0/24 Valid Other IRR onlyRADB 669 99% 67
38.91.50.0/24 Valid Other IRR onlyRADB 669 99% 67
38.91.60.0/24 Valid Other IRR onlyRADB 669 99% 67
38.92.32.0/24 Valid Other IRR onlyRADB 669 99% 67
38.92.34.0/24 Valid Other IRR onlyRADB 669 99% 67
38.92.56.0/24 Valid Other IRR onlyRADB 669 99% 67
38.92.58.0/24 Valid Other IRR onlyRADB 669 99% 67
38.45.172.0/22 Valid RIR databaseARIN, RADB 670 100% 67
38.45.176.0/22 Valid RIR databaseARIN, RADB 670 100% 67
38.45.188.0/22 Valid RIR databaseARIN, RADB 670 100% 67
38.64.240.0/22 Valid RIR databaseARIN, RADB 670 100% 67
38.91.48.0/22 Valid RIR databaseARIN, RADB 670 100% 67
38.91.60.0/23 Valid RIR databaseARIN, RADB 670 100% 67
38.92.32.0/22 Valid RIR databaseARIN, RADB 670 100% 67
38.92.56.0/22 Valid RIR databaseARIN, RADB 670 100% 67
38.113.176.0/22 Valid RIR databaseARIN, RADB 670 100% 67
134.195.252.0/24 Valid RIR databaseARIN, RADB 668 99% 67

AS-SET

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

  • ROA: none1
  • Route object: none12
  • Route object: RIR25
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2605:c9c0::/32No ROA covers it. Add a ROA for AS398371, maxLength 32.632 of 636
Route object: RIR2605:c9c0::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: none38.45.176.0/24No route object for it. A route object for 38.45.176.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.45.177.0/24No route object for it. A route object for 38.45.176.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.45.178.0/24No route object for it. A route object for 38.45.176.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.45.179.0/24No route object for it. A route object for 38.45.176.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.45.189.0/24No route object for it. A route object for 38.45.188.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.45.191.0/24No route object for it. A route object for 38.45.188.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.113.176.0/24No route object for it. A route object for 38.113.176.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.113.177.0/24No route object for it. A route object for 38.113.176.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.113.178.0/24No route object for it. A route object for 38.113.176.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.113.179.0/24No route object for it. A route object for 38.113.176.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.672 of 673
Route object: none38.45.188.0/24No route object for it. A route object for 38.45.188.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.669 of 673
Route object: none38.45.190.0/24No route object for it. A route object for 38.45.188.0/22 with origin AS398371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398371 in the RIR database for the space.669 of 673
Route object: RIR198.160.27.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.45.173.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.45.175.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.64.240.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.64.241.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.64.242.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.91.49.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.91.51.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.91.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.92.33.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.92.35.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.92.57.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.92.59.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR198.160.26.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR198.160.26.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.45.172.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.45.174.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.91.48.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.91.50.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.91.60.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.92.32.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.92.34.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.92.56.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.92.58.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

38.64.243.0/24RADBValid

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.